Standards are easy. They are very well documented by the standardizing bodies. The W3C has very clear definitions of what semantically valid HTML markup looks like. Similarly, Oracle has very clear naming standards for classes, interfaces, and methods.
In fact, every Software Engineering student should at one time be introduced to coding standards, if not throughout their entire University career.
No matter what field we are in, the main goal of our education is to provide us all a foundation for communicating with other experts in our field. Coding standards are just one common way to ensure that a developer from a school in Maryland can step in and begin working on a very large, enterprise application developed by a developer in the UK, Oregon, California, or India.
In Business Administration, many of the terminology is used from region to region, such as "empowerment" or :MacGregor's Theory X and Theory Y" style management theories.
Standards help make sure people are on the same page and have common ground. They also go far beyond communication into the realm of good application design.
In terms of Google App Engine development, Google Engineers build sample projects that describe what they -- the technical experts on their platform -- believe is the best approach to building a scalable, extensible application... on their platform.
For Spring, the Spring developers post very detailed information in their documentation as well as in their blogs on how to approach situations, such as marshalling and unmarshalling objects from Java to XML/JSON and vice versa.
I know the other development platforms have similar standards.
When I want to know how to integrate with something a developer in our company built, I consult that developer, my colleague. When I want to know how to properly store an Entity object in the Google App Engine JDO datastore, I consult the Google Engineers who designed and built Google App Engine. If I want to know how to properly deserialize an object back to Java, and I'm using Spring, I consult the Spring development community.