OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: namespace URIs


I had an action item on this.

OASIS namespace policies are outlined here:

<http://docs.oasis-open.org/specGuidelines/namingGuidelines/ 
resourceNaming.html#NamespaceDesign>

Elias had a strawman URI in his ontology of <http:// 
opendocument.xml.org/2007/03/meta-manifest/ns>. If we could do that,  
I actually think that would be good (though should "meta-manifest" be  
"meta/manifest"?).

The key point is this:

"HTTP scheme namespace URIs should be rooted at http://docs.oasis- 
open.org/[TC-shortName]/ or (preferably) at [TC-shortName]/ 
[productName]/ — or possibly otherwise, as negotiated with TC  
Administration"

If we go with the preferred option above, that perhaps suggests  
something like:

	manifest --> <http://docs.oasis-open.org/odf/meta/manifest>
	meta --> <http://docs.oasis-open.org/odf/meta>

Integrating Elias' W3C best practice approach with the dates included  
would instead yield something like this I guess:

	manifest --> <http://docs.oasis-open.org/odf/2007/03/meta/manifest>
	meta --> <http://docs.oasis-open.org/odf/2007/03/meta>

The "other" option is basically whatever we want; the example is  
DocBook's "http://docbook.org/ns/docbook"; namespace URI.

The point I was making about a forward-looking schema is just that it  
would be nice if the namespace URI for the basic meta prefix stuff  
would resolve to a page from which further links could direct people  
to other documentation resources.

Bruce



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]