[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> -----Original Message-----
> From: Paul Prescod [mailto:paul@prescod.net]
> Sent: 06 June 2002 22:23
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Can RDDL and RDF coexist?
>
>
> I am not entirely satisfied with the answers to Roger's question.
Sorry to hear it.
> Let's say I am working my way through a maze of hyperlinked
> RDF/XML documents.
You've already moved outside of RDF. RDF doesn't have any notion of
hyperlinking. That some RDF constants might have a retrievable RDF
schema at the end of them is a happy coincidence (unless you're
Patrick ;)
The thing to do is keep the code that reasons about the graph
separate from the code that streams information into the graph.
>I come upon a new namespace I've never
> seen. I want to figure out the semantics of that namespace,
> especially if there is a chance that it is an extension of
> one I already know and understand. Therefore I want to get
> from the document to its schema definition(s).
If you're a person rather than a piece of software, you can type
the URL into a browser or wget and see what comes back. This is
much the same kind of thing people do to understand RDF literals,
they read them and infer what to do. Web hyperlinking shouldn't
really care what's at the end of a link, so long as it has a
mimetype. RDF is more restricted. Without a processing model, local
conventions and pragmatism will apply.
> I think that following the namespace is a reasonable way. How
> do the various assembled luminaries propose to do this?
Throw an exception to the application, let the application figure
out what to do (ie try a GET, page an admin), let it stream back
triples to the graph. But do not have an RDF processor parsing into
the URI refs, leave that to web code.
Bill de hÓra
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPQDIMOaWiFwg2CH4EQJ20gCgsHTPat2xreTFINmdHpvul1ySdEkAnjzM
Hmarb4MqbSsd+IFpx6vrZqfS
=lzsH
-----END PGP SIGNATURE-----
|
