Return to Answer

The term "standards" in programming often refers to a technology that is governed by a group or community. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

Companies like IBM, Microsoft and others have published documentation of how to implement REST. One could say there is a "common way" of implementing REST. You can pick an authoritative source that describes an implementation of REST, and claim to follow that reference. The use of authoritative sources is one way we've been dealing with the problems of compatibility in web browsers.

The term "standards" in programming often refers to a technology/document that is governed by a group or community. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

Companies like IBM, Microsoft and others have published documentation of how to implement REST. One could say there is a "common way" of implementing REST. You can pick an authoritative source that describes an implementation of REST, and claim to follow that reference. The use of authoritative sources is one way we've been dealing with the problems of compatibility in web browsers.

The term "standards" in programming often refers to a group or community that governs a technology. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

Companies like IBM, Microsoft and others have published documentation of how to implement REST. One could say there is a "common way" of implementing REST. You can pick an authoritative source that describes an implementation of REST, and claim to follow that reference. The use of authoritative sources is one way we've been dealing with the problems of compatibility in web browsers.

The term "standards" in programming often refers to a technology that is governed by a group or community. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

Companies like IBM, Microsoft and others have published documentation of how to implement REST. One could say there is a "common way" of implementing REST. You can pick an authoritative source that describes an implementation of REST, and claim to follow that reference. The use of authoritative sources is one way we've been dealing with the problems of compatibility in web browsers.

The term "standards" in programming often refers to a group or community that governs a technology. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

The term "standards" in programming often refers to a group or community that governs a technology. The members of that group often share common invested goals, are active users of that technology and want to ensure the technology continues.

There are many "things" in programming that have a community that governs them. These members can range from programmers to corporate representation (i.e. Apple, Microsoft, IBM, etc. etc.)

W3C is a very large group that work together to define many standards.

Here is a list of members.

http://www.w3.org/Consortium/Member/List

REST is an example of a technology, by way of it's popularity is used by many people, but there is no group or community governing it. Therefore, there is no one place to point a finger and say "that's how the standards say it should be done".

Companies like IBM, Microsoft and others have published documentation of how to implement REST. One could say there is a "common way" of implementing REST. You can pick an authoritative source that describes an implementation of REST, and claim to follow that reference. The use of authoritative sources is one way we've been dealing with the problems of compatibility in web browsers.