[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Question on Public IDs
Hi Jang, I'm glad you're looking at this sort of issue in FrameMaker ... I've long been frustrated with FrameMaker's XSLT support for other reasons, which we can go into if you're looking to improve FrameMaker's XSLT support in the general case. I think even attempting this sort of processing (passing arbitrary public IDs to a result document) is problematic, particularly with XSLT. When I first attempted this in XSLT 1.0 (when it was not possible to do so), I learned from the XSLT cognoscenti that XSLT was not meant to be a general-purpose XML to XML transformation language. More recently, XSLT supports <xsl:output>, which allows one to set a public ID, but because <xsl:output> is a top-level stylesheet element, you cannot parameterize the public ID value in the result document. IMO, "adding the public ID as an attribute value" is a losing proposition, at least with XSLT, because it's not possible to parameterize the XML declaration of the result document. Furthermore, using this value in the general case to adjust the transformation (via template parameterization or via other processing methods) strikes me as a scary proposition. If I were a FrameMaker product developer, I might focus instead
on implementing true (@class-aware) specialization support. :-)
I acknowledge that this may be where you are trying to go. -Alan On 2/2/18 4:23 AM, Jang wrote:
-- Alan Houser Group Wellesley, Inc. Consultant and Trainer, Technical Publishing arh on Twitter 412-450-0532 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]