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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Mapping XHTML to XLink via Architectural Forms

[ Lists Home | Date Index | Thread Index ]
  • From: Jonathan Borden <jborden@mediaone.net>
  • To: "Simon St.Laurent" <simonstl@simonstl.com>, xml-dev@lists.xml.org
  • Date: Fri, 27 Oct 2000 14:07:12 -0400

Simon St.Laurent wrote:
>
> _Should_ attributes like this be 'global' attributes?  It seems odd to me
> to have XLink doing such work for linking while leaving STYLE on a
> case-by-case basis.
>
> I definitely _don't_ want to see STYLE or style made into an effectively
> reserved word within local names.
>

We agree. The way I see it, namespaces are the easiest way to prevent this
from happening, that is for new applications "x:style" is a better option
than "style" (btw: by 'global attribute' do you mean a non namespace
prefixed attribute?), for XHTML of course interop with HTML limites the
choice of names and AFs are the simplest way to map the attribute "style" ->
"html:style".***

Jonathan Borden
The Open Healthcare Group
http://www.openhealth.org


*** using xml:attribute="html:style style" is essentially an AF renamer-att,
the only difference being that AFs are defined, i.e. have a defined API
whereas xml:attribute needs to be implemented, though this could be done
fairly easily via a SAX filter.






 

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

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