search

adiwg / adiwg-metadata

Documentation and examples for ADIwg metadata profiles
The Unlicense
3 stars 0 forks source link

validation of example.xml #1

Open smrgeoinfo opened 8 years ago

smrgeoinfo commented 8 years ago

example won't validate because the schema location is a local path. I used http://ngdc.noaa.gov/metadata/published/xsd/schema.xsd as the schema location to try validating and gmd:taxonomy is invalid content. The schema extensions have to be defined in their own namespace and a separate schema location provided for that namespace to validate. (maybe the one on your local file system is set up to do that?) Still, bad practice to add you extension elements to a namespace that you are not the steward for....

stansmith907 commented 8 years ago

Can you tell me exactly where you found the XML example? Sounds like one from my development files that got away. Because of the time it takes to load the XSDs remotely I stash a copy locally for development purposes. The mdTranslator does specify the proper NOAA version of the XSDs. Looks like I need to patch the example with the proper XSD or remove it from public space.

The current NOAA XSD for ISO 19115-2 that includes the ISO_Bio profile is ftp://ftp.ncddc.noaa.gov/pub/Metadata/Online_ISO_Training/Intro_to_ISO/schemas/ISObio/schema.xsd. Last time I checked (about 6 months ago) this was still the preferred distribution point according to NOAA.

stansmith907 commented 8 years ago

The example on the adiwg-metadata documentation repo has been updated.

smrgeoinfo commented 8 years ago

I'm looking at the example at https://github.com/adiwg/adiwg-metadata/blob/master/iso/19115-2/examples/ADIwg_ISO_19115-2_Example.xml I'll grab that other schema (it imports gmd and srv from local paths--its the same file as I was using in a differnt location, buty maybe the gmd and srv xsd's there are different (they shouldn't be ....)

stansmith907 commented 8 years ago

The biological extension is embedded in gmd namespace. So I would guess the ISObio gmd xsd is extended.

smrgeoinfo commented 8 years ago

almost there-- there's a duplicate gml:id (they need to be unique in the scope of the xml doc) just change one of the timeperiod030 to something else (e.g. timeperiod031).

stansmith907 commented 8 years ago

Hey Josh - Looks like the v1 schema example 'full_example.json' used to create the example placed in the documentation folder has two timePeriods with id = 'timePeriod030'. Looks like the same block may have been copied to multiple temporalElements. 'full_example2.json is OK. Not sure why we have to full_examples?

I use a separate full_example in development since the schema examples necessarily lag development.