[OASIS Issue Tracker] (DITAADOPT-15) As a DITA information architect, I want to learn about best practices for implementing conditional attribute values so they are maintainable across multiple releases.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/DITAADOPT-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Schengili-Roberts updated DITAADOPT-15:
---------------------------------------------

    Priority: Minor  (was: Major)

> As a DITA information architect, I want to learn about best practices for implementing conditional attribute values so they are maintainable across multiple releases.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DITAADOPT-15
>                 URL: https://issues.oasis-open.org/browse/DITAADOPT-15
>             Project: OASIS DITA Adoption TC
>          Issue Type: Task
>          Components: Whitepapers
>            Reporter: Stanley Doherty
>            Assignee: Keith Schengili-Roberts
>            Priority: Minor
>
> * For DITA architects/users to understand some of the best practices for managing condition (and related DITAVALs), we may need to frame for them the benefits of some of the DITA 1.2 and 1.3 features designed to help (e.g. subjectScheme maps notably).
> * Similarly, soliciting feedback and input from companies who have been managing conditions for a long time would offer reads some insight into the lifecycle of this information (creation, maintenance, retirement).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)