Investigation Use of XML and HTML in publication of ISO Standards

1
Investigation -- Use of XML and HTML in
publication of ISO Standards

• Myrtle Beach, SC
• February, 2002

2
Purpose

• Provide Background and Input to the Discussions
  on Use of XML and HTML in the Publication of ISO
  Standards
• Provide
• Draft Set of Goals/Options
• Feasibility Test of XML Publication in ISO
• XML Schema Using Fowler HTML Input (from SF)
• Lessons Learned
• Issues/Approaches

3
Goals and Options (1)

• Conform to Open Standards
• W3C Recommendations
• XML http//www.w3.org/TR/2000/REC-xml-20001006
  
• XSL 1.0 http//www.w3.org/TR/xsl/
• HTML 4.01 http//www.w3.org/TR/html401/
• XHTML 1.0 http//www.w3.org/TR/xhtml1/
• Three Flavors Strict,Transitional, and
  Frameset
• XHTML 1.1 Modules-based XHTML http//www.w3.org/T
  R/xhtml11/
• XPath 1.0 http//www.w3.org/TR/xpath
• XPointer 1.0 http//www.w3.org/TR/xptr/
• W3C Drafts
• XML Accessibility Guidelines http//www.w3.org/T
  R/xmlgl
• 14 Guidelines, Three Levels of Conformance

4
Goals and Options (2)

• Conform to Open Standards
• Document Standards
• ISO Standards Specification (To Be Published)
• DocBook
• (SGML) DTD http//www.oasis-open.org/committees/
  docbook/sgml/4.1/ index.shtml
• DocBook 5.0 to be XML DTD with an experimental
  XML Schema to be Developed (not backwards
  compatible) http//www.oasis-open.org/
  committees/docbook/sgml/4.1/50issues.txt
• W3C xmlspec for Recommendations
• XML Schema http//dev.w3.org/cvsweb/spec-prod/sc
  hema/xmlspec.xsd? rev1.2content-typetext/x-cvsw
  eb-markup
• XML DTD http//www.w3.org/XML/1998/06/xmlspec-re
  port-v21.htm
• OpenOffice (StarOffice 6.0)

5
Goals and Options (3)

• Support User Viewing Needs/Preferences
• Browsers
• Microsofts Internet Explorer (versions 6.0,
  5.5, 5.01, 4.0, )
• Netscape Navigator (versions 6.2, 6.1, 6, 5, 3,
  2, 1)
• W3Cs Amaya (versions 5.3, plus concurrent
  versions)
• IBM Home Page Reader 3.0
• Others ???
• Hard Copy
• Printable (X)HTML - pagination
• Use CSS2 - ltP style"page-break-before always"gt
  (IE 4.1)
• Print via Word Processor
• Print HTML

6
Goals and Options (4)

• Support User Viewing Needs/Preferences
• Users with Disabilities
• Web Accessibility Guidelines (W3C)
• European Commission (Article 13 of the EC Treaty,
  non-discrimination)
• http//europa.eu.int/rapid/start/cgi/guesten.ksh?p
  _action.gettxtgtdoc IP/00/4770RAPIDlgEN
• US (ADA, Section 508 Rehabilitation Act
  Amendments of 1998 (Public Law 105-220)) -
  August 7, 2000
• http//www.icdri.org/SL508overview.html
• Many Other National Law Initiatives

7
Goals and Options (5)

• Keep as Simple as Possible
• User
• Point and Click in any Browser
• Provide compatibility with a set of Browser
• Editor, Contributors
• Create in XML/XHTML/HTML Using Toolsets (e.g.,
  XMLSpy, Amaya, Text Editors, )
• Create in Word Processor, Automatically
  Convert/Validate XML, HTML
• ISO Secretariat
• Assure compliance with Access Law
• Simple Maintenance and Update
• Ability to Charge Appropriately (Charge/Page,
  Charge/Byte)

8
Goals and Options (6)

• Keep as Simple as Possible
• Create a Family of ISO Documents/Formats Using
  a Single Composite XML Schema/DTD
• Standard (AP) Document
• Standard (Module) Document
• Technical Corrigenda
• Technical Specifications
• Minutes of Meetings/Workshops
• Guidance (e.g., ISO Directives, Supplementary
  Directives, Application Guidelines, Training, )
• Embed Conformance in Schema, Stylesheets,
  Validation to the Maximum Extent
