Request for TC feedback about @subjectrefs proposal

[kris eberleinconsulting.com <kris@eberleinconsulting.com>]

I was expecting to send the stage three proposal to reviewers (Robert, Gershon, Carsten) last Friday, but ran into some glitches when considering how to update the example topics in the “Cascading metadata” section of the spec.

 

The technical requirements outlined in the stage two proposal called for adding @subjectrefs to <topicref> and specializations of <topicref>. Now I’m wondering if @subjectrefs should also be available on <map>.

 

I don’t think setting @subjectrefs on <map> will be something that folks often do, but it would make it easier to explain how @subjectrefs cascades from a <mapref> element to the topics referenced in the submap.

 

I was hoping to simply edit the following topic: “Example: How attributes cascade from one map to another” …

 

Draft stage three proposal attached, as well as a PDF of the extant example topic.

 

Kris

 

Attachment: stage-3-647-replace-classification-domain-with-new-attribute.pdf
Description: stage-3-647-replace-classification-domain-with-new-attribute.pdf

Attachment: Pages from dita-2.0-specification.pdf
Description: Pages from dita-2.0-specification.pdf