Lists Home |
Date Index |
- From: Peter Murray-Rust <email@example.com>
- To: "Xml-Dev (E-mail)" <firstname.lastname@example.org>
- Date: Fri, 29 May 1998 18:10:34
At 15:21 29/05/98 UT, Simon St.Laurent wrote:
>How will XSchema use/relate to RDF?
[... Simon's analysis snipped ...]
First let me say that I am a supporter of RDF and have used it in my
specimen documents to the best of my knowledge.
I share Simon's concerns about RDF. Firstly I don't fully understand it -
and certainly not how it will be used. For example, are there any working
RDF documents other than the examples in the draft? Secondly, there is no
software for authoring or reading it. Of course there *will* be, but the
timescale is important. Let us say that we finish XShema in a month (cf.
SAX). Suppose it were all in RDF - what would most people actually do with
it? But my main concern is that it will detract from the simplicity of the
proposed XSchema (or my assumption of the simplicity :-)
If I write:
<Seq optional="yes" repeatable="yes>
this is - at present - everything *I* need. What would I need above this?
If it is recast as
it gets more complex and I don't immediately see the payoff. Since I shall
probably be initially authoring XSchemas by hand (sic) it needs to be
obvious what to write.
I can see that an XSchema2RDF converter might be algorithmically possible.
I appreciate that this may appear simplistic, but I have consistently taken
the line that XML should be kept very simple - I already think there are
bits which will hardly ever be used. We can always add more layers later.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
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)