Re: Should xlink:arcrole or xlink:role be the primary way todispatchon related resources? was Re: URIs, names and well known RDDL names,

[Jonathan Borden <jborden@mediaone.net>]

Thomas B. Passin wrote:

> Jonathan Borden writes, referring to my previous post on the useage for
title,
> role, and arcrole -
>
> > Let me also answer Jason's question about why ever have
xl:role=xl:arcrole:
> >
> > In some specific situations, the purpose and nature of a resource are
the
> > same, for example the main XML Schema: Its purpose is to be an "XML
Schema"
> > and it *is* an "XML Schema" so in this particular situation:
> >
> > xlink:title="XML Schema"
> > xlink:arcrole="http://www.w3.org/2000/10/XMLSchema
> > xlink:role="http://www.w3.org/2000/10/XMLSchema
> >
>
> May I respectfully suggest that the purpose "to be the main schema" is
> distinct from the nature of the resource "is an xml schema"?  I don't
think
> this is splitting hairs at all, I think it is a true conceptual
difference.
> And after all, the main schema could be an xmlschema, a RELAX schema, a
DTD, a
> TREX schema, and so on, while still having the purpose of being a main
schema.

Right, I am just trying to simplify the API, what I was thinking is that
generally we can write:

RDDLURL rurl = new RDDLURL(
                                "http://wherever.org/some-ns" // namespace
URI
                                "http://www.w3.org/2001/10/XMLSchema" //
xlink:arcrole or if null, xlink:role
                                );
InputStream xsdStream = rurl.getInputStream();

which in most situations is what someone wants.

Using your proposal -- which I think is fine btw, it just adds a little
complexity for the most common situation --:

RDDLURL rurl = new RDDLURL(
                                http://wherever.org/some-ns , // namespace
URI
                                http://www.rddl.org/arcrole#main-schema , //
xlink:arcrole
                                http://www.rddl.org/2000/10/XMLSchema //
xlink:role
                            );
InputStream xsdStream = rurl.getInputStream();

>
> I propose - or request - that this distinction be clearly incorporated
into
> the rddl rec, and that it be implemented with a set of URIs for "arcrole"
that
> are distinct from the URIs for "role".

    I agree with the distinction you are making and will incorporate this
into the next version of the spec.

    We've come to the agreement that the xl:role for XSD is properly
http://www.w3.org/2000/10/XMLSchema .

    Is there a URI you suggest we use as the xl:arcrole for an XSD or are
you saying that we should create one? (Remember that under most
circumstances the xl:arcrole alone can be used to disambiguate resources)
Perhaps we might use the URI of the specification itself?
...

> >
> > xl:arcrole="http://www.rddl.org/arcrole#imported-schema
> > xl:role="http://www.w3.org/2000/10/XMLSchema
> >
> > (for us, we do specifically intend to place some documentation of these
> > terms at the arcrole URI, so we'd actually prefer that its a URL :-)
> >
> I like the thought that you can get more info if you need to look at it.
As
> long as de-referencing it stays optional.
>
Certainly.

-Jonathan