[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] New topic about "Map-to-map cascading"
> -----Original Message----- > From: Kristen James Eberlein [mailto:kris@eberleinconsulting.com] > Sent: Sunday, 2010 February 28 19:52 > To: DITA TC > Subject: [dita] New topic about "Map-to-map cascading" > > I've authored a new topic about "Map-to-map cascading," based on review > comments from Jeff Ogden, Dave Helfinstine, Paul Grosso, and Robert > Anderson. I'll copy and paste an HTML version below; you also can grab > the file (map-to-map-cascading-of-metadata.dita) from the archSpec > subdirectory in SVN. Comments (mostly from Dave Helfinstine, though I take the blame for any mistakes or confusion): There is a basic problem with this discussion of map to map cascading behavior document and the examples. The cascading of attributes from map to map ONLY overrides or supplements the map element of the embedded map. Those attributes from the map cascade into the map. For example, if toc="no" is specified on a map, but the embedded map has <map toc="yes"> . . . <topicref href="a.dita" toc="yes" /> </map> The effective map would have <map toc="no"> . . . <topicref href="a.dita" toc="yes" /> </map> Note that the toc attribute would still be toc="yes" on that topic as cascading attributes do not override other explicit attributes. The same is true for the others, except audience works a bit differently. The embedded map again might have audience="publishers" set. Then the effective value for the map element would be audience="publishers developers". If there is no audience attribute on the map, the map element would have the audience="developers" and that would cascade normally through the map.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]