Troubleshooting Web Service Deployment - Blog
If you are deploying a OneGeology WMS, please visit: http://onegeology.org/wmsCookbook/home.html for more detailed requirements. For AASG naming conventions, please visit this link
Discussion of using the “lax” function in Schema Documents
We’ve recently changed how we are structuring our XSD schemas by adding a “lax” process function element at the end of the sequence. The ‘lax’ function, or ‘any Element’ function, can be specified by the author of the schema document, and enables additional elements not specified by the schema to be included.
Testing your Web Services using Non-Proprietary GIS Software (uDig)
Validation of XML data interchange documents with normative schemas using free, open-source software (XML Explorer)
One of the objectives of the US Geoscience Information Network (USGIN) is to establish a community of practice for developing, documenting, adopting, and using standard document encoding for data interchange. The technology for encoding schemes is evolving continuously, and current practice is to use XML encoding with data schema defined by XML schema.
If you decide to use GeoServer to deploy your Web Services, you will find that part of the process includes creating an SLD or Styled Layer Descriptor for portrayal of the data you intend to publish. A natural symbology for such layers is an ESRI layer file format. Using this format initially presented a problem, though; creating an SLD for data with a complicated symbology scheme, such as a geologic map, is not trivial using XML editing software-- even if you have a template to work from. Many times, conversion from RGB to Hexidecimal is required for each entry in your symbology layer. Even if one uses a built-in formula converter in Excel (or from various websites), a large amount of hand entry is still required.