Lists Home |
Date Index |
- From: "Sean B. Palmer" <email@example.com>
- To: Tim Bray <firstname.lastname@example.org>, email@example.com
- Date: Sat, 30 Dec 2000 22:17:04 +0000
> 1. a few basic chunks of XHTML
> 2. the simple XLink element (I don't think you need extended, and
> by using simple you could graft the whole thing onto an XHTML
> <div> or some such).
> 3. a namespace in which are defined a bunch of reserved
> role attribute values
Blimey, this is a good idea...
But it would require fast and consistent work. Also, I think this is
something that should be taken up by a W3C WG, rather than a humble DEV
mailing list. FWIW, I believe that this is a good aproach, and would itself
rely on namespaces (quite bizarre), but I don't seriously think it will
ever come to fruition. I suppose you are aiming at something like:-
<title>Namespace Schema for: MyLang</title>
<link rel="schema" ns:type="syntactic schema" xlink:href="schema.xsd" />
<link rel="schema" ns:type="presentational" xlink:href="present.xsl" />
<p>My lang has an <a href="[...]">XML Schema</a> and a [...]</p>
<div>By <a href="mailto:[...]
> I think this would be the ideal kind of thing to retrieve
> when you dereference a namespace URI. Readable by humans
> and also machine-processable and fully extensible.
> If I were feeling particularly grandiose, I'd also describe
> such a thing as a key building block for the Semantic Web.
Sean B. Palmer
"Perhaps, but let's not get bogged down in semantics."
- Homer J. Simpson, BABF07.