OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] namespace reprise

[ Lists Home | Date Index | Thread Index ]

> From: Emmanuil Batsis (Manos) [mailto:mbatsis@humanmarkup.org]
> Sent: Wednesday, August 21, 2002 3:43 PM
> To: Julian Reschke; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] namespace reprise
>
>
> Julian Reschke wrote:
>
> >>Julian Reschke wrote:
> >>
> >>
> >Old discussion from when XHTML 1.0 came out. It has a single
> namespace name,
> >but multiple schemata.
> >
>
> You mean DTDs. I don't recall any normative schema provided with
> XHTML 1.0.
> But point taken and yes I don't like that, meaning one namespace
> corresponding to multiple document definitions. So perhaps we need a way
> to group node names under something like a namespace for processors to
> be able and make use of those (a browser for example). Personally, I
> would like the namespace to point to such a document definition and the
> element names (when appended to the namespace URI as fragment
> identifiers) to point to their type definition (the fragment of the
> document definition).
>
> Which sounds insane today.
>
> >>you haven't answered my question on how will processing of *old*
> >>documents break.
> >>
> >>
> >
> >Well, your new code will have to explicitly support both namespaces. In
> >XSLT, that's a nightmare.
> >
>
> Why? I don't usually hard-code stuff and in XSLT (as with anything else)
> you can initialize a variable with either namespace as a value; not
> exactly a nightmare.

In which case the XSLT code will either accept old documents or new
documents, but not both...






 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS