[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Release Management Domain: Must apply to maps as well as topics
I for one would not object to the TC's finding this to be a logical
and straightforward bug fix. -- Don On 3/8/2014 11:45 AM, Eliot Kimber
wrote:
Proposal 13102 as written says: "enables content workers to log comments and metadata at the topic level when changes are made." The implicit restriction to topics is not necessary: there's no reason not to allow revision history within maps and no technical reason to not use it within maps (that is, <metadata>, the specialization base of <change-historylist>, is allowed within <topicmeta>, so the domain is inherently allowable within maps). I take this to be a simple oversight on the part of the original proposers who were focused on topic-specific use cases. I can't see any reason not to allow the domain within maps and can think of times when I would want to use it in maps. Does the TC object to adjusting the spec language to explicitly allow use of the domain within maps (which also implies integrating the domain in all non-base map types in addition to the non-base topic types already indicated in the proposal). Cheers, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com --------------------------------------------------------------------- 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 --
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]