[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cgmo-webcgm] Re: namespace convention
Lofton said:
==================================================================
> ...we were
> thinking of doing something like SVG and some other W3C standards. Its
> namespace URL is:
>
> http://www.w3.org/2000/svg
>
> and that resolves to a little HTML document, which contains the W3C logo
> and the text:
>
> >This is an XML namespace defined in the Scalable Vector Graphics (SVG) 1.0
> >Specification. The latest version can be found http://www.w3.org/TR/SVG.
> >
> >For more information about SVG, please refer to the W3C SVG overview. For
> >more information about XML, please refer to The Extensible Markup Language
> >(XML) 1.0 specification. For more information about XML namespaces, please
> >refer to the Namespaces in XML specification.
==================================================================
Mary can tell you something more authoritative, but I think the (new)
OASIS rules will let you put a RDDL Namespace Document at the
end of the namespace URI, so that you get the RDDL if you
dereference it.
This is becoming more common now, since the W3C TAG (lightly)
approved this strategy; see http://xml.coverpages.org/rddl.html
For RDDL version 2.0:
..."This document is a working draft that contains substantial
input from the W3C Technical Architecture Group, produced in
connection with the work on its issue namespaceDocument-8. It
is the consensus of the TAG that RDDL is a suitable format for
use as a 'Namespace Document', that is to say as a representation
yielded by dereferencing a URI in use as an XML Namespace Name.
While this document has no official standing, it is the intention
of the TAG to seek guidance from the W3C membership and the larger
community on the question of whether and how to progress this
document and the use of RDDL..."
And here's an example from the Web Single Sign-On (SSO)
Identity Specification recently co-published by Microsoft and
Sun:
The XML Schema:
http://schemas.xmlsoap.org/ws/2005/04/ssi/WebSSOMEXProtocol.xsd
The Namespace URI:
http://schemas.xmlsoap.org/ws/2005/04/ssi
*dereference it: resolves to the XHTML RDDL document, which looks like
many of the other RDDL Namespace Documents (online) because it uses
the CSS stylesheet from the RDDL web site:
Note: xmlns:rddl="http://www.rddl.org/
link href="http://www.rddl.org/xrd.css"; type="text/css"
<html xmlns="http://www.w3.org/1999/xhtml";
xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:rddl="http://www.rddl.org/";
xml:lang="en" lang="en">
<head>
<title>Web Single Sign-On Interoperability (WebSSO Interop)</title>
<link href="http://www.rddl.org/xrd.css"; type="text/css" rel="stylesheet" />
On Fri, 10 Jun 2005, Lofton Henderson wrote:
> I'm still a little confused. SInce I'm trying to edit the spec now, can
> you clarify about the URL for the namespace declaration?
>
> At 04:00 PM 6/10/2005 -0400, Mary McRae wrote:
> >[...]
> >On 6/10/05, Cruikshank, David W <david.w.cruikshank@boeing.com> wrote:
> > >[...]>
> > > 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}
>
> From this I gather something like:
>
> http://www.oasis-open.org/webcgm/schema/{schema-filename} or
> http://www.oasis-open.org/webcgm2005/schema/{schema-filename} or
> http://www.oasis-open.org/webcgmXCF/schema/{schema-filename} or ...
>
> I put in the webcgm2005 to illustrate a possibility and a point. The 2005
> is not a version, but is basically the year the namespace URL went into
> use. It is a convention from my years in W3C. It is not desired that it
> be updated for versions, and in fact it is detrimental (to implementors and
> interoperability) if it is updated for versions.
>
> We can live without it (the "2005"), IMO (but I'm not claiming to speak for
> everyone.)
>
> QUESTION. What is implied by "schema filename"? Are you saying, if the
> address resolves to anything, then must resolve to a schema? We were
> thinking of doing something like SVG and some other W3C standards. Its
> namespace URL is:
>
> http://www.w3.org/2000/svg
>
> and that resolves to a little HTML document, which contains the W3C logo
> and the text:
>
> >This is an XML namespace defined in the Scalable Vector Graphics (SVG) 1.0
> >Specification. The latest version can be found http://www.w3.org/TR/SVG.
> >
> >For more information about SVG, please refer to the W3C SVG overview. For
> >more information about XML, please refer to The Extensible Markup Language
> >(XML) 1.0 specification. For more information about XML namespaces, please
> >refer to the Namespaces in XML specification.
>
> While this little file mentions 1.0, in fact SVG 1.1 and 1.2 all use the
> same namespace URL, and each of them has a section saying that.
>
> As I said, we were thinking -- if the namespace URL resolves at all -- that
> it should resolve to something like this, and not a schema or dtd.
>
> So ... how to wrap this up so that we can have an operational namespace URL
> asap?
>
> Thanks,
> -Lofton
>
>
>
>
>
>
>
>
>
>
>
>
--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]