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] Rethinking namespaces, attribute remapping (was Re:[xml-de

[ Lists Home | Date Index | Thread Index ]

Hi Dare,

Dare said:
<html xmlns="http://www.w3.org/1999/xhtml";
hlink:definition=http://www.example.org/whatever...
 
Advantages: Modular, easy for Joe Blow to use without understanding how
it works
Disadvantages: Security issues, information necessary to process
document no longer self contained
 
Didier replies:
I am not so sure about if what you said as an advantage is really one. I
tested with a real joe Blow (i.e. somebody that knows a bit about XML
and a lot about HTML) and he got some difficulties to grasp the mapping
process. It is probably easier for someone used to object inheritance as
commonly used in object languages or to someone who learned about
architectural forms :-)

I have also some questions. 
a) Would this implies that XSLT 2.0 should support such mapping in order
to be able to process documents. For instance, to match with a link
element and be aware that in fact, it should match with an object
element (which is mapped to a link element)?. 
b)Would this imply that XSLT 1.0 is broken when we think of processing
XHTML 2.0 documents (with the Hlink mapping)?
c) if the mapping document is external to the document to be processed,
why then not use a DTD including architectural form declaration to
perform the mapping?
d) are slowly following a path where documents are no longer self
sufficient?
e) have reached the limits of the original axioms?
f) Are we brain damaged? :-) :-), just kidding :-)


Cheers
Didier PH Martin





 

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

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