Lists Home |
Date Index |
- From: Paul Prescod <email@example.com>
- To: "Xml-Dev (E-mail)" <firstname.lastname@example.org>
- Date: Sat, 30 May 1998 07:02:38 -0400
Peter Murray-Rust wrote:
> In this way we shan't be held back. If xschema.xsc and xschema.rdf are
> algorithmically transformable, then this could be a starting point.
This is an important point. HyTime is another system for describing
relationships between resources, and could thus be used to attach
properties to resources. But because it uses architectural forms, authors
don't need to know anything about HyTime to use it. Only document type
designers must know about it. The XML world has so few document types that
hardly anybody worries about this problem yet. But they will...
What we have here is a perfect example. We want to make a language that is
optimized for our user community. We want that language to also be an RDF
application. Those two goals seem to be in conflict, because RDF seems to
require you to embed RDF specific elements into any document that uses
RDF. We would rather have the document use RDF indirectly through some
sort of transformation specified by the small set of experts in this
I could imagine that being handled by a RDF:role attribute that could be
defaulted in the DTD, by RDF:Role processing instructions, through a
reference to some kind of transformation language, etc.
How do the RDPhiles intend for this situation to be handled in general?
Paul Prescod - http://itrc.uwaterloo.ca/~papresco
Three things see no end: A loop with exit code done wrong
A semaphore untested, and the change that comes along
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)