Lists Home |
Date Index |
Using the namespace to change the interpretation logic is an old trick ;
RDDL allows to add a level of indirection. In that sense RDDL does perfectly
matches the need of a Namespace Description Language (well, letting the
human-readable documentation quirks aside).
But there are cases in which you don't want to handle each namespace
independently, but consider a document mixing namespaces as a whole, not as
a patchwork of elements from various namespaces.
Validating a RDDL document implies using the RDDL DTD, which integrates tags
from different namespaces, right ? I can validate a RDDL document with its
DTD, because the DTD location is specified in the DOCTYPE. If I want to
validate it using, say, the RELAX NG schema that you provide, I can't find a
way to automatically fetch the RDDL document for a RDDL document and get the
resource with the 'http://www.xml.gr.jp/xmlns/relaxNamespace' role, because
RDDL are found at namespace URLs, but my RDDL document is not bound
specifically to the RDDL namespace.
That's why I suggest to split the spec in two : one spec trying to answer
the 'riddle' (I got it, now :) "what's at the end of a namespace URL", and
another trying to solve the serious problem of a generic way to associate
meta-data to XML document without making them crowded with DOCTYPE,
xsi:schemaLocation, stylesheet PIS (which are a bad idea, BTW) and other
>De : Jonathan Borden [mailto:firstname.lastname@example.org]
>Envoyé : vendredi 18 janvier 2002 17:04
>À : Nicolas LEHUEN; 'Elliotte Rusty Harold'; 'Paul T'; 'Bullard, Claude
>L (Len)'; 'Leigh Dodds'; email@example.com
>Objet : RDDL and XML element behaviors was: Re: [xml-dev] RDDL (was RE:
>[xml-dev] Negotiate Out The Noise)
>Nicolas LEHUEN wrote:
>> How do you handle the case of, say, a RDDL document, which
>> namespaces from XHTML, RDDL itself and XLink ? How could XSV
>> document for the RDDL document ? Please describe me the algorithm.
>A couple of points, RDDL _might_ be used in cases where an
>"xsi:schemaLocation" attribute might be present but isn't, and
>it is desired
>to locate a schema.
>Mixing namespaces: Suppose an XHTML _renderer_ hits some SVG
>or MathML in a
>document. Suppose that the creators of the SVG and MathML
>namespaces want to
>support all of the IE, Netscape, Java based etc. renderers. An XLink
>pointing to the location of each of the renderers for each of
>(i.e. plugins) is placed in the RDDL for the respective namespaces. The
>renderer/client might then be able to locate some software capable of
>displaying elements in the namespace.
>Microsoft already has a solution to this problem: namespace associated
>behaviors. It is an excellent solution except that it is
>specific to the IE
>browser. RDDL is _a_ way to allow the designer/creator of the
>support multiple platforms if so desired i.e. a platform neutral way to
>associate 'behaviors' with namespace qualified XML elements.