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


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] Simplest Namespace That Could Possibly Work

Eliot Kimber wrote:

> There may be a blindly simple way to solve the 1.0 namespace issue:
> Have a namespace-bound schema that defines only the DITA class attribute.

Using the latest DITA schemas from Eric I have implemented this approach 
and tested it a little bit (I'm about out of time today). It only 
required declaring a separate XSD for the qualified class attribute:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'


And then changing all the lines of the form:

<xs:attribute ref="class"


<xs:attribute ref="dita:class"

In all the .xsd and .mod files.

I also had to declare the ditabase namespace and import the little 
schema shown above in each .xsd and .mod file.

No other changes required as far as I can tell.

In instance documents, all element types would continue to be in no 
namespace, with only the class attributes in a namespace.

Like I said in my initial post, this would completely satisfy my desire 
that documents declare the DITA namespace and would otherwise leave 
existing DTDs and schemas, and the existing specialization and 
DTD/schema modularization mechanisms, unaffected.


W. Eliot Kimber
Professional Services
Innodata Isogen
9390 Research Blvd, #410
Austin, TX 78759
(512) 372-8122


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]