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] Groups - 1.1 Issue 37: Reconciling link and topicref (Issue37.html) uploaded


Hi, Yas:

Through the combination of linklist, linkpool, and link, DITA already supports the complex case for expressing topic relationships within topic. To be able to have a single element for topic relationships in both map and topic, we need the ability to express the same complexity.

One typical scenario for the complex case might be as part of a processing pipeline. The context in which a topic appears could be instilled into the topic so we can generate output with links to the contexts in which it appears.

Another scenario might be where each topic identifies its children (separately from its associative relationships), and the processing assembles the hierarchy from the topics. If, within the problem domain, the children for a topic never change, that approach would be highly maintainable.

I agree that the most typical case would be to maintain the hierarchical relationships in the map and only the associative relationships in the topic. So, the goal would be for the standard case to be simple to express and for more unusual cases to be possible to express.


Thanks,


Erik Hennum
ehennum@us.ibm.com


"Yas Etessam" <yas.etessam@blastradius.com> wrote on 08/16/2005 07:20:28 AM:

> Hi Erik,
>  
> Issue #37 proposes a sensible solution for the simple case (copy
> paste links/topicrefs).  However, I'm questioning the need to
> support the complex case (adding relcontext and thisTopic elements).
>
> Is this necessary or a "nice to have" feature.  DITA already
> contains fairly sophisticated linking mechanisms.  I'd like to see
> the simple case implemented but don't yet understand the immediate
> need for supporting the complex case.
>
> Could you shed some light on this?
>
> Thanks,
>
>
> Yas Etessam
>
>  
>
>
> -----Original Message-----
> From: ehennum@us.ibm.com [mailto:ehennum@us.ibm.com]
> Sent: Monday, August 15, 2005 8:22 PM
> To: dita@lists.oasis-open.org
> Subject: [dita] Groups - 1.1 Issue 37: Reconciling link and topicref
> (Issue37.html) uploaded
>
> Please see the description for DITA 1.1 issue 37:  reconciling link
> and topicref
>
>  -- Erik Hennum
>
> The document named 1.1 Issue 37: Reconciling link and topicref
> (Issue37.html) has been submitted by Erik Hennum to the OASIS Darwin
> Information Typing Architecture (DITA) TC document repository.
>
> Document Description:
> DITA 1.0 expresses a relationship between two topics in two different
> ways:
>
> *  Within a topic, using the link element
>
> *  Within a map, using the topicref element
>
> Representing topic relationships with a single element would
> simplify the story.
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/dita/document.php?
> document_id=14060
>
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/dita/download.
> php/14060/Issue37.html
>
>
> PLEASE NOTE:  If the above links do not work for you, your email
> application may be breaking the link into two pieces.  You may be
> able to copy and paste the entire link address into the address
> field of your web browser.
>
> -OASIS Open Administration



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