• Reduce QC Checklists to Content Checking

9
Goals and Options (7)

• Minimize Number of Requirements/Guidelines
• Maintain ISO Formats and Styles
• Capture Spirit of ISO, Supplementary Directives
• Enforce Tag Semantics in XML, Reflect to Extent
  Possible in (X)HTML
• Assure/Provide Appropriate Metadata
• Dublin Core
• Keywords (for Document, for Document Sections)
• Assure All, Latest Required Text will be in
  Document
• In Referenced Files or in Stylesheets
• Enable/Define Validation Criteria and Automate
  Validation/Conformance

10
Goals and Options (8)

• Minimize ISO Resource Requirements
• Harvest Other Standards
• W3C
• DocBook
• Dublin Core
• Use Toolsets to Facilitate Document Generation
• Provide XML Schema/DTD
• Required Elements
• Provide XSL (with Required Text)
• Browser Set Compatible HTML
• Printable Files
• Convert to Other Formats

11
Goals and Options (9)

• Minimize ISO Resource Requirements
• Establish Single Website (Namespace) for XML
  Schema(s), Stylesheets,
• Semi-Automate Conversion of Legacy Documents
  (if convert at all)
• ISO Central Secretarial Review of Accessibility
  Compliance during Balloting

12
Review Alternatives for ISO Standards in HTML
(1)

• Create in WORD or WordPerfect, use conversion
  facility for HTML
• Commonly in use, familiar, proprietary
• Large files produced all styles embedded on each
  element, bookmarks, automatic numbering lost
• Create in HTML
• Contributors must know and consistently write
  (X)HTML conformant to desired validation level
  (e.g., HTML 4.01 Transitional)
• Can use simple text editor or WYSIWYG tools
  (e.g., AMAYA)
• (Some) Lack Grammar and Spell Checking

13
Review Alternatives for ISO Standards in HTML
(2)

• XML -gt XSL -gt HTML
• Create in WORD or WordPerfect, use conversion
  facility for XML, XSL for conversion to HTML
• .xml File is function of styles used (not a
  Schema/DTD)
• Few Tools for Conversion (XML Spy)
• Much Manual Editing/Tagging Required
• Create in XML, XSL for conversion to HTML
• Create or Cut and Paste from Word Processor
  into .xml file governed by Schema/DTD
• Lack of Grammar and Spell Checking, Manual
• Use Commercial XML-based Word Processor
• Not Available, StarOffice most promising, but may
  produce file bloat

14
Feasibility Test of XML-based Publication in ISO

• Used ISO 10303-28 Cover Page through Clause 5 as
  Sample
• Developed Simple XML Schema and XSL Stylesheet
• Reviewed Other Approaches (DocBook and W3C)
• Defined Schema to Use
• Defined XSL to obtain ISO look and feel and
  test Fowler (SF ISO conference) Recommended
  Minimum Tag Set
• Goal Reasonable ISO look and feel on Explorer,
  Netscape, Amaya, and IBM HPR browsers
• Reviewed for Accessibility
• Reviewed Validation of generated HTML

15
Review Other Approaches

• DocBook (In Development)
• Exceedingly Complex, Highly Parameterized DTD
• Schema under Development, No Guarantee of Upward
  Compatibility
• W3C (Beta version, Unstable, over 1 year old
  (Oct. 2000))
• Different Look and Feel
• Parameterized, Complex
• Nomenclature not Reflect ISO Terminology
• Conclusions
• Complex, Difficult for Editors, Contributors to
  Use
• Beta, Unstable Versions
• Best Insight from Building Own Schema, XSL

16
Prototype Development Philosophy

• ISO Standard Only (Not Genl Document)
• Reflect ISO Content, Structure, Nomenclature
• KISS
• Simplify Learning
• Clarity Sought over Efficiency/File Size
• Build Schema Elements as Needed
• Incorporate Document, ISO Rules in Schema
• To Extent Possible and Reasonable
• Without Undo Complication
• Build Look and Feel then Make Conform
• Accessibility (Embed and Constrain (SDs))
• Validation (W3C validator)

