Project

General

Profile

Task #6053

MNDeployment #4247: EDORA (Environmental Data for the Oak Ridge Area)

Task #6047: Validate EDORA content against the ORNL Mercury schema

Update science metadata files to include ORNL schema type

Added by Chris Jones almost 8 years ago. Updated over 7 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Ranjeet Devarakonda
Target version:
Start date:
2014-08-19
Due date:
% Done:

30%

Story Points:
Sprint:

Description

Once the ORNL Mercury metadata schema is published at a permanent URI (like http://purl.org/ornl/schema/mercury/terms/v1.1), all of the instance documents that conform to this schema just declare so, such as:


...
/ornl:metadata

This unambiguous typing lets consumers of the file know exactly how to parse it.

Map_Counties_Surrounding_ORR_Land_Cover_Landsat_NLCD_30m_1992.xml Magnifier (7.54 KB) Ranjeet Devarakonda, 2014-08-29 17:32

History

#1 Updated by Chris Jones almost 8 years ago

  • Assignee changed from Ranjeet Devarakonda to Jim Green

#2 Updated by Ranjeet Devarakonda almost 8 years ago

Chris-I haven't heard back from purl.org folks about the domain registration request. So, I will have to proceed with Plan B that we discussed yesterday, i.e. to add direct location to the server where the XSD actually resides. Please see sample XML and let me know if this works?

#3 Updated by Chris Jones almost 8 years ago

  • Status changed from New to In Progress
  • Assignee changed from Chris Jones to Ranjeet Devarakonda

Hi Ranjeet,

I've looked over the XML instance documents attached. There's a couple issues to address:

1) We decided to go forward with the namespace string of 'http://purl.org/ornl/schema/mercury/terms/v1.0', and even though you haven't heard back from the purl.org folks yet, I don't see a problem with it. Skye is updating the CN indexing code to look for this namespace, and I'm adding it to the object format list on the CNs. So, a namespace of ornlmercury/schema/v1.0 will be problematic. Let's stick with the purl.org persistent URI, and trust that the registration process will be completed in time.

2) In XML instance documents, the schemaLocation attribute should have one or more pairs of URIs, separated by whitespace [1]. The first string in the pair is the namespace, and the second is a hint as to the physical location of the schema for that namespace. So, the documents need to be corrected to have the root element look like:


...

/ornl:metadata

Notice the single space between the namespace and the physical location. If you want the physical location hint to be a web URI, you could alternatively use:

xsi:schemaLocation="http://purl.org/ornl/schema/mercury/terms/v1.0 http://mercury-ops2.ornl.gov/metadata/schema/mercury-ornl-v1.xsd">

[1] See http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/#schemaLocation

#4 Updated by Laura Moyers over 7 years ago

  • Target version changed from Deploy by end of Y1Q1 to Deploy by end of NCTE

#5 Updated by Laura Moyers over 7 years ago

  • Target version changed from Deploy by end of NCTE to Operational

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)