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] Namespaces and Schemas: Some Initial Findings andXSLTImplications

Paul Grosso wrote:

> At 18:38 2004-06-28 -0500, Eliot Kimber wrote:
>> The problem turned out to be that the topic2html.xsl style sheet is
>> written entirely against the class mappings, which is what it
>> should do, but because those class mappings are defined in the
>> schema equivalent of "fixed" attributes, Saxon doesn't see them
>> because the open source version of Saxon 8 isn't schema aware. Doh!
> I don't know any details, but it seems odd that you can't get saxon 
> to work with attribute defaults (I assume it doesn't matter whether 
> they are "fixed" or not).  You might want to shoot an email to 
> Michael Kay <mhk@mhk.me.uk> to see if you're missing something (or to
> see if he has near term plans to fix this).

> On the other hand, I'm tempted to say that, if this is true, Saxon 8 
> is broken and don't use it, but that's not a reason to change DITA. 
> There are other XSLT processors that work properly.

Mike is very clear that the free version of Saxon 8 is not schema aware 
and will not process schemas at all (as far as I can tell--it's possible 
I missed an option in my investigations yesterday). The commercial 
version, Saxon SA, is schema aware and will properly propogate the 
defaulted attributes. While I hate to pay for anything, I think Mike is 
certainly justified in trying to get back a little something for the 
huge amount of value he's provided to the world through Saxon.

The whole issue of defaulted attributes in XML is one of the XML Big 
Lies, namely the assertion that there is no markup minimization in XML. 
There isn't *except* for defaulted attributes. In thinking about it now 
this suggests that there ought to be a simple, schema-compatible, way to 
define attribute defaults that is separate from the larger function of 
defining data types and content constraints so that processors could 
easily implement attribute defaulting without having to step up to full 
schema awareness, but it appears that this idea got lost in schema land 
(not surprisingly). Hmmm.

In any case, it poses a practical problem, hopefully addressed by the 
code mentioned in Eric's post on this same topic.


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


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