[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [dita] Machine Industry Task question
Robert, Thanks for your work and I beg your pardon for delaying things. Your impression of our needs is very well described in your mail. Let me just add a few remarks. In a first step our SC revised the very general (section like) content model of prereq and postreq to meet more specific needs for preliminary requirements in a task. We developed a content model that has beed derived and simplified from the S1000D standard. After this first approach we received the response from the TC, that these additional elements must not become part of the generic task type as e.g. the Software industry would not need these elements. So we decided to go for a domain specialization for an optional replacing of the prereq and postreq elements with two new called prelreqs and closereqs elements. (by using the DITA 1.2 constrain mechanism) Based on this second approach we had two response: 1. according to DITA 1.1 we are not allowed to specialize from prereq and postreq. 2. if these two new elements are derived from prereq and postreq, we are going to limit the use of these elements to task and to topics that are specialized from task. To offer more flexibility to specializer who would like to building their own procedual descriptions based on a generic topic, we decided to derive prelreqs and closereqs from section and example. Best regards Chris SeicoDyne GmbH Eichenstrasse 16 CH-6015 Reussbühl Switzerland Tel: +41 41 534 66 97 Mob: +41 78 790 66 97 Skype: seicodyne www.seicodyne.com christian.kravogel@seicodyne.com Member of the DITA Technical Committee Chairman of the DITA Machine Industry Subcommittee -----Ursprüngliche Nachricht----- Von: Robert D Anderson [mailto:robander@us.ibm.com] Gesendet: Mittwoch, 25. Juni 2008 16:44 An: dita@lists.oasis-open.org Betreff: [dita] Machine Industry Task question Hi, I had some questions about the mitask implementation and ran them by Chris Kravogel, who requested that they be discussed at the TC. So, this is a note to get them on the agenda. Background: the machine industry task domain contains the elements prelreqs and closereqs. From what I can tell, these have the same semantic meaning as prereq and postreq, though with much a much more specific content model. The prelreqs element is specialized from section, and the closereqs element is specialized from example. I asked Chris why closereqs comes from example (it is primarily so that closereqs appears at the end of the task). I suggested that the 2 elements actually be specialized from prereq and postreq, which is now legal in DITA 1.2, but the machine industry SC is reluctant because the domain could no longer be used in tasks that are not specialized from task. So, Chris and I would like to discuss these questions: 1. Should our designs anticipate support for specialized tasks that are not specialized from task, or does the TC disapprove of specializing alternate tasks with no relationship to the OASIS task? 2. If so, is the TC also OK with specializing closereqs from example, when it is not an example? Given the close semantic relationship between prelreqs/prereq and closereqs/postreq, are we OK with having no defined relationship? 3. If the domain is designed to be used outside of the OASIS DITA Task module, I have some discomfort with calling it the OASIS "mitask" domain, because it implies a relationship to the OASIS task - do others share this discomfort? Thanks - Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit (507) 253-8787, T/L 553-8787 (Good Monday & Thursday) --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]