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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Resource Gloss (Human Readable)

Charles Reitzel wrote:

 >> Actually, XML Catalogs came first, but I am part of the OASIS TC.
 > Sorry, I should have said "has been incorporated into".  Has it?

In effect, yes.

 > I guess my eyes were getting a bit blurry following the thread.
 > Reading more closely, you're missing the XLink role attribute
 > needed by some for NS resolution to multiple resources.  You're
 > after a more general purpose catalog usable for, say, bitmaps or
 > whatever.

Any XML entity, parsed or unparsed, can be mapped through a Socat/
XML Catalog.  But the mapping generated is unique.

 > My basic point would be that your job probably isn't done until you
 > do handle NS entities.  OTOH, RDDL probably isn't done until it can
 >  map PUBLIC IDs to SYSTEM IDs like XML Catalog (as others have
 > suggested in this thread).  Two 3/4 overlapping specs would be,
 > well, redundant.

OTOH it might be that the job of saying "What are the associated
for this namespace?" and "What is the local meaning of this
system id or public id?" are actually quite orthogonal, and should
be handled by separate mechanisms.

 > As an aside, I think the difference between PUBLIC IDs and NS URIs
 > is not important.  I checked the grammar for the NS "URI" and it is
 > a garden variety XML attribute value, not even a URI, URN, let
 > alone a URL.

In order to be xml-names correct, it has to be syntactically a URI;

 > I look at the production for PublicId (in XML, not
 > XML Catalog) and I see it has character set limitations (roughly
 > a-z,A-Z + comic book cursing).


 > To my mind, the discussion is all about a) deciding if a NS "URI" is
 >  an entity or not and b), if it is, what kind.  Personally, I think
 >  b) is a minor point until you decide a).

A URI labels a resource, which may have (MIME) entity bodies associated
with it.  A URI can't *be* an entity.

There is / one art             || John Cowan <jcowan@reutershealth.com>
no more / no less              || http://www.reutershealth.com
to do / all things             || http://www.ccil.org/~cowan
with art- / lessness           \\ -- Piet Hein