Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Mon, Jan 06, 2003 at 08:01:05PM -0500, Simon St.Laurent wrote: > ziggy@p... (Adam Turoff) writes: > >I've heard the praise and hype for HyTime and out-of-line linking, > >but I can't say as I've seen a single practical need for it. What > >would a sensible out-of-line linking language provide that > >SkunkLink+RDF (or the moral equivalent) *can't* provide? > > My primary problem with RDF, XLink, and their current moral equivalents > is their obsession with URIs as magic identifiers. I've stated a number > of times that I find working with RDF quite painful because it seems to > believe that URIs are the one true identifier for everything, and so I'd > much prefer to work with a dedicated linking vocabulary - but then I > also find that XLink is not a very good linking vocabulary. I don't see that as an objection against the moral equivalent of SkunkLink+RDF as a replacement for XLink. I see that as an objection to using RDF per se as half of that combination. :-) Suppose there was a SkunkOOL vocabulary that used tag names to specify a certain class of out-of-line relationships. The only URIs would be the resources being linked through xml:href and xml:src attributes. Would such a vocabulary be a sufficient replacement for XLink for out-of-line linking? <ool:document xml:href="http://www.example.com/foobar/"> <ool:title>Welcome to FooBar Industries</ool:title> <dc:creator>...</dc:creator> <ool:schema type="wxs" xml:href="http://www.example.com/foobar.xsd"/> <ool:schema type="rng" xml:href="http://www.example.com/foobar.rng"/> <ool:stylesheet type="css"> xml:href="http://www.example.com/foobar.css"/> <ool:stylesheet type="xsl"> xml:href="http://www.example.com/foobar.xsl"/> ... </ool:document> Z.
|
