One approach to this is to simply say that the context (“chapterness”,
“partness”, or …) does not cascade when a generic topic
reference is used. Where a generic topic reference is a reference from a
topicref or any topicref specialization defined in mapgropup-d (mostly
this just picks up mapref).
The idea is that we don't want to lose the more detailed
context that is available from a topicref specialization when maps or branches
of maps are referenced using generic topicrefs that contain less information.
This might or might not also be combined with a note that
says that such references are discouraged and that implementations MAY, but are
NOT REQUIRED to, issue warning messages in such cases.
So,
Topicref to bookmap:
Chapters in the bookmap
maintain their “chapterness”
Parts in the bookmap maintain
their “partness”
Chapter to map:
Top level topicrefs in the
map receive “chapterness”
Part to map
Top level topicrefs in the
map receive “partness”
-Jeff
> -----Original Message-----
> From: Grosso, Paul [mailto:]
> Sent: Friday, June 05, 2009 12:52 PM
> To: dita
> Subject: RE: [dita] referencing a bookmap from a map
>
> Don,
>
> I've not seen any responses to this. Can you put it on
> the agenda for our next meeting?
>
> thanks,
>
> paul
>
> > -----Original Message-----
> > From: Grosso, Paul [mailto:]
> > Sent: Thursday, 2009 May 28 10:44
> > To: dita
> > Subject: [dita] referencing a bookmap from a map
> >
> >
> > Proposal 12055 is clear about what we do in the specialized
map to
> > generic map case and also about the specialized map to
specialized
> > map case, but we're not sure what should happen when a
generic map
> > references a specialized map.
> >
> > For example, what should happen in the following case:
> >
> > map1
> > ----
> > topicref to bookmap2
> >
> > bookmap2
> > --------
> > frontmatter
> > booklists
> > Toc
> > part referencing a concept
> > chapter
referencing a task
> >
> > What are the contexts or roles for the elements in bookmap2?
> > Unchanged?
> > Or does the generic topic reference from map1 override the
top level
> > topicrefs in bookmap2 so you end up with something
> > effectively like the
> > following for bookmap2:
> >
> > bookmap2
> > --------
> > topicref for frontmatter
> > booklists
> > Toc
> > topicref for part referencing a concept
> > chapter
referencing a task
> >
> >
> > Keeping things unchanged preserves the specialized
information from a
> > bookmap,
> > but it also allows you to create situations using map
references that
> > you
> > could not create within a single bookmap (e.g., a chapter
within a
> > chapter or
> > a part within a topic).
> >
> > On the other hand, if the generic topic reference from map1
overrides
> > the
> > top level topicrefs in bookmap2, you couldn't create
unexpected
> > situations, but
> > you lose all of the specialized information from a bookmap
because you
> > more or
> > less fallback to the lower common denominator of a generic
map.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS
TC that
> > generates this mail. Follow this link to all your TCs
in OASIS at:
> >
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC
that
> generates this mail. Follow this link to all your TCs in
OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
