[esip-semanticweb] ESIP namespace definitions

[Christopher Lynnes]

We are now beginning to actually implement cross-ESIP applications  
that have need of namespace declarations, specfically:
o  Federated search
o  Machine tagging of WMS capabilities documents
I believe there are some semantic web applications that are not too  
far behind...

Given that permanence is a desirable feature of namespace  
declarations, I would like to propose we settle on a definition scheme  
that can be implemented soon, but which we expect to be stable.

I would like to suggest we use a scheme like:
http://esipfed.org/ns/foo/bar

where
o  http is the scheme
o  esipfed.org is the authority
o  ns indicates that it is a namespace
o  foo/bar is a hierarchical path

Examples of foo might be:
o  fedsearch
o  scast (for servicecasting)
o  datatypes

So for example, to uniquely identify a URI as refering to a URL to a  
browse image (useful for typing in Federated Search) responses), we  
might have:

http://esipfed.org/ns/fedsearch/browseImage

One minor downside to this scheme is that it is often useful, but not  
required, to put an informational document, such as a schema document,  
at the URI.  Brian, would this be feasible?  Again, I don't believe it  
is required for a namespace URI.

Any counter-proposals?
--
Christopher Lynnes             NASA/GSFC, Code 610.2          
301-614-5185