OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] Scenario for cross-deliverable referencing


On Sep 6, 2011, at 8:11 AM, Michael Priestley wrote:

> Hi Eliot, 
> I believed your scenario was covered in my case of multiple chapters being produced as separate PDFs. 
> In that scenario, the author of Map A does not define a key that references a key defined in map B - they simply include map B's definition of map B's keys, after it has gone through processing to produce a deliverable-specific version of that key definition. 
I'm wading in deep water here:-) and may very well have missed a critical point, but it seems like this is a markup issue that isn't resolve in the general case by simply merging the two (or more) sets of key definitions (which I think is what you're saying above).

If the keys are unique across all of the maps, then yes, you could simply include map B's definitions in map A and use them directly. But, if they are not unique, then don't you still need markup that will allow you to uniquely identify the key you want? In which case, you're back to the problem Eliot stated originally (at least as I understand his original statement). Also, don't you still need a method for identifying the universe of maps that are in play?

Best Regards,
Richard Hamilton
XML Press
XML for Technical Communicators

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]