Re: namespace convention

[Mary McRae <marypmcrae@gmail.com>]

Hi Dave,

  You should see the Artifact Identification Requirements coming out
for public (member) review in a week or two, but basically here's the
info.

Regards,

Mary

On 6/10/05, Cruikshank, David W <david.w.cruikshank@boeing.com> wrote:
> Mary,
> 
> I just wanted to confirm the result of our discussions.  I think there may be some confusion on this issue.
> 
> There are 2 potential locations to be addressed:
> 
> 1)  url reference for the namespace declaration in our XML DTD - This one is just a url defining the domain for the namespace.  It doesn't necessarily even have to resolve, but we might want to put a generic page in place to explain that it is the namespace domain for WebCGM.  I don't think this one should be version dependent. It's just declaring the domain space.
> 
URLs or URNs (not both).

URLs. It will be left to the TC's discretion if there will actually be
something at the other end of a URL namespace.

The URL namespace will take the form of:

{oasis domain}/{spec-id}/schema/{schema filename}

If the TC instead chooses to use a URN for the namespace, it will take
the form of:

urn:oasis:names:
followed by two variations:
tc:{tc-id}:{type}{:subtype}?:{document-id}
or
specification:{specification-id}:{type} {:subtype}?:{document-id}


> 2) url reference to the location of XML DTD's or Schemas that resolve to the actual parsing instructions for an instance.  This one needs to be resolvable and points to the actual DTD or Schema file.  It may be version dependent if the DTD changes versions.
> 

Persistent URLs will take the form of:
docs.oasis-open.org/webcgm/v2.0/{filename.ext}

or, if the TC prefers:
docs.oasis-open.org/webcgm/v2.0/schema/{filename.ext}

> Can you clarify any OASIS conventions for each of these.
> 
> thx...Dave Cruikshank
> 
> Technical Fellow - Graphics/Digital Data Interchange
> Boeing Commercial Airplane
> 206.544.8876, fax 206.544.9590
> david.w.cruikshank@boeing.com
> 
>