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: Stage 2 proposal: make @audience, @platform, @product, and @otherprops into specializations


DITA 2.0 proposed feature #18: Make audience, platform, product, otherprops into specializations

DITA 2.0 should refactor the existing profiling attributes – @audience, @platform, @product, and @othermeta – so that they’re defined in domains and specialized from @props, as we did for @deliveryTarget in 1.3.

Date and version information
Date that this feature proposal was completed

Champion of the proposal Links to any previous versions of the proposal Links to minutes where this proposal was discussed at stage 1 and moved to stage 2 Links to e-mail discussion that resulted in new versions of the proposal Link to the GitHub issue Original requirement or use case

As discussed at the TC May 2, 2017, the goal is to clean up our architecture by making the original four filter attributes into specializations of @props. They already function exactly the same way as @props (including the fact that they allow the grouping syntax that is exactly equivalent to the generalized attribute syntax). However, they were defined as part of the core before we had specialized attributes, so for backwards compatibility they have remained in the core even though logically they must be treated exactly the same as any specialization of @props.

Use cases


New terminology

N/A; any terminology needed for these already exists for specialized attributes.

Proposed solution

Benefits
Who will benefit from this feature? How many people probably will make use of this feature? How much of a positive impact is expected for the users who will make use of the feature? Technical requirements
Adding new elements or attributes Removing elements or attributes Processing impact Overall usability Backwards compatibility
Was this change previously announced in an earlier version of DITA? Removing or renaming an attribute that was shipped in DITA 1.3? Are element or attribute groups being renamed or shuffled? Migration planCosts
Outline the impact (time and effort) of the feature on the following groups: Examples

N/A; content is exactly the same.


Regards,

Robert D. Anderson
DITA-OT lead and Co-editor DITA 1.3 specification,
Digital Services Group


E-mail: robander@us.ibm.com
Digital Services Group
11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA




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