[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [dita-machine-industry] Groups - Example of hazard statement styling (Hazard-styling-Jang.pdf) uploaded
Hi Jonathan Just a short question. Don't you plan any telephone mettings or did I miss something? Thank you for a short reply. Kind regards Sissi Prof. Sissi Closs Informations- und Medientechnik Hochschule Karlsruhe - Technik und Wirtschaft Büro: F 312 Geschäftsleitung Comet Computer GmbH Comet Communication GmbH Rückertstr. 5 80336 München Firma Tel: 089 / 46224611 Firma Fax: 089 / 46224612 Email: closs@comet.de VAT: DE128219532 HRB: 81386 München Geschäftsführung: Prof. Sissi Closs ---------------------------------------------------- ---------------------------------------------------- Trends, Impulse und Visionen Ihr Termin im neuen Jahr: 11. Single-Source-Forum von Comet am 23. Mai 2011 in München Weitere Infos und Online-Anmeldung unter: www.single-source-forum.de ---------------------------------------------------- -----Ursprüngliche Nachricht----- Von: Jonatan Lundin [mailto:Jonatan.Lundin@citec.com] Gesendet: Freitag, 11. Februar 2011 11:09 An: Keld Jellesen; jang@jang.nl; dita-machine-industry@lists.oasis-open.org Cc: birgit@xstructuring.eu Betreff: RE: [dita-machine-industry] Groups - Example of hazard statement styling (Hazard-styling-Jang.pdf) uploaded Hi, I agree totally! What I mean is that the spec and OT should include an example, just to give the user an idea of what a hazard statement can look like (one typical example out of many). The spec shall of course not state that a hazard statement MUST be implemented as the example. Then the spec should be extended to say something like "this is an example and the rendering principle must be implemented according to organization/authority policy". So what we must do is to pick examples from ANSI and ISO standards we believe is good examples. Br, Jonatan ________________________________________ From: Keld Jellesen [keld.jellesen@advice2u.dk] Sent: Friday, February 11, 2011 9:53 AM To: Jonatan Lundin; jang@jang.nl; dita-machine-industry@lists.oasis-open.org Cc: birgit@xstructuring.eu Subject: RE: [dita-machine-industry] Groups - Example of hazard statement styling (Hazard-styling-Jang.pdf) uploaded Here my opinion on this matter. I don't think this is a matter DITA should interfere in, because normally are hazards statements and the way they are represented and used regulated by other authorize which can be local or world wide. What is important is that the structure allows for placing the statements where the authorities want them to be. Also notice that sometimes we have seen accidents to change the way authorizes want hazards statements to show/render, and those changes normally get introduced quite quickly. I think it is fine that OT provide some kind of reasonable default rendition, but start to introduce this to become a part of the DITA Specification is completely off and waist of our time :-(. Rendition of hazard statements are quite hairy I can tell. Why do I know because I'm just in the middle of implementing one. Sorry to be so direct Keld Jellesen Skype: keld.jellesen Mobile: +45 30-277-965 (30-css-xml) -----Original Message----- From: Jonatan Lundin [mailto:Jonatan.Lundin@citec.com] Sent: 11. februar 2011 09:10 To: jang@jang.nl; dita-machine-industry@lists.oasis-open.org Cc: birgit@xstructuring.eu Subject: RE: [dita-machine-industry] Groups - Example of hazard statement styling (Hazard-styling-Jang.pdf) uploaded Hi all, About the rendering of hazard statements in DITA OT and in DITA 1.2 spec. The group discussed and decided upon hazard statement rendering examples that we suggested should be used in the 1.2 spec. See mail from Chris 15 of sep 2009 (subject "Hazard Statement Examples"). But I see that the examples was never included in the spec (I dont know why). Of course our group must argue to use the same examples in the spec as in DITA OT. I see that there are differences, from a rendering point of view, in the doc Jang submitted in dec last year compared to the examples from 2009; for example in Jangs example the hazard icon is within the frame, but in the example from 2009 the hazard symbol is outside to the left of the frame. There are also some other differences. This we must discuss on next meeting. Br, Jonatan ________________________________________ From: jang@jang.nl [jang@jang.nl] Sent: Tuesday, December 14, 2010 4:01 PM To: dita-machine-industry@lists.oasis-open.org Cc: birgit@xstructuring.eu Subject: [dita-machine-industry] Groups - Example of hazard statement styling (Hazard-styling-Jang.pdf) uploaded The document named Example of hazard statement styling (Hazard-styling-Jang.pdf) has been submitted by Jang Graat to the DITA Machine Industry SC document repository. Document Description: The hazard statement in DITA 1.2 was defined to follow the ANSI Z535.4 standard. I have created matching hazard statements and styling in FrameMaker for a client. I am offering this document for discussion in the Machine Industry SC. The goal is to reach a styling example that will be used in future DITA-OT releases. View Document Details: http://www.oasis-open.org/committees/document.php?document_id=40577 Download Document: http://www.oasis-open.org/committees/download.php/40577/Hazard-styling-Jang. pdf PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser. -OASIS Open Administration --------------------------------------------------------------------- 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_workgroups.php --------------------------------------------------------------------- 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_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]