Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Should xlink:arcrole or xlink:role be the primary way todispatchon r
"Jason Diamond" <jason@i...> writes:
> > I was with you right to this point. I have exactly the opposite
> > inclination, namely that the xl:role is all I normally will need to
> > look at. If I'm a schema validator, I'm going to special-case
> > situations in which there is only one resource with xl:link=the NS uri
> > for the schema language I validate with. Release 1 will probably punt
> > all other situations. I _really_, _really_ want to get to the point
> > where I can have the bare minimum to declare victory, namely:
>
> I can sympathize with this but think that the ability to further constrain
> resources using well-known arcrole URIs as Thomas' example showed offers
> almost unlimited flexibility without adding that much complexity.
>
> I suspect that all RDDL APIs (regardless of what language they're
> implemented in) will provide means to retrieve resources by role, arcrole,
> or a combination of both.
>
> >
> > <html xmlns:html='.../xhtml'>
> > . . .
> > <rddl:resource xl:type='simple'
> > xl:role='http://www.w3.org/2000/10/XMLSchema'
> > xs:href='http://www.example.com/Schemas/myns.xsd'/>
> > <rddl:resource xl:type='simple'
> > xl:role='http://www.w3.org/1999/XSL/Transform'
> > xs:href='http://www.example.com/Stylesheets/myns.xsl'/>
> > <rddl:resource xl:type='simple'
> > xl:role='http://www.w3.org/1999/XML/namespace'
> > xs:href='http://www.example.com/DTDs/myns.dtd'/>
> > . . .
> > </html>
>
> I imagine most directories will look like just that. GetResourceByRole (or
> whatever) could be used with no problem. If there's a XSD or DTD in there,
> you could probably reasonably assume that you should validate an instance
> document with it. But what does the transform do? Does it render an instance
> as HTML/FOs? Does it scrape the document for RDF/RSS? Or does it have some
> other purpose that I can't even imagine today?
>
> Without arcroles, your namespace can only be effectively "associated" with
> one stylesheet using RDDL. There's no problem adding a second resource with
> an XSL role to the directory--but how would you know which stylesheet to use
> when dereferencing the namespace without some means of disambiguating the
> two? This is where GetResourceByArcrole or even GetResourceByRoleAndArcrole
> would come in handy.
I agree with all of the above, just want to be sure GetResourceByRole
is not lost in the noise of the others, which doesn't sound too
likely, so I'm content.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@c...
URL: http://www.ltg.ed.ac.uk/~ht/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
