I don’t have a problem including it, as these elements are not mandatory, but can be used if needed.
Thanks and best regards,
--Scott Scott Hudson | PELCO by Schneider Electric | United States | Standards & Information Architect Phone: +1 970 282 1952 | Mobile: +1 720 369 2433 | Email: scott.hudson@schneider-electric.com Dear L&T Sub-committee members and
list -
DITA 1.3 will include a new "Release
management domain," which is described in this Stage 3 proposal -
https://www.oasis-open.org/committees/download.php/50971/13102_Stage3Proposal.pdf.
Essentially, this domain is included
with the Technical-content domain elements and provides additional metadata
elements (11 by my count) for tracking content changes, including the person,
organization, summary of the change, and key dates.
Kris has asked if we want it included
or not with the default content models for the L&T topics.
My personal take is that since the default
L&T content models do not include the other Tech-content domains, such
as programming or software elements, or the new equation, mathml, and svg
domains, that we keep the Release mgt domain optional as well. This leaves
it to the implementers to decide, based on the content types and mgt systems
they use.
What do others think? Please get
back to me with your input by the end of the day this Friday if possible,
so we can get back to the Kris and the TC with a recommendation.
Thanks much in advance!
John
___________________________________
John Hunt
Chair, OASIS DITA Learning and Training
Content Sub-Committee
Senior Technical Content Architect
IBM Collaboration Solutions | User Experience: Design and Information Excellence
4205 S. Miami Blvd, Durham, NC 27703
john_hunt@us.ibm.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
|