dita-machine-industry message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: DITA Machine Industry SC: Meeting Minutes 2006/12/12
- From: Klaus.Fenchel@ovidius.com
- To: dita-machine-industry@lists.oasis-open.org
- Date: Fri, 22 Dec 2006 14:46:34 +0100
1) Roll call
We have quorum.
2) We need a Secretary
Issue postponed. The secretary role
rotates.
Minutes taken by Klaus Fenchel
3) Approve minutes from previous business
meeting:
* http://www.oasis-open.org/apps/org/workgroup/dita-machine-industry/email/archives/200612/msg00000.html
Minutes accepted by: Chris Kravogel
Seconded by: Klaus Fenchel
4) Business:
4.1) Motion to accept the type attributes
notice and caution to note element
Motion: Chris Kravogel
Second: Sissy Closs
4.2) Summary changes to DTD as discussed
during meeting of November, 28th
* The required attribute "type"
of the element "hazardstatement" was renamed to "level"
because it indicates the degree of the hazardstatement.
* An optional attribute "type"
was added to the element hazardstatement to indicate the type of hazard.
Examples for type: "Hazardous Electrical Voltage", "Laser
Light", ... The attribute is of type CDATA and optional (#IMPLIED).
4.3) Correction of error in DTD:
DTD and LangRef Proposal Issue5-v2-2.pdf
has + sign after content model of hazard statement
change
((%messagepanel;), (%symbol;)*)+ (Issue5-v2-2.pdf)
to
((%messagepanel;)+, (%symbol;)*) (Issue5-v2-3.pdf)
4.4) Summary changes to DTD as discussed
during meeting of November, 28th (cont.)
* An optional attribute "type"
was added to the element hazardstatement
to inicate the type of hazard.
Examples for type: "Hazardous Electrical
Voltage", "Laser Light",
...
* The DTD allows to specialize the element
"hazardstatement" to leave
out the element "symbol"
for applications where the user should only be
allowed to pick from a predefined
number of symbols (= types).
* The DTD allows to specialize the element
"messagepanel" to a
stricter content model where
"typeofhazard" is mandatory and at least
one element "howtoavoid"
must appear:
* The DTD allows to specialize the element
"hazardstatement" to a
stricter content model where
"messagepanel" is mandatory (and the
symbol is controled via the type
attribute)
4.5) Discussion of Content Model of
typeofhazard
Proposal: Change content model of typeofhazard
from (#PCDATA|%basic.ph;)
to (#PCDATA|%ph;)
4.6) Discussion of Content Model of
consequence
Proposal: Change content model of consequence
from (#PCDATA|%basic.ph;)
to (#PCDATA|%ph;)
4.7 Discussion of howtoavoid:
Proposal: add simpletable, remove p
from %hazard.cnt;
4.8 Presentation Patrick Willekens:
Maintenance Task
Patrick presents his proposal.
Klaus Fenchel
Geschäftsführer
--
Ovidius GmbH
Alte Jakobstr. 77
D-10179 Berlin
T: +49 30 283089-0
F: +49 30 283089-29
klaus.fenchel@ovidius.com
http://www.ovidius.com
--------------------------------------------
Komplexe DTDs - einfach visualisiert!
TreeVision im Einsatz bei Eurocopter Deutschland.
Erfahren Sie mehr auf unserer Webseite:
http://www.treevision.de
--------------------------------------------
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]