[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-accessibility] Groups - Graphics Accessibility Proposal06212007 (Graphics_Proposal_06212007.odp) uploaded
Page 1. Slide 1 Proposal: Improvement of Business Graphics Accessibility in ODF 1.2 "Data model attachment to graphics" Chieko Asakawa, Hironobu Takagi and Tatsuya Ishihara IBM Research --------------- Page 2. Slide 2 Proposed items at CSUN F2F meeting (March 2007) - We will focus on the second proposal, today. - P1. Generalization of connectors -- Images, graphic shapes for representing connections of objects --- Necessary for representing diagram structures - P2. Attachment of "original XML data" to formal diagrams -- UML, Mindmap, .... -- Attach metadata representing data models - P3. Preservation of alignment information -- Automatic preservation of alignment history --- Useful for automatic conversion of pictorial Braille --------------- Page 3 with graphics. P2. Attachment of "Original XML Data" to Formal Diagrams - Benefit -- Allow assistive technologies to convert semantic structure of a graphic into accessible format by providing original data model structure. --- Braille translation, screen reading, simplification for magnification/small screen.... - Examples -- Data model of chemical (Chemical Markup Language) -- Data model for UML (XML Metadata Interchange) -- BPEL (Business Process Execution Language) -- Mindmap (FreeMind, etc...) - DocExplorer - ViewPlus Pro Braille Printer http://www.viewplus.com/products/braille-embossers/braille-printers/ - Dot View DV-2 http://www.kgs-jpn.co.jp/b_dv2.html - IVEO http://www.viewplus.com/products/touch-audio-learning/IVEO/ --------------- Page 4 with graphics. Examples of Graphics and Standardize XML Representations CML <cmldoc> <molecule convention="MDLMol" id="diazepam"> <date day="22" month="11" year="1995"> </date> <atomArray> <atom id="a1"> <string builtin="elementType">C</string> <float builtin="x2">1.4278</float> <float builtin="y2">-0.202</float> </atom> <atom id="a2"> <string builtin="elementType">C</string> <float builtin="x2">0.2204</float> <float builtin="y2">0.7483</float> </atom> http://croczilla.com/svg/samples/diazepam/screenshot.png UML (XMI) BPEL Mindmap http://www.ibm.com/developerworks/webservices/library/ws-uml2bpel/index.html http://publib.boulder.ibm.com/infocenter/adiehelp/index.jsptopic=/com.ibm.etools.scenario.emerged.doc/ref/bbldflow.html http://freemind.sourceforge.net/FreeMind-learning-german.png --------------- Page 5. Slide 5 Design Choice for Diagram Data Attachment Table... Blank Use case 1: Attach data model to an "image" Use case 2: Attach data model to a group of "graphic objects" Design 1: Expand use of <draw:frame> for accessibility purpose Not require any change to the ODF spec 1.1. Require ODF spec changes Design 2: Apply new metadata spec proposed by metadata SC Require spec changes (along with metadata SC) Table structure... - Row 1. 3 cells. Blank Use case 1: Attach data model to an "image" Use case 2: Attach data model to a group of "graphic objects" -- Blank -- Use case 1: Attach data model to an "image" -- Use case 2: Attach data model to a group of "graphic objects" - Row 2. 3 cells. Design 1: Expand use of <draw:frame> for accessibility purpose Not require any change to the ODF spec 1.1. Require ODF spec changes -- Design 1: Expand use of <draw:frame> for accessibility purpose -- Not require any change to the ODF spec 1.1. -- Require ODF spec changes --- e.g. support <draw:g> inside <draw:frame> - Row 3. 2 cells. Design 2: Apply new metadata spec proposed by metadata SC Require spec changes (along with metadata SC) -- Design 2: Apply new metadata spec proposed by metadata SC -- Require spec changes (along with metadata SC) --------------- Page 6 with graphics. Slide 6 Design 1. Use <draw:frame> element (Use case 1) - <draw:frame draw:style-name="gr1" draw:layer="layout" svg:width="9.032cm" svg:height="2.258cm" svg:x="9.514cm" svg:y="9.382cm"> - <draw:object xlink:href="./Object 1/classdiagram.dnx" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad"/> - </draw:frame> - <draw:page draw:name="page2" draw:style-name="dp1" draw:master-page-name="Default" presentation:presentation-page-layout-name="AL2T1"> - <draw:image xlink:href="./ObjectReplacements/Object 1" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad"/> - <presentation:notes draw:style-name="dp2"> - <draw:page-thumbnail draw:layer="layout" svg:width="12.7cm" svg:height="9.525cm" svg:x="3.175cm" svg:y="1.905cm" draw:page-number="2"/> - <draw:frame presentation:style-name="pr4" draw:text-style-name="P1" draw:layer="layout" svg:width="15.24cm" svg:height="11.432cm" svg:x="1.905cm" svg:y="12.065cm" presentation:class="notes" presentation:placeholder="true"> - <draw:text-box/> - </draw:frame> - </presentation:notes> - </draw:page> 2 subitems... - Bind UML data and image - Create image from UML File Name : classdiagram.dnx - <children xmi:id="_thHq0NkgEduKaPpMZBg-ow" - targetEdges="_uhC2wNkgEduKaPpMZBg-ow"> - <children xmi:id="_thHq09kgEduKaPpMZBg-ow" - type="ImageCompartment"> - <element xmi:type="uml:Class" href="EE/> - <layoutConstraint xmi:type="notation:Size" - xmi:id="NkgEduKaPpMZBg-ow" - width="1320" height="1320"/> - </children> --------------- Page 7 with graphics and notes. Slide 7 Design 1. Use <draw:frame> element (Use case 2) - <draw:frame draw:style-name="gr1" draw:layer="layout" svg:width="9.032cm" svg:height="2.258cm" svg:x="9.514cm" svg:y="9.382cm"> - </draw:frame> - <draw:page draw:name="page2" draw:style-name="dp1" draw:master-page-name="Default" presentation:presentation-page-layout-name="AL2T1"> - <draw:g> - <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P3" draw:layer="layout" svg:width="6.001cm" svg:height="3.201cm" svg:x="6.099cm" svg:y="4.723cm"> - <text:p text:style-name="P2"> - <text:span text:style-name="T1">Parent</text:span> - </text:p> - <draw:enhanced-geometry svg:viewBox="0 0 21600 21600" draw:type="rectangle" draw:enhanced-path="M 0 0 L 21600 0 21600 21600 0 21600 0 0 Z N"/> - </draw:custom-shape> - <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P3" draw:layer="layout" svg:width="6.001cm" svg:height="3.201cm" svg:x="13.3cm" svg:y="11.924cm"> - <text:p text:style-name="P2"> - <text:span text:style-name="T1">Child</text:span> - </text:p> - <draw:enhanced-geometry svg:viewBox="0 0 21600 21600" draw:type="rectangle" draw:enhanced-path="M 0 0 L 21600 0 21600 21600 0 21600 0 0 Z N"/> - </draw:custom-shape> - <draw:line draw:style-name="gr2" draw:text-style-name="P4" draw:layer="layout" svg:x1="13.498cm" svg:y1="11.527cm" svg:x2="11.298cm" svg:y2="8.123cm"> - <text:p text:style-name="P1"/> - </draw:line> - </draw:g> - <presentation:notes draw:style-name="dp2"> - <draw:page-thumbnail draw:layer="layout" svg:width="12.7cm" svg:height="9.525cm" svg:x="3.175cm" svg:y="1.905cm" draw:page-number="2"/> - <draw:frame presentation:style-name="pr4" draw:text-style-name="P1" draw:layer="layout" svg:width="15.24cm" svg:height="11.432cm" svg:x="1.905cm" svg:y="12.065cm" presentation:class="notes" presentation:placeholder="true"> - <draw:text-box/> - </draw:frame> - </presentation:notes> - </draw:page> - <draw:object xlink:href="./Object 1/classdiagram.dnx" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad"/> Render by SVG Bind data model File Name : classdiagram.dnx --------------- Notes for page 7 This is an example for applying <draw:object> approach to a group of graphic objects. This example is not compatible with current ODF spec (ODF1.1), so we have to propose changes to the ODF spec, if we will take this design approach. --------------- Page 8 with graphics. Slide 8 Current Metadata Proposal for ODF 1.2 6 subitems... - content.xml - <text:meta-field xml:id="citation-1"> - (<text:meta-field xml:id="citation-1-r1"> - Smith, 2000 - </text:meta-field>) - </text:meta-field> rdf:about="urn:uuid:afdc453c-5dc8-4988-8dab-fc378bd9e73d"> - citation.rdf - <cite:Reference - <dcterms:source rdf:resource="urn:isbn:23983487"/> <!-- to specify - the ID/URI for the source --> - <odf:position>1</odf:position> <!-- to track position within the list - of references --> - <cite:pages>23</cite:pages> - </cite:Reference> 2 subitems... - <text:meta-field> is content - created by metadata function 2 subitems... - Specify metadata file - by <odf:MetadataFile> 2 subitems... - Bind content.xml and metadata - By odf:Element 18 subitems... - bibiliography.rdf - <b:Document rdf:about="urn:isbn:23983487"> - <b:referenceType="http://zotero.org/types/book"/> - <dcterms:creator rdf:resource="http://ex.net/people#jane"/> - <dc:title>Some Book Title</dc:title> - <dc:date>2000</dc:date> - <dcterms:publisher rdf:resource="http://ex.net"/> - </b:Document> - <vcard:VCard rdf:about="http://ex.net/people#jane";;> - <!-- note, here, we're using vcard; this could be stored in a - contacts.rdf if one wanted --> - <vcard:sort-string>Smith, Jane</vcard:sort-string> - <!-- obviously could encode much more --> - </vcard:VCard> - <vcard:VCard rdf:about="http://ex.net/people#jane";;> - <vcard:fn>ABC Books</vcard:fn> - <!-- obviously could encode much more --> - </vcard:VCard> 11 subitems... - meta.xml - <odf:Package rdf:about="urn:uuid:224ab023-77b8-4396-a75a-8cecd85b81e3" xmlns:odf="http://docs.oasis-open.org/opendocument/meta/package#";;> - <odf:hasPart> - <odf:MetadataFile odf:path="citation.rdf"> - <odf:Element rdf:about="urn:uuid:afdc453c-5dc8-4988-8dab-fc378bd9e73d" odf:idref="citation-1-r1"/> - </odf:MetadataFile> - </odf:hasPart> - <odf:hasPart> - <odf:MetadataFile odf:path="bibliography.rdf"/> - </odf:hasPart> - </odf:Package> http://lists.oasis-open.org/archives/office-metadata/200706/msg00018.html --------------- Page 9 with graphics and notes. Design 2. Metadata Approach (Use case 1) - <draw:page draw:name="page2" draw:style-name="dp1" draw:master-page-name="Default" presentation:presentation-page-layout-name="AL2T1"> - <draw:frame draw:style-name="gr1" draw:layer="layout" svg:width="9.032cm" svg:height="2.258cm" svg:x="9.514cm" svg:y="9.382cm"> - <draw:image xml:id="id1" xlink:href="./ObjectReplacements/Object 1" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad"/> - </draw:frame> - <presentation:notes draw:style-name="dp2"> - <draw:page-thumbnail draw:layer="layout" svg:width="12.7cm" svg:height="9.525cm" svg:x="3.175cm" svg:y="1.905cm" draw:page-number="2"/> - <draw:frame presentation:style-name="pr4" draw:text-style-name="P1" draw:layer="layout" svg:width="15.24cm" svg:height="11.432cm" svg:x="1.905cm" svg:y="12.065cm" presentation:class="notes" presentation:placeholder="true"> - <draw:text-box/> - </draw:frame> - </presentation:notes> - </draw:page> Create image from UML File Name : classdiagram.dnx - <children xmi:id="_thHq0NkgEduKaPpMZBg-ow" - targetEdges="_uhC2wNkgEduKaPpMZBg-ow"> - <children xmi:id="_thHq09kgEduKaPpMZBg-ow" - type="ImageCompartment"> - <element xmi:type="uml:Class" href="EE/> - <layoutConstraint xmi:type="notation:Size" - xmi:id="NkgEduKaPpMZBg-ow" - width="1320" height="1320"/> - </children> - <office:meta> - <odf:MetadataFile odf:path="classdiagram.dnx"> - <odf:Element rdf:about="urn:uuid:afdc453c-5dc8-4988-8dab-fc378bd9e73d" odf:idref="id1"/> - </odf:MetadataFile> - </office:meta> Set UML data as metadafta file Specify root element of classdiagram.dnx --------------- Notes for page 9 This shows an example tag structure for applying metadata proposal to blind XML structure to an image. If we will take this approach, it is required to discuss with metadata SC. --------------- Page 10 with notes. Slide 10 Design 2. Metadata Approach (Use case 2) - <draw:page draw:name="page2" draw:style-name="dp1" draw:master-page-name="Default" presentation:presentation-page-layout-name="AL2T1"> - <draw:g xml:id="id1"> - <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P3" draw:layer="layout" svg:width="6.001cm" svg:height="3.201cm" svg:x="6.099cm" svg:y="4.723cm"> - <text:p text:style-name="P2"> - <text:span text:style-name="T1">Parent</text:span> - </text:p> - <draw:enhanced-geometry svg:viewBox="0 0 21600 21600" draw:type="rectangle" draw:enhanced-path="M 0 0 L 21600 0 21600 21600 0 21600 0 0 Z N"/> - </draw:custom-shape> - <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P3" draw:layer="layout" svg:width="6.001cm" svg:height="3.201cm" svg:x="13.3cm" svg:y="11.924cm"> - <text:p text:style-name="P2"> - <text:span text:style-name="T1">Child</text:span> - </text:p> - <draw:enhanced-geometry svg:viewBox="0 0 21600 21600" draw:type="rectangle" draw:enhanced-path="M 0 0 L 21600 0 21600 21600 0 21600 0 0 Z N"/> - </draw:custom-shape> - <draw:line draw:style-name="gr2" draw:text-style-name="P4" draw:layer="layout" svg:x1="13.498cm" svg:y1="11.527cm" svg:x2="11.298cm" svg:y2="8.123cm"> - <text:p text:style-name="P1"/> - </draw:line> - </draw:g> - <presentation:notes draw:style-name="dp2"> - <draw:page-thumbnail draw:layer="layout" svg:width="12.7cm" svg:height="9.525cm" svg:x="3.175cm" svg:y="1.905cm" draw:page-number="2"/> - <draw:frame presentation:style-name="pr4" draw:text-style-name="P1" draw:layer="layout" svg:width="15.24cm" svg:height="11.432cm" svg:x="1.905cm" svg:y="12.065cm" presentation:class="notes" presentation:placeholder="true"> - <draw:text-box/> - </draw:frame> - </presentation:notes> - </draw:page> - <office:meta> - <odf:MetadataFile odf:path="classdiagram.dnx"> - <odf:Element rdf:about="urn:uuid:afdc453c-5dc8-4988-8dab-fc378bd9e73d" odf:idref="id1"/> - </odf:MetadataFile> - </office:meta> File Name : classdiagram.dnx Set UML data as metadafta file Specify root element of classdiagram.dnx --------------- Page 11. Slide 11 Back up --------------- Page 12. ODF 1.1 Spec 9.3 Frames - A frame is a rectangular container where that contains enhanced content like text boxes, images or objects. Frames are very similar to regular drawing shapes, but support some features that are not available for regular drawing shapes, like contours, image maps and hyperlinks. In particular, a frame allows to have multiple renditions of an object. That is, a frame may for instance contain an object as well as an image. In this case, the application may choose the content that it supports best. If the application supports the object type contained in the frame, it probably will render the object. If it does not support the object, it will render the image. - In general, an application must not render more than one of the content elements contained in a frame. The order of content elements dictates the document author's preference for rendering, with the first child being the most preferred. This means that applications should render the first child element that it supports. A frame must contain at least one content element. The inclusion of multiple content elements is optional. Application may preserve the content elements they don't render, but don't have to.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]