Andy said:
> I'm not clear what you mean by 'alongside' here. We only have one URI,
> the namespace URI, so we can only point at one thing. Does the namespace
> URI resolve to the XHTML which points at the RDDL or does the namespace
> URI resolve to the RDDL which points at the XHTML?
I thought we were talking about embedding the elements from the RDDL
namespace (the links to the various resources associated with the
namespace - RDFS, XSLT etc etc etc) _within_ the XHTML document, the
remaining content of which would provide a human readable description about
the namespace. This is what the RDDL spec itself does
http://www.openhealth.org/RDDL/
(Mind you my Netscape 4..08 browser barfs on trying to render it, but I'm
not suggesting that's a reason for not doing it!)
My interpretation only here (!).... but I understood Dan Brickley's
"alongside" suggestion to mean, if we can embed RDDL in XHTML then we can
also embed RDF/RDFS, so we could embed an RDF schema in that same XHTML
document. That would make an RDF Schema available to RDF-aware applicatons
"at the namespace URI" rather than as the result of following another
redirection (specified by the embedded RDDL).
Tom Baker said:
> > Could those goodies include translations? Rachel alluded to problems in
> > implementing this.
I'd have thought so? Haven't looked at RDDL closely enough to see whether it
deals explicitly with language but it sounds exactly the sort of thing it
should be used for.
Pete
|