OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

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

Subject: Re: [dita-comment] <supplies> element

Hi Julio,

Thanks for the comments.

For this one and for the comment about <supequip> - these elements are part of a domain created by the machinery subcommittee. The domain was created in DITA 1.2, so we are not able to remove elements at this time - doing so would break backwards compatibility for any DITA 1.2 user of the machinery task topics. We will have an opportunity to redesign or simplify this model in DITA 2.0.

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

Inactive hide details for "Julio Vazquez" ---08/05/2015 07:21:43---http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part3-all-"Julio Vazquez" ---08/05/2015 07:21:43---http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part3-all-inclusive/langRe f/technicalContent/supp

From: "Julio Vazquez" <jvazquez@vasont.com>
To: <dita-comment@lists.oasis-open.org>
Date: 08/05/2015 07:21
Subject: [dita-comment] <supplies> element


I have the same problem with this element as I do with <supequip>. This adds unnecessary bloat to the content model. Either you have a list of supplies or there are no supplies. I’m sure the content model could be written such that either the list or the element that indicates there is no requirement is specified. I won’t comment on other areas of this task structure that should be removed but I think that containers just for the fact of a container makes little sense. Processors could supply titles for these sorts of items, if needed without a container to trigger them.

Julio J. Vazquez
Senior Content Analyst
Vasont Systems
A TransPerfect Company
Skype: tpt_jvazquez

+1 717-793-3895
The information in this email is confidential and intended for those to whom it is addressed.

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