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] RE: Bookmap implementation

Hi, France, Yas, and Eliot:

I have a bit of concern about pushing the role semantic up to the container. By rights, shouldn't the role semantic be associated directly with the <topicref> element via specialization? Putting the role semantic on the container does work in this case because book roles are fundamentally top-down, but applied generally, that approach would result in deeper structures with a much higher markup to content ratio.

A more general solution might be to enhance specialization so a specialized element could acquire or shed contextual roles without limiting reuse.

The other point is that, if people conref from a bookmap into an ordinary map, generalization should enable that reuse because chapterref can revert to topicref.

Would it be better to build in the container legacy for this special case? Or to work on the long-term solution and, in the mean time, reuse from a bookmap into an ordinary map?

Hoping that's useful,

Erik Hennum

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