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: Re: [dita] Release management stage proposal: conent of change-person and change-organization


Hi Tom - that is in line with what I understood on the call - that is, I
don't think it's a change in what we discussed, it's more a clarification
of the specialization ancestry. As I understood the discussion, the
elements should each be specialized from <data>, with content models that
allow either plain text or the "text" element.

In DTD terms, that would mean that each of these elements allows:
(#PCDATA | text)

Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/)



From:	JoAnn Hackos <joann.hackos@comtech-serv.com>
To:	Cihak Thomas-R65612 <R65612@freescale.com>,
Cc:	"dita@lists.oasis-open.org" <dita@lists.oasis-open.org>
Date:	09/03/2013 20:17
Subject:	Re: [dita] Release management stage proposal: conent of
            change-person and change-organization
Sent by:	<dita@lists.oasis-open.org>



You have my firm support.
JoAnn

Sent from my iPad
JoAnn Hackos
Comtech Services Inc
710 Kipling Street Suite 400
Lakewood CO 80215

On Sep 3, 2013, at 4:34 PM, "Cihak Thomas-R65612" <R65612@freescale.com>
wrote:

      Hello,

      I am sending this email to let you know that I want to deviate
      slightly from what we agreed on this morning. However, I believe the
      deviation makes good sense.

      We agreed this morning that these two elements, which are being
      reverted to what they were before the xnal domain was involved, would
      have text content. When I send out the revised proposal tomorrow,
      however, I would like to base them on <data>, for these reasons:
               ·         The elements in bookchangehistory that they are
               based on, organization and person, are specialized on
               <data>.
               ·         All the other child elements of
               <change-historylist> are specialized on <data>; there is no
               reason for these two to be different.
               ·         These elements would have been specialized from
               <data> if xnal had not entered the picture.

      I hope this change will be acceptable to everyone, since it makes for
      a completely uniform structure that more closely resembles the domain
      it’s based on.

      Thank you.


      with best regards

      Tom Cihak
      Freescale
      512.996.5072


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