[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Review D: Processing expectations for @keyref in the context of a subject scheme and schemeref
The PDF that went out for review included important comments in the "Extending subject schemes" topic, which we need to address for DITA 2.0:
I think we need to make a normative statement about this [extending a subject scheme] for DITA 2.0. I realize that doing so would require developing detailed content about processing subject scheme maps, since they have different processing expectations than DITA maps in general. Also, see the following draft comment (from the 1.3 time frame), which had been commented out of this topic.
I added this topic to address comments made by Chris Nitchie in the targeted review [of this content for DITA 1.3]. FYI, the paragraph above was in the DITA 1.2 Language Reference topic about the schemeref element.
Re "Example: Extending a subject scheme", Chris stated "That's not how keyref normally works. We definitely need normative language describing the expected processing of keyref in the context of a subject scheme. It's completely different from normal keyref behavior. Normally, a keyref is a reference to the content referenced by the key-defining topicref, not a reference to the topicref itself. And there's no transclusion or extension, as is implied here. So it's completely different processing rules for keys in a subject scheme, and it needs normative description."
Re "Example: Extending a subject scheme upwards", Chris stated " ... the use of keyref in subject schemes to recombine subject definitions is never covered anywhere."
We need additional normative content in this topic ...
I think we MUST cover this information in a sound
architectural topic for DITA 2.0.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]