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


Help: OASIS Mailing Lists Help | MarkMail Help



   [xml-dev] extending XHTML

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org
  • Subject: [xml-dev] extending XHTML
  • From: Carlin Rogers <carlin.rogers@gmail.com>
  • Date: Wed, 15 Jun 2005 08:47:14 -0600
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jgmMeVCMqWZ/ZohhufkBTbnK61PkSuNZPolHoId/cPYenEN6KeXSjPT/vwds/Njb1B33hJrbqsAbt2KCyuvYX+0Ib5A+sSA9HLv3mrS/B4stvskDcxUbUpZs2kSUxZipoo01abJ8vDgFADO/6oU4Von/ThirEkDLPYNkeIWttl4=
  • Reply-to: Carlin Rogers <carlin.rogers@gmail.com>

I hope this is kind of question is appropriate for this list. If 
not, please suggest a list that might help me find a solution.

I've have been unable to find a way to extend XHTML such that the 
document output from an application framework validates correctly.

The documents will include extra attributes on a small subset of
elements, like div. I'd like to avoid creating a custom DTD so
I've been using an internal subset of the DOCTYPE declaration.
For example, something like...

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  <!ATTLIST html
      xmlns:netui CDATA #FIXED "http://beehive.apache.org/netui/tags";
  <!ATTLIST div netui:treename CDATA #IMPLIED>
<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml";
      xmlns:netui="http://beehive.apache.org/netui/tags"; >
    <div netui:treename="Tree101">
      Stuff Here

...where the div tag has the treename attribute from the
XML namespace, "netui" and the html element has the
attribute to declare the xmlns. This is a valid document.

The unfortunate problem in creating documents like this is
that they don't display correctly in IE. The browser
displays a leading "] >" at the top of the document. 

Are there other alternatives for this solution, other than
supporting and providing a custom DTD, such that the document
will both validate and display correctly? 

Thanks for your help. Kind regards,


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

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