[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] DITA and Namespaces? A Potential Compromise Solution for DITA 1.3?
For XSLT 1 you'd simply have to do the look directly in your match expression--you wouldn't be able to hide it behind a function. So it could be done in XSLT 1, but it wouldn't be pretty. In any case, it's a moot point for DITA 1.3 since we decided we're not going to pursue this at this time. Cheers, E. On 5/22/12 3:26 PM, "Jirka Kosek" <jirka@kosek.cz> wrote: > On 22.5.2012 21:56, Eliot Kimber wrote: > >> I guess I'd rather have a more compact syntax at the cost of a little >> processing. Moore's law continues to hold but verbose syntax is always >> verbose. > > Maybe I missed something, but this "little processing" would mean that > for each @class attribute you would need to: > > 1. Find all "DITA namespace declarations" (dita_ns:* attributes) which > are in scope > > 2. Based on this replace prefixes in @class attribute by corresponding > namespace URI > > 3. Do a match on replaced @class with namespace URI + original element > name after : > > This is actually quite complex thing to do. In XSLT 2.0 you can create > user defined function to do this and use it for template matching. But I > can't imagine how to do this in XSLT 1.0. > > Jirka -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]