<versionNumber>.gml.xsdLocation
: i.e. "/schemas/5.0/DDMS/gml.xsd"<versionNumber>.ism.cveLocation
: i.e. "/schemas/5.0/ISM/CVE/"<versionNumber>.ism.xmlNamespace
: i.e. "urn:us:gov:ic:ism"<versionNumber>.ntk.xmlNamespace
: i.e. "urn:us:gov:ic:ntk"<versionNumber>.ntk.xsdLocation
: i.e. "/schemas/5.0/NTK/IC-NTK.xsd"<versionNumber>.tspi.xmlNamespace
: i.e. "http://metadata.ces.mil/mdr/ns/GSIP/tspi/2.0"<versionNumber>.tspi.xsdLocation
: i.e. "/schemas/5.0/tspi/2.0.0/tspi.xsd"<versionNumber>.virt.xmlNamespace
: i.e. "urn:us:gov:ic:virt"<versionNumber>.xlink.xmlNamespace
: i.e. "http://www.w3.org/1999/xlink" The format of an xsdLocation should generally follow /schemas/<versionNumber>/schemaLocationInDataDirectory
.
Version-specific Notes:
Because DDMS 3.0.1 is syntactically identical to DDMS 3.0, requests for version 3.0.1 will simply alias to DDMS 3.0. DDMS 3.0.1 is not set up as a separate batch of schemas and namespaces, since none of the technical artifacts changed (3.0.1 was a documentation release).
Because DDMS 4.1 uses the same XML namespace as DDMS 4.0, resolving the XML namespace to a version will always return 4.1 (because it is newer). 4.0.1 is now an alias for 4.1, and warnings will appear when using new 4.1 components.
This class is intended for use in a single-threaded environment.
@author Brian Uri! @since 0.9.b
|
|