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


Help: OASIS Mailing Lists Help | MarkMail Help

dita-help message

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

Subject: FW: [dita-help] Values for yield-to-topic

Greetings all


Ian has mailed the below response, and I think his suggestions are better than mine! The only further change I would suggest is to use “priority” (or “source-priority” or “processing-priority” as the attribute name, because “source-id” seems to suggest that the value should be an identification number.


What does everyone else think?



Tony Self


From: ian balanza-davis [mailto:ibalanza_davis@yahoo.co.uk]
Sent: Saturday, 24 August 2013 4:25 AM
To: tself@hyperwrite.com
Subject: Re: [dita-help] Values for yield-to-topic


Hi Tony

Nice to know I think along the same lines as Robert... :-)

I am not sure yield is descriptive enough, how about something like "source-id"
and values of (=> means change to):
use-both                        =>        topic-and-map
ignore-map                    =>        topic-only
ignore-topic                    =>       map-only
for-conflict-ignore-map   =>       map-takes-priority
for-conflict-ignore-topic  =>        topic-takes-priority

or something along those lines



From: Tony Self <tself@hyperwrite.com>
To: dita-help@lists.oasis-open.org
Sent: Friday, 23 August 2013, 0:55
Subject: [dita-help] Values for yield-to-topic

Greetings, colleagues

Robert Anderson has come up with some suggestions about the CSH proposal in
its revised form (actually, his comments would also have applied if we had a
separate ua-context element).

Anyway, Robert has pointed out that a boolean yes/no value in yield-to-topic
may not be detailed enough to cater for a scenario where you wanted to use
the topic context hooks unless there was a conflict, in which case you
wanted to use those in the map. Or if there was a conflict (same
context-id), you may want to include both the context from the map AND the

Robert saw the potential values as 1. Use values from both 2. Ignore all
resourceid's in the map and use those in the topic
2.5 Opposite - ignore all those in the topic and let the map override 3.
Ignore those in the map that conflict (same appname), but use the rest
3.5 Opposite of 3, ignore those in the topic that conflict.

I think we should change the attribute name to just "yield", and suggest
valid values of use-both, ignore-map, ignore-topic, for-conflict-ignore-map,
and for-topic-ignore-topic.

Could you have a think about this before next Monday's meeting, and either
share your supports through the mailing list, or bring them along to the

Best regards

Tony Self

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:

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