Re: [dita-help] Context-Sensitivity

[Stan Doherty <Stanley.Doherty@Sun.COM>]

Good stuff ... here's some friendly additions/qualifications:

. context hooks stored in the [individual] topic [prolog?]
. context hooks stored in the [individual] map [prolog?]
. context hooks stored in an [unstructured] 
  intermediate (external) file
. context hooks stored in a specialized 
  DITA topic or specialized domain element
 

Rationale ... we should explicitly add the option of a DITA-parseable 
topic or element that contains CS hooks that could be reused, filtered, 
or transformed across multiple projects. At Sun we do a lot of weird, 
one-off help development, so the ability to process callbacks without 
leaving the DITA parsing environment would be cool ... parsing callbacks 
using the same logic that we use to process regular DITA elements via 
.ditaval settings would be a plus.

Stan

P.S. I have a 1:30PM/EST meeting offsite and will make every effort to 
make it back to my office or to home by 4:30PM/EST for our concall.

Tony Self wrote:
> Dear All
>  
> Would it be right to summarise the CS requirement by saying that we need to provide for three options?
>
> . context hooks stored in the topic
> . context hooks stored in the map
> . context hooks stored in an intermediate (external) file
>
> During processing, the necessary map/alias/header/cshelp files would be produced from whatever resource was available.
>
> There would need to be some rules to cope with hooks found in more than one location. For example, if there was a hook in the map's topicref and the topic, which hook would be used. I would suggest that both would be valid. But is that logical? Maybe we need a "cascade":
>
> . Context Hook in intermediate (external) file overrides...
> . any context hook specified in the map, which overrides...
> . any context hook specified in the topic.
>
> Thoughts?
>
> Tony
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>