17
ISO_Template Schema Document Structure
18
ISO_Template Schema Clause Structure
19
ISO_Template Schema (Sub)Clause Structure
20
ISO_Template Schema Paragraph Structure
21
ISO_Template Schema Figure Structure
22
ISO_Template Schema Table Structure
23
ISO_Template Schema Bibliography Structure
24
ISO_Template Schema Cover Page Structure
25
ISO_Template Schema Metadata Structure
26
ISO_Template Schema .xml File Example
27
XSL for Conversion to HTML

• Attempted to Produce ISO Look and Feel
• Attempted to Produce ISO SF Meeting Recommended
  HTML tags
• From Fowler in San Francisco Meeting
• Identified Gaps in Tag Recommendations
• Preservation of Semantic of Tags (not misuse for
  format)
• No CSS
• Attempted to Assist Editor/Creator
• Produce MetaData, Accessibility Elements
• Automatic Table of Contents Generation
• Used Meaningful Document Content/Text for
  Identification, Anchors
• Ability to Find/Replace all Abbr, DefinedTerm
  to link to Expansions, DefiningText

28
Accessibility

• Techniques for Web content Accessibility
  Guidelines http//www.w3.org/TR/Wai-WEBCONTENT-T
  ECHS/
• 1. Provide equivalent alternatives to auditory
  and visual content.
• 2. Dont rely on color alone.
• 3. Use markup and style sheets and do so
  properly.
• 4. Clarify natural language usage.
• 5. Create tables that transform gracefully.
• 6. Ensure that pages featuring new technologies
  transform gracefully.
• 7. Ensure user control of time-sensitive content
  changes.

29
Accessibility (cont.)

• Techniques for Web content Accessibility
  Guidelines http//www.w3.org/TR/Wai-WEBCONTENT-T
  ECHS/
• 8. Ensure direct accessibility of embedded user
  interfaces.
• 9. Design for device independence.
• 10. Use interim solutions.
• 11. Use W3C technologies and guidelines.
• 12. Provide context and orientation information.
• 13. Provide clear navigation mechanisms.
• 14. Ensure that documents are clear and simple.

30
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
31
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
32
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
33
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
34
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
35
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
36
Simple Schema XSL Fowler Tag Recommendation
from SF ISO Meeting
37
XML-XSL-HTML Cover Page (1)
38
XML-XSL-HTML Table of Contents (2)
39
XML-XSL-HTML Forward w/AnnexRef (3)
40
XML-XSL-HTML Scope w/Notes in List (4)
41
XML-XSL-HTML Normative References (5)
42
XML-XSL-HTML Terms and Defn (6)
43
XML-XSL-HTML Abbreviations w/AbbrRef (7)
44
XML-XSL-HTML Example w/Code (8)
45
XML-XSL-HTML Table (9)
46
XML-XSL-HTML Annex (10)
47
XML-XSL-HTML Presentation (11)
48
XML-XSL-HTML Font Size (12)
Smaller Browser Font
Largest Browser Font
49
Findings Feasibility Test

• Use of XML for content of ISO standards appears
  FEASIBLE.
• Able to develop XML Schema for elements in ISO
  10303-28 (Thru Clause 4, Appendix A)
• Able to develop XSL to convert XML content to
  HTML that validates to HTML 4.01 Transitional and
  appears (with a little more work) to be
  validatable to 4.01 Strict.
• Generated HTML able to meet all Priority 1
  Accessibility Requirements/Checkpoints of W3C,
  Priority 2 and 3 can be achieved.
• HTML document has reasonable ISO look and
  feel

50
Findings Feasibility Test

• Organizational Challenges Identified
• Need ISO/TC184/SC4 Consensus -- wide review and
  testing
• Have own (ISO) or specialize others Schemas
• Is Master Format XML? HTML?, WORD? Or Some
  Combination
• Coverage
• Mapping Specifications
• Browser Viewable File Formats (EXPRESS-G, )
• ISO 15926
• Modules
• Usability (for Editors, Contributors)
• Conversion of Legacy, Proprietary Format
  Documents
• Following consensus
• Training and Guidelines (SDs) Needed

51
Findings Feasibility Test

• Technical Decisions/Actions Identified
• Validation of HTML (4.01 Transitional?)
• Browser Set that Must be Supported
• Requirements for IDs in Schema
• Alternate Forms of DefinedTerms (Plural,
  Capitalization, )
• Clauses, SubClauses, Annexes, SubAnnexes,
  BibliographyEntries (Needed During
  Creation/Editing)
• Development of XSL or other tools to check
  document and/assist in creation/editing.
