social media
User login
Popular Domains
AIP-4
AIP4
AIP GEOSS
AIP Telecon
AIP Telecon 2011/05/31
Application Schema
climate
csw
EarthCube
GEOSS
GEOSS AIP
GEOSS AIP-4
GIS
gml
hydrology
IoT
Java
observations and measures profile
OGC
ogcdoc
ogcdoc standards status
OGC Web Services
ows8
sensorml
Sensor Web
sld
SOS 2.0
sps
swe
testbed
waterml2
weather
wfs
wms
wps
xml
delicious OGC
- worldwindrcp - Google Code
- i-Scope - Interoperable Smart City Services (current)
- Web Geoservices for monitoring the Environmental Impact of Large Structures (2010)
- http://tws01.terranovaws.it/osiris/hws.asp
- Advances in 3d Geo-information Science (2011)
- CAAD-GIS Interface – Conversion of IFC Models into CityGML Models (2008)
- Service-oriented Visualization of Virtual 3D City Models - Directions Magazine
- GeoBolivia - colaboración con OSGeo y OGC - Proyectos de software libre estandardizados - Bolivia
- Service-oriented Visualization of Virtual 3D City Models (2011)
- Zoo - The Powerful WPS Platform (2011)
- Drift-X WPS: Pesticide atmospheric dispersion Web GIS (2010)
- OGC Document Catalog | OGC Network 2012
- YouTube channel for OGC related videos (2010 to present)
- Find the Data You Need
- Open Source Software and OGC Web Services: Life-saving Components in Québec's Emergency and Disaster Management - Directions Magazine
Per the GML 3.2.1 editor, GML
Per the GML 3.2.1 editor, GML 3.2.1 "will only validate if you
validate gml.xsd (the root schema document)." One reason for this is
due to the number of deprecated components.
For a similiar discussion, see http://www.ogcnetwork.net/node/1161
Cheers,
kevin
Hi, I just starting to face
Hi,
I just starting to face the same problem. In my opinion this is a problem that is worth looking at, the validation errors show up because components that are not included/imported are referenced from several GML schema files (gmlBase, dictionary and units). If the reason why these components are not included is because they are deprecated, why the references to them were not deleted? The schemas containing the references are then inconsistent whether you use or not gml.xsd to validate some XML instance file: what happen if an element or attribute for these "not included" types or elements is declared in the instance file?
About the fact that that GML 3.2.1 "will only validate if you validate gml.xsd (the root schema document)." it does not work if option "http://apache.org/xml/features/honour-all-schemaLocations" is true when trying to validate Xerces-J. It reports 910 errors including the ones resulting for validating the files mentioned above directly. Interestingly, this option should consider all repeated imports for the same namespace in a file, fact that at first sight is not happening in any of the schemas in GML or the ISO folder (I'm working with a local copy of the schemas)
Best Regards
Alain
The deprecated components are
The deprecated components are included for backwards compatibility, but there were comments in the revision process that ask to separate the deprecated components as clearly as possible. This is why it was separated in its own schema document.
With hindsight, all schema documents should have an include statement that includes gml.xsd to avoid errors being reported when someone tries to validate some GML schema document that is not gml.xsd (which does not make sense according to the XML Schema spec). This is what we plan to do in the future in such cases.
In the schema document design we have to support all valid options for determining the schema of a namespaces allowed per the XML Schema spec (http://www.w3.org/TR/xmlschema-1/#schema_reference). As a result, all schemaLocation references in instances and in imports must go to gml.xsd to make these options consistent with each other. I do not know how the honour-all-schemaLocations feature of Xerces-J has been implemented, but if it correctly identifies duplicate schema components when it loads the same schema document multiple times, then this should work (although probably be slower), so I do not know what the issue is without looking closer at the Xerces implementation. In any case, this feature is not needed when validating GML schemas/documents and should be left in its default state ("false").