[Smwg] namespace registry

John Pietras john.pietras at gst.com
Mon Jun 22 15:30:30 UTC 2015


SMWG colleagues ---
During last week the CSSMWG telecon, we discussed the SANA registries that would have to be in place by the time that the Simple Schedule book is published. During the discussion of the XML schema registry, I side-tracked the conversation for a bit (for which I apologize) about whether the request to SANA for an XML schema registry needs any further action on our (CSSMWG) part at this time. We concluded that the request for the SCCS-SM Information Entity XML Schema registry that Colin had submitted to SANA puts the next action on SANA.

However, there *was* something that was bothering me in the back of my mind - the need to register the  URN namespaces used by the schemas.

The XML schemas used by the Simple Schedule are defined in three namespaces: 'urn:ccsds:schema:cssm:smInfoEntHeader:1.0.0', 'urn:ccsds:schema:cssm:ccsdsTimecodes:1.0.0', and 'urn:ccsds:schema:cssm:simple_schedule:1.0.0'.

There is a candidate SANA URN Namespace (http://sanaregistry.org/r/urn/urn.html), which was last updated on 15 December 2014. All of the namespaces listed in that registry are still listed with a Status of 'Provisional' (presumably because the registry itself is still only a candidate), including  the NDM XML schemas namespace (given that the NDM XML schemas are normative and published elsewhere by SANA, I think that the namespace is well past being merely provisional).

In any case, I believe that there is an additional action needed to get our three namespaces added to the SANA CCSDS URN registry, and to understand what needs to happen to get that registry actually approved .

A final note - the namespace registry has a Reference column. All but the NDM XML namespace has a reference of CCSDS 315.1-Y-0, and the NDM XML namespace entry has no Reference supplied. Should we use the Simple Schedule Book as the reference document for our three namespaces?

Again, my apologies for fumbling this topic when we discussed it last Thursday.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/0b627cb6/attachment.html>


More information about the SMWG mailing list