• Manipulation of XML file
• Conversion from non-XML formats (e.g., WORD)

52
Findings Feasibility Test

• Technical Decisions/Actions Identified (cont.)
• Is Index of Terms a Requirement?
• How to resolve printable copy issue?
• Are more complex Tables needed?
• How are Notes and Examples best presented in the
  browsers
• What metadata is to be required? Dublin Core or
  other(s)?
• Will synonyms be provided in the XML Schema
  (e.g., ltpgt, ltPgt, ltparagraphgt, and/or ltParagraphgt
  elements so that author/editor preferences/
  background can be accommodated?

53
Questions, Comments, Thoughts
Can you elaborate on ? Whats Next? Id like
to add a comment/thought.
54
Supplementary DirectivesXML/XSL/HTML and Web
Accessibility Issues

• Review of SD Issues
• XML/XSL/HTML
• W3C Accessibility Checkpoints by Priority
  (1,2,3)
• with Potential Solution Suggestions

55
Supplementary Directives and XML/HTML Issues

• Need to develop additional material for the SDs
  that states the XML/HTML tags and tools to use
  for each element that can occur in a standard
• XML
• Must Provide/Define/Maintain Schema or DTD
• XSL
• Must Provide/Maintain Stylesheet(s)
• HTML
• Must specify validation of HTML
• Must state association of tags with semantics and
  what tags to use and not to use for formatting
• Assure Accessibility to Content of HTML Document
• Tools to Use for Authoring, Checking, Converting

56
Supplementary Directives and XML/HTML Issues

• XML Schema/DTD
• Have Prototype XML Schema with XSL to produce
  HTML (HTML 4.01 Transitional valid)
• Only Tested with Sample of Part 28
• Need to Conduct Review and Testing
• Scope Must be Defined (10303, SC4, TC184, ISO)
• Need Consensus/Harmonization
• Definition of Elements/Schema(s)
• Need Guidance Document
• Definition of XML Schema(s) to be used
• How to Use
• How to Revise/Modify

57
Supplementary Directives and XML/HTML Issues

• XSL
• Have Prototype XML Schema with XSL to produce
  HTML (HTML 4.01 Transitional valid)
• Output Only Tested with Sample of Part 28
• OK in IE 5.5, Netscape 6, AMAYA, IBM HPR 3.0
• Need to Conduct More Review and Testing?
• Need Consensus/Harmonization on Browser Set to
  (Visually Verify)
• Need Guidance Document
• Definition of HTML Tags to Use for Schema
  Elements
• Definition of Testing Required (QC Checklist
  Item?)
• How to Revise/Modify/Upgrade

58
Supplementary Directives and XML/HTML Issues

• (X)HTML
• Have Prototype XML Schema with XSL to produce
  HTML (HTML 4.01 Transitional valid)
• Appears that HTML 4.01 Strict could be achived
• NOTE While use of borderon attribute for
  table validates, it produces a parsing error with
  AMAYA (border must be pixels in IMG, OBJ in 4.01
  REC)
• Need Consensus/Harmonization of Validation Level
• Need Guidance Document
• Definition of tags and what they mean/are used
  for
• If HTML authored, converted from other format
  (Problem with proprietary word processor based
  conversions)
• How to Revise/Modify/Remain Compatible

59
Supplementary Directives and XML/HTML Issues

• Tools
• Have Prototype XML Schema with XSL to produce
  HTML (HTML 4.01 Transitional valid)
• Used XML Spy (Suite 500 US)
• Produce .xml by Cut and Paste from WORD
  document.
• Reasonable, Some crashes
• Produce .xml by import of WORD document
• Dependant on degree of agreement of styles in
  WORD and Elements in XML Schema
• Dependant on use/need for import of WORD
  proprietary features, e.g., autonumber,
  cross-references, autorecognize links, bookmarks,
• Need Consensus/Harmonization
• Need Guidance Document
• What Tools Available/Cost/Features
• How to Use (Strengths and Weaknesses)
• How to Revise/Modify List

60
Supplementary Directives and XML/HTML
Accessibility Issues

• W3C has produced HTML Techniques for Web Content
  Accessibility Guidelines 1.0
• Following slides suggest ways to meet guidelines
  in the order the guidance/checkpoints presented
  in this document.
• SD -gt Supplementary Directives Must Enforce
• XML -gt Schema Can Enforce
• XSL -gt Stylesheet Can Enforce
• HTML -gt Validation of HTML Can Enforce (If
  directly authored in HTML, XML and XSL
  Enforcement not Possible)
• Other W3C documents exist
• CSS Techniques, Core Techniques. XML Techniques

61
Accessibility Requirements

• Priority 1
• Clearly identify changes in the natural language
  of a documents text and any text equivalents
  (e.g., captions).
• SD Soln 1-
• Only English Allowed in ISO Documents
• XML/XSL/HTML Soln 2
• Add Language Element Tag, Embed in HTML as
  lang attribute on SPAN or DIV

62
Accessibility Requirements

• Priority 1 (cont.)
• Provide text equivalent for every non-text
  element (e.g., via alt, longdesc, or in
  element content.
• This includes images,
• XML Soln Required FigureDescription and
  TableDescription elements in Schema (used for
  altand summary attributes respectively)
• graphical representations of text (including
  symbols),
• SD Soln Not Allowed
• image map regions,
• SD Soln Not Allowed
• animations (e.g., animated .gifs),
• SD Soln Not Allowed
• applets and programmatic objects
• SD/XML Soln Not Allowed

63
Accessibility Requirements

• Priority 1 (cont.)
• Provide text equivalent for every non-text
  element (e.g., via alt, longdesc, or in
  element content.
• This includes (cont.)
• ASCII art
• SD Soln Not Allowed
• images used as list bullets
• SD/XML Soln Not Allowed
• spacers
• SD/XML Soln Required
• Graphical buttons
• SD Soln Not Allowed
• Sounds (played with or without user interaction)
• SD /XML Soln Not Allowed

64
Accessibility Requirements

• Priority 1 (cont.)
• Provide text equivalent for every non-text
  element (e.g., via alt, longdesc, or in
  element content.
• This includes (cont.)
• stand-alone audio files
• SD Soln Not Allowed
• audio tracks of video
• SD Soln Not Allowed
• and video.
• SD Soln Not Allowed

65
Accessibility Requirements

• Priority 1 (cont.)
• For data tables, identify row and column headers.
• XML Soln -- Done in XSL, ColumnHeading scope
  attributes
• For data tables that have two or more logical
  levels of row or column headers, use markup to
  associate data cells and header cells
• SD/XML Soln Not Allowed May need to
  reconsider.
• Provide client-side image maps instead of
  server-side image maps except where the regions
  cannot be defined with an available geometric
  shape.
• SD Soln Not Allow image maps.

66
Accessibility Requirements

• Priority 1 (cont.)
• Provide redundant text links for each active
  region of a server-side map.
• SD Soln Not Allow image maps.
• Ensure that equivalents for dynamic content are
  updated when dynamic content changes.
• SD Soln Not Allow dynamic content.
• Ensure that pages are useable when scripts,
  applets, or other programmatic objects are turned
  off or not supported. If this is not possible,
  provide equivalent information on an alternative
  accessible page.
• SD/XML Soln Not Allow scripts, applets, or
  other programmatic objects.

67
Accessibility Requirements

• Priority 1 (cont.)
• Until user agents allow users to control
  flickering, avoid causing the screen to flicker.
• SD Soln Flickering Elements Not Allowed
• For any time-based multimedia presentation,
  (e.g., a movie or animation), synchronize
  equivalent alternatives (e.g., captions or
  auditory descriptions of the visual track with
  the presentation.
• SD Soln Multimedia Not Allowed
• Title each frame to facilitate frame
  identification and navigation
• SD/XML Soln Frames Not Allowed Impact on AMs

68
Accessibility Requirements

• Priority 1 (cont.)
• Make programmatic elements such as scripts and
  applets directly accessible or compatible with
  assistive technologies.
• SD/XML Soln Priority 1 if functionality is
  important and not presented elsewhere, otherwise
  Priority 2
• scripts and applets not allowed.

69
Accessibility Requirements

• Priority 2
• Document structure and metadata
• TITLE, Address, Meta, Link elements
• XML Soln - Dublin Core Metadata Made Mandatory
  Elements
• Mandatory lttitlegt element
• Address of dc.creator in header, contributors in
  header
• No periodic refresh or auto redirect allowed
• Validate to published formal grammars
• XSL Soln --Demonstration validated to HTML 4.01
  Transitional
• http//validator.w3.org/
• SD Soln --Demonstration Reviewed for
  Accesibility
• http//www.temple.edu/inst_disabilities/piat/wave/
  index.html
• Ensure Dynamic Content is accesible
• SD Soln No dynamic content allowed.

70
Accessibility Requirements

• Priority 2 (cont.)
• Divide large blocks of information into more
  manageable groups
• XML/XSL Soln -- Section headings create
  structured document with automatic ToC. (although
  sequence is not strictly enforced (h1 -gt h2 -gt h3
  ...)
• XML Soln -- All tables have summary attribute
  required
• XML Soln -- Nested lists (although numbering can
  be made more accessible)
• XML Soln -- ltParagraphsgt, ltExamplegt, ltNotegt,
  ltClausegt, ltSubnClausegt, ltAnnexgt, ltSubnAnnexgt
  elements used to organize text into logical units.

71
Accessibility Requirements

• Priority 2 (cont.)
• Use style sheets to control layout and
  presentation
• Use ltemgt and ltstronggt for structural emphasis -
  avoid ltbgt and ltigt -
• XSL Soln Only ltemgt and ltstronggt tags
  generated.
• Specify expansion of each abbreviation in
  document where it first occurs.
• XML Soln Clause 3 used for abbreviations,
  facility to link to expansion throughout document
  available.
• XML Soln -- Use of Abbr in Table Headings not
  yet implemented.
• Markup quotations. Do not use quotation markup
  for formatting.
• XML Soln ltLongQuotegt (ltblockquotegt) and
  ltShortQuotegt (lt_____gt) elements used -- ltqgt
  not recognized by IE

72
Accessibility Requirements

• Priority 2 (cont.)
• When an appropriate markup language exists, use
  markup rather than images (e.g., math equations)
  to convey infromation.
• ??? Soln -- No requirements identified, not
  implemented in demonstration.
• Mark-up lists and list items properly.
• XML Soln only ltdlgt, ltulgt. ltolgt used for lists,
  not used for indentation.
• NOTE numbering using compound numbers
  recommended by W3C, not implemented in
  demonstration.

73
Accessibility Requirements

• Priority 2 (cont.)
• Do not use tables for layout unless the table
  makes sense when linearized, do not use
  structural markup for formatting
• XML Soln -- ltTablegt element used for tables, can
  contain structure in Cells (not used to format)
• XSL Soln -- ltNotegt and ltExamplegt displayed as
  single cell table with summary indicating that
  table is for formatting of non-normative text.
• HTML Soln -- Linearization Tested with IBM Home
  Page Reader 3.0
• Reading of table headings not achieved in HPR 3.0
• Structural Markup read acceptably.

74
Accessibility Requirements

• Priority 2 (cont.)
• Clearly identify targets of links
• SD Soln all links identified using meaningful
  (to reader) text, e.g., ltAbbrgt, ltDefinedTermgt,
  External links cannot be controlled by markup
• Do not use pop-ups or other windows that appear
  without informing user
• SD/XML Soln Not allowed.
• Avoid movement/animation in pages.
• SD Soln Not allowed.
• Make programmatic elements such as scripts and
  applets directly accessible or compatible with
  assistive technologies Priority 2 if
  functionality is noimportant
• SD/XML Soln Not allowed

75
Accessibility Requirements

• Priority 2 (cont.)
• Mark-up
• Use relative rather than absolute units in
  attributes and style sheets
• XSL Soln relative units used throughout
  prototype
• For applets and scripts ensure event handlers are
  device-independent
• SD/XML Soln Applets and Scripts not allowed.
• Assure dynamic content is accessible.
• SD Soln Dynamic content not allowed.
• Avoid blinking content.
• SD Soln Blinking content not allowed.
• Do not create automatic refreshing of pages
• SD Soln Automatic refresh not allowed.

76
Accessibility Requirements

• Priority 2 (cont.)
• Mark-up
• Ensure that any element that has its own
  interface can be operated in a device-independent
  manner.
• SD Soln no interface elements allowed.
• Avoid Pop-ups or changing windows without
  informing user
• SD Soln Popups and window changes not allowed.
• Describe frames and their relationships
• SD/XML Soln Frames not allowed in HTML 4.01
  Transitional.
• Associate labels explicitly with their controls,
  ensure control is properly located
• SD Soln Controls not allowed.

77
Accessibility Requirements

• Priority 2 (cont.)
• Avoid deprecated features of W3C technologies
• SD Soln Require validation using W3C
  validators.

78
Accessibility Requirements

• Priority 3
• Provide information on document collections
• SD/XML Soln Publish as single document/page
  with (only) figure file references.
• Identify primary natural language of document.
• XML Soln en as lang attribute of html
  document, ltAltLanguagegt element to be
  investigated.
• Specify expansion of each abbreviation where it
  first occurs
• SD/XML/XSL Soln Define all abbreviations in
  Clause 3, use mechanism to link all occurrences
  of abbreviation to expansion in Clause 3
  (ltAbbrRefgt)

79
Accessibility Requirements

• Priority 3
• Provide summaries for tables and abbreviations
  for header labels
• XML/XSL Soln summary required for tables, in
  XSL for tables used for formatting (Notes, )
• Abbreviations for table headers not yet
  implemented.
• Group related links, identify the group and
  provide a way to by-pass the group.
• ?? Soln -- Not implemented could provide
  bypass of ToC
• Include non-link, printable characters between
  adjacent links
• SD/XML Soln Comma separation of series of
  links, not enforceable by XLS but refs fail if
  not conform

80
Accessibility Requirements

• Priority 3
• Create a logical tab order through links, form
  controls and objects Provide keyboard shortcuts
  to important links
• XML/XSL Soln Shortcuts Not yet addressed, Tab
  order is acceptable
• Provide a means to skip over multi-line ASCII
  art
• SD Soln ASCII art not allowed.
• Provide redundant text links for each active
  region of a client-side image map
• SD Soln -- Image maps not allowed for
  navigation.

81
Accessibility Requirements

• Priority 3
• Assure foreground and background color
  combinations for text provide sufficent contrast
  (for those with color deficits) and on black and
  white screen)
• SD XSL Soln Black text on white background
  only in XSL except for Notes and Examples
  (colored background contrast must be verified.
• Include default, place holding characters in edit
  boxes and text areas
• SD/XML Soln Text and edit boxes not allowed.

82
Findings Feasibility Test

• Use of XML for content of ISO standards appears
  FEASIBLE.
• Able to develop XML Schema for elements in ISO
  10303-28 (Thru Clause 4, Appendix A)
• Able to develop XSL to convert XML content to
  HTML that validates to HTML 4.01 Transitional and
  appears (with a little more work) to be
  validatable to 4.01 Strict.
• Generated HTML able to meet all Priority 1
  Accessibility Requirements/Checkpoints of W3C,
  Priority 2 and 3 can be achieved.
• HTML document has reasonable ISO look and
  feel

83
Organizational Challenges

• Need ISO/TC184/SC4 Consensus -- wide review and
  testing
• Is Master Format XML? HTML?, WORD? Or Some
  Combination -- Is XML HTML Needed/Desired?
• Have own (ISO) or specialize others Schemas
• Coverage
• Mapping Specifications
• Browser Viewable File Formats (EXPRESS_G, )
• ISO 15926
• Modules
• Usability (for Editors, Contributors)
• Conversion of Legacy, Proprietary Format
  Documents
• Following consensus
• Training and Guidelines (SDs) Needed

84
Technical Decisions/Actions

• Validation of HTML (4.01 Transitional?)
• Browser Set that Must be Supported
• Requirements for IDs in Schema
• Alternate Forms of DefinedTerms (Plural,
  Capitalization, )
• Clauses, SubClauses, Annexes, SubAnnexes,
  BibliographyEntries (Needed During
  Creation/Editing)
• Development of XSL or other tools to check
  document and/assist in creation/editing.
• Manipulation of XML file
• Conversion from non-XML formats (e.g., WORD)

85
Technical Decisions/Actions Identified (cont.)

• Is Index of Terms a Requirement?
• How to resolve printable copy issue?
• Are more complex Tables needed?
• How are Notes and Examples best presented in the
  browsers
• What metadata is to be required? Dublin Core or
  other(s)?
• Will synonyms be provided in the XML Schema
  (e.g., ltpgt, ltPgt, ltparagraphgt, and/or ltParagraphgt
  elements so that author/editor preferences/
  background can be accommodated?

86
Questions, Comments, Thoughts
Can you elaborate on ? Whats Next? Id like
to add a comment/thought.