RE: [dita-adoption] Thoughts on DITA 1.2 adoption

["Bruce Nevin (bnevin)" <bnevin@cisco.com>]

For some time the problem was that there was no definitive list of
discrete, identified DITA 1.2 features. This may still be the case. When
I was looking for "the list of features" last year I combed through
email threads etc. and sent a draft list to JoAnn.

> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com] 
> Sent: Monday, August 02, 2010 10:55 AM
> To: Joann Hackos; DITA Adoption TC
> Subject: RE: [dita-adoption] Thoughts on DITA 1.2 adoption
> 
> 
> 
> > -----Original Message-----
> > From: Joann Hackos [mailto:joann.hackos@comtech-serv.com]
> > Sent: Monday, 2010 August 02 9:14
> > To: DITA Adoption TC
> > Subject: [dita-adoption] Thoughts on DITA 1.2 adoption
> > 
> > Hi All!
> > At today's meeting could we discuss developing a basic list of DITA
> 1.2
> > features that we would like to see adopted by editing and content 
> > management developers?
> 
> I'm not sure I understand.
> 
> Which features do we NOT want to see adopted by editing and 
> content management developers?
> 
> paul
> 
> > 
> > In asking about DITA 1.2 adoption in writing the status 
> article, I got 
> > such diverse feedback from developers that I would like to have a 
> > standard list.
> > 
> > Specializations
> > Learning and Training
> > Safety Hazard
> > Machine Industry
> > 
> > Keyref
> > Conkeyref
> > Conref Push
> > Delayed conref resolution
> > 
> > Referencing a range of elements
> > 
> > Constraint mechanism
> > Controlled values
> > Taxonomy mechanism
> > Acronym/glossary
> > 
> > New linking capabilities in relationship tables
> > 
> > All the new DTD capabilities such as
> > <sectiondiv>
> > <bodydiv>
> > New map references
> > 
> > I'd like to set something up that is like a checklist that 
> vendors can 
> > go to and tell everyone what they have implemented (or the 
> dates for 
> > implementation).
> > 
> > JoAnn
> 
> ---------------------------------------------------------------------
> 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_workgr
> oups.php 
> 
>