Docstoc

htm_code_

Document Sample
htm_code_ Powered By Docstoc
					<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html lang="en">
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-16">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>ISO TC184/SC4 on Industrial Data          © ISO 2002 - All rights reserved</title>
<meta name="DC.Title" content="Guidelines for publication of ISO TC184/SC4 documents in HTML">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#title">
<meta name="DC.Title.Alternative" content="HTML Guidelines">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#title">
<meta name="DC.Creator" content="ISO Central Secretariat">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#creator">
<meta name="DC.Creator.Address" content="central@isocs.iso.ch">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#creator">
<meta name="DC.Subject" content="publication guidelines">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#subject">
<meta name="DC.Subject" content="HTML publication">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#subject">
<meta name="DC.Description" content="An ISO standing document to guide authors and editors in publishing documents in
HTML.">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#description">
<meta name="DC.Publisher" content="ISO">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#publisher">
<meta name="DC.Publisher.Address" content="central@isocs.iso.ch">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#publisher">
<meta name="DC.Contributor" content="Gerry Radack">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#contributor">
<meta name="DC.Contributor.Address" content="gradack@ctc.com">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#contributor">
<meta name="DC.Contributor" content="Others">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#contributor">
<meta name="DC.Contributor.Address" content="yyy@xxx.uk">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#contributor">
<meta name="DC.Date" SCHEME="ISO8601" content="2002-03-26">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#date">
<meta name="DC.Type" content="xml">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#type">
<meta name="DC.Format" SCHEME="IMT" content="NEED TO CHECK HOW THIS IS TO BE EXPRESSEDl">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#format">
<link rel="SCHEMA.imt" href="http://sunsite.auc.dk/RFC/rfc/rfc2046.html">
<meta name="DC.Identifier" content=" ISO TC184/SC4 QC N233">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#identifier">
<meta name="DC.Identifier" SCHEME="URN" content="ISO%2010303-28">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#identifier">
<meta name="DC.Source" content="ISO Sales Office">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#source">
<meta name="DC.Language" SCHEME="ISO639-1" content="en">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#language">
<meta name="DC.Relation" content="Relation Unknown">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#relation">
<meta name="DC.Coverage" content="Covers all EXPRESS to XML DTD Mapping">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#coverage">
<meta name="DC.Rights" content="Copyright ISO 2002">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#rights">
<meta name="DC.Date.X-MetadataLastModified" SCHEME="ISO8601" content="2002-02-07">
<link rel="SCHEMA.dc" href="http://purl.org/metadata/dublin_core_elements#date">
</head>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The header and the cover page were added to the draft document of 2002-03-13
for illustration/completeness. Header is centered and indented as it cannot be fully justified and print out in both Netscape
and Explorer without line wrapping in one or the other. Wording in the copyright notice is general -- First sentance
references to technical specification, international standard removed so one statement could handle all.</td>
</tr>
</table><br><hr><h3 align="center">DRAFT STANDING DOCUMENT                                       © ISO 2002 - All rights
reserved</h3><hr><br><h1>ISO TC184/SC4 Standing Document -
         Guidelines for the format and layout of SC4 standards using HTML</h1>
<h2>ISO TC184/SC4/QC N233</h2>
<p>2002-03-28</p>
<p>Supercedes: Document reviews and suggests changes for consideration against the 2002-03-13 DRAFT of this
document.</p><br><table align="center" border="1" cellspacing="0" cellpadding="0">
<tr>
<td colspan="2" valign="middle">
<h3>COPYRIGHT NOTICE</h3>
<p>This ISO document is copyright protected by ISO. While the reproduction of ISO copyright protected materials in any
form for use by participants in the ISO standards development process is permitted without prior permission from ISO,
neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose
without prior written permission from ISO.</p>
<p>Requests for permission to reproduce should be addressed to ISO at the address below or ISO's member body in the
country of the requester:</p>
<p align="center">Copyright Manager, ISO Central Secretariat, 1 rue de Varembe, CH-1211 Geneva 20, Switzerland<br>
                 telephone: +41 22 749 0111, telefacsimile: +41 22 734 0179<br>
                 Internet: <a href="central@isocs.iso.ch"> central@isocs.iso.ch</a>, X.400: c=ch; a=400net; p=iso; o=isocs;
s=central<br>
                 Web Address: <a href="www.iso.ch">www.iso.ch</a></p>
<p>Reproduction for sales purposes for any of the above-mentioned documents may be subject to royalty payments or a
licensing agreement.Violators may be prosecuted.</p><br></td>
</tr>
<tr>
<td colspan="2" valign="middle">
<h3>ABSTRACT</h3>
<p>This ISO TC 184/SC4 standing document provides rules and guidance on the publication of ISO TC184/SC4 standards,
technical specifications, and standing documents in html. It provides and conforms to the ISO TC184/SC4 rules for
publishing documents for international review and approval in .html format.</p><br></td>
</tr>
<tr>
<td colspan="2" valign="middle">
<h3>KEYWORDS</h3>
<p>HTML Guidelines,
                          HTML Publication of ISO Standards,
                          ISO TC184/SC4 Standing Document,
                          </p><br></td>
</tr>
<tr>
<td colspan="2" valign="middle">
<h3>COMMENTS TO READER</h3>
<p>Readers are cautioned that this document reflects html development up to and including the HTML 4.01
Recommendation of the W3C and some elements may not be viewable on browsers that cannot present all HTML 4.01
elements.</p><br></td>
</tr>
<tr>
<td align="center" colspan="1" valign="middle">
<h3>Project Leader</h3><small>Gerry Radack<br>CTC Corporation<br>Street<br>City, State,
nnnnn-nnnn<br>USA<br><br>+01 aaa/lll-nnnn<br>+01 aaa/lll-nnnn<br><a
href="mailto:graddack@ctc.com">graddack@ctc.com</a><br><br></small></td>
<td align="center" colspan="1" valign="middle">
<h3>Editor</h3><small>Gerry Radack<br>CTC Corporation<br>Street<br>City, State, nnnnn-nnnn<br>USA<br><br>+01
aaa/lll-nnnn<br>+01 aaa/lll-nnnn<br><a href="mailto:graddack@ctc.com">graddack@ctc.com</a><br><br></small></td>
</tr>
</table>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Brazy </em><p>ISSUE: 1</p>
<p>AUTHOR: Brazy</p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: Add meta tags to HTML document to indicate author,title, subject, date, and keywords.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td> Example:
<pre><code>&lt;META name="title" content="Guidelines for the format and layout of SC4
standards using HTML 2002-03-12"&gt;
&lt;META name ="subject" content="Guidelines for the format and layout of SC4
standards using HTML"&gt;
&lt;META name="date" content="2002-03-12"&gt;
&lt;META name="author" content="Radack, Gerry"&gt;
&lt;META name="description" content="This standing document specifies
requirements for the HTML markup of standards developed by ISO TC184/SC4."&gt;
&lt;META name="keywords" content="ISO TC184/SC4, industrial data, standards,
QC, qcn233, HTML guidelines, SC4 standards"&gt;</code></pre><br></td>
</tr>
</table><br><p>PROPOSED SOLUTION: </p>
<p>DISCUSSION: See Nazemetz comment in his comments at <a href="#ClauseRefMetadata and Use of Background
Color ">Metadata and Use of Background Color </a></p>
<p>RESOLUTION:</p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: GOSET </em><p>ISSUE: 4</p>
<p>AUTHOR: GOSET</p>
<p>CLAUSE: General</p>
<p>ALTERNATE CLAUSE: </p>
<p>CLASSIFICATION: MINOR/fundamental</p>
<p>DESCRIPTION: The HTML guidelines misses to specify guidelines for the main aspect of HTML documents, i.e. the
ability to navigate in a multi-files document. For example, the only version of AP214 which is considered as useful is its
HTML version. This version is felt useful not because of the format of texts in every pages but because of the wide
capabilities to navigate in the whole AP. Such an organization of the documentation should be used as a model for the other
SC4 HTML documents and in particular for the other APs. Otherwise, the present guidelines would be inconsistent with the
only AP marketed by ISO with an HTML version. They would also be far from providing the navigation capabilities that have
been experienced within AP214 and proved to be useful and necessary.</p>
<p>PROPOSED SOLUTION: Use the HTML version of AP214 as the model for structuring and providing navigation
capabilities in an SC4 HTML document.</p>
<p>Note: of course the structure may need to be adapted for the case Integrated resources documents.</p>
<p>DISCUSSION: See Nazemetz comment on <a href="#ClauseRefGuidelines as Example">Guidelines as
Example</a></p>
<p>RESOLUTION: </p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: John Nazemetz </em><h3>General Comments <a name="ClauseRefGeneral
Comments"></a>from Nazemetz [<a href="#0">Top</a>]</h3>
<p>Background/FYI --This .html document was produced using a prototype XML Schema and XSL and, for the most part
faithfully presents/reflects the content of the draft document provided for a four-week review by Gerry Radack and sent out
via e-mail by Thomas Warren, Coordinator of the ISO TC 184/SC4 Quality Committee on 2002-03-13. I tried to document
all added/modified text/content in comments immediately following the changes. The rationale for the use of an XML
schema was to enhance my personal ISO-related XML schema experiences and have the ability to experiment/study the
.html options using XSLs. The use of XSL permitted rapid and consistently encoded changes (in the .html) without any
(laborious and inconsistent) manual editing the .html code. I tried to incorporate the accessibility requirements of the W3C
WAI into the XML schema and, via XSL, ihe .html encoding of these guidelines as I had outlined at the Myrtle Beach
Meeting [<a href="http://www.tc184-sc4.org/SC4_Open/SC4_and_Working_Groups/QC/N-DOCS/">[(QCn231)]</a>]. I also
wanted to study the applicability of the prototype and the robustness of the elements in the prototype schema developed
using the Part 28 document to additional ISO TC184/SC4 documents and gain insight into the requirements for an ISO
xml-based document production process. I also did a quick review of the .html of Part 25 that is currently under ballot.
The procedures and documentation for this approach can be added to this standing document as an informative annex, if
desired by the authoring and review committee for this document. I am willing to try to author such as set of annexes and
provide the xsl, xsd, html, and other files that I have to assist others in experimenting with xml/xsl for ISO document
publication. I hypothesize that we will have a much better set of HTML guidelines if we do some "look-ahead" to a possible
xml/xsl publication environment.</p>
<p>I created a website that has all of the documents and files I created in this prototype test. The site is available through
<a href="http://www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/GuidelinesDocuments">OSU</a>. There are two
webpages that allows you to view the documents</p>
<ul>
<li> first allows <a
href="http:www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/GuidelinesDocuments\Comparison.html">side-by-side</a>
viewing so that you can easily compare the various format options, the input/output/coding etc. To take advantage of this,
you need a 1200 pixel or better display.</li>
<li>the second is for those of you will less screen resolution and is a <a
href="http:www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/GuidelinesDocuments\Display.html">single window/frame
display</a>.</li>
</ul>
<p>I particularly recommend the review of the ISODraftDocumentDocumentation.html file -- it is a graphical display of the
xml schema I devised for this stydy -- one needs not know any xml to follow the structure -- I suggest that you visit the site
and when you open the file, first clisk on ISODocumentTemplate and then on the plus (+) signs in the small boxes to
navigate through the structure. I appreciate any commments (<a
href="mailto:jnazeme@okstate.edu">jnazeme@okstate.edu</a>.</p>
<h4> XML Concept/Context <a name="ClauseRefXML Concept/Context"></a>from Nazemetz [<a
href="#0">Top</a>]</h4>
<p> In order to facilitate other reviewers' understanding of my concept of an xml/xsl-based publication environment for ISO,
I am provideing a brief listing of an activity model concept:</p>
<ol>
<li>The concept/NWI is produced and approved. An .xml instance document containing the header, cover sheet, table of
contents, foreword, introduction, and scope information and a listing/outline of all (projected) clauses, subclauses, annexes,
subannexes, ... is produced.</li>
<li>Authoring reponsibilities are assigned and each author creates his/her content in a copy of the .xml instance
document.</li>
<li>[Optional] Some/each author's content is reviewed using ISO .xml editing tools and procedures (that is, reviewers insert
comments into copies of the instance documents), the author consolidates, evaluates, and incorporates the input into his/her
section of the document -- E-mail exploders can/will still be used for resolution of (focused) issues as we do today.</li>
<li>The editor consolidates all author input into a single ISODocument-schema-conforming document with all cross
references (hyperlinks) and numbering consistent and complete. Both an.xml and an .html version are made available to
reviewers.</li>
<li>The CD is distributed and comments are collected. Comments are submitted on ballot comment forms by those
reviewers using the .html version as there is no simple way to automatically identify comments that are/may be imbedded in
an .html instance file. Reviewers using the .xml versions have two options for submitting comments: using the ballot
comment forms or inserting them into an .xml document (as I did in this experiment and applying a style sheet to obtain the
desired presentation in .html). The comments inserted in the .xml are contained in semantically-identified elements
conforming to the document schema in copies of the balloted instance file (with identity so that they can be consolidated
without loss of source) and the comments can be either stripped out of the document onto ballot comment forms or all
comments (from multiple reviewers, multiple instance documents) consolidated into a single instance document. This
process will allow a transition to .xml based document production that provides for current practices to be continued as new
practices are undertaken.</li>
<li>The comments are resolved and an ISODocument-schema-conformant document is produced for additional review or
publication.</li>
<li>[Optional] Publication and distribution can be made in various forms that are automatically derived from the master (.xml)
file. These forms could be, but are not limited to, single (.html) file documents for CD distribution, packeted documents (for
example, each clause in a separate file for quick download, encripted files in publicly available websites with the decription
key sold by ISO Central Secretariat, etc.).</li>
<li>After some period of time, a required review or resolution of SEDs issues causes the cycle to repeated. During this cycle
repetition, the document/sections of the document are (re)drafted, reviewed using the .xml and/or .html versions, comments
consolidated, and review/ballot cycles executed. The evolution of the document (configuration management) is
documented and preserved for historical records.</li>
</ol>
<p>The functions and resulting files/content needed for an xml/xsl publication environment and their status (based on this
experiment) are outlined below and those that have been drafted are available for viewing at <a
href="http://www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/Comparison.html">my OSU website</a>.</p><br><a
name="TableRef"></a><table width="100%" border="1" summary="List of all .xml, .xsl., .html files used in this review/study."
align="center">
<tr>
<th scope="col" colspan="1" align="center">File</th>
<th scope="col" colspan="1" align="center">Status</th>
<th scope="col" colspan="1" align="center">Purpose/Content</th>
</tr>
<tr>
<td colspan="1" align="center">ISODocument.xsd</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This file provides and XML schema that can be used to validate documents prior to
review/ballot. All major document elements (and their substructures), block elments, hyperlinked elements, navigation
elements, documentation elements, and configuration management elements are in the schema. No editing elements
(comments, inserts, deletes) are allowed in the final document by the schema and thus the schema can be used in the
project's internal review to assure document conformance to the guidelines as the schema will enforce this
conformance.</td>
</tr>
<tr>
<td colspan="1" align="center">ISODocumentDocumentation.html</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the XML Spy-generated documentation for the ISODocument schema.</td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocument.xsd</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides an XML schema that can be used to validate documents that are being
reviewed. All major document elements (and their substructures), block elments, hyperlinked elements, navigation
elements, documentation elements, and configuration management elements are in the schema. All previous history of
approved changes (that is through TCs, SEDS, and/or new editions) are/can be included in the schema/document. Editing
elements (comments, inserts, deletes) are allowed in the schema and these elements allow the reviewers to comment in the
document at the location of the concern -- the schema requires the reviewers to identify themselves and reviewers
can/should put all their input into the comments so that all comments from all reviewers can be (automatically) consolidated
and the comment review/editor can then resolve each comment (by modifing the non-comment text) -- using the
ISODocument.xsd will assure that all comments have been dealt with before sending the document out for
review/ballot/publication. The document structure and required elements as defined by the ISODocument.xsd and are
enforced by the ISODraftDocument.xsd so that reviewer comments can contain directly useable, conforming encodings for
content. <table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate
informative text of example from surrounding text.">
<tr>
<td>EXAMPLE              As an example, this table, even in an example conforms to the schema (it must have a
TableDescription for the visually impaired, TableIdentifier, TableTitle, ... as required in the schema -- had it been produced
by a reviewing process as a "suggested solution" to an identified problem, the editor could, upon acceptance of the
suggested solution, simply cut and paste it into the normative portion of the instance document (in .html or .xml), assured
that it is correctly coded/conforming. </td>
</tr>
</table><br></td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocumentDocumentation.html</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the XML Spy-generated (tool I used, not to be interpreted as a commercial
endorsement) documentation for the ISODraftDocument schema.</td>
</tr>
<tr>
<td colspan="1" align="center">ISODocument.xsl</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides an XSL (XML style sheet) that transforms the instance data (.xml) into .html.
It ignores all editing elements when producing the .html so that it can be applied to either an ISODocument.xsd-conforming
.xml file or an ISODraftDocument.xsd-conforming .xml file and produce "reviewable/ballotable" .html. </td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocumentShowAllElements.xsl</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides an XSL (XML style sheet) that transforms the instance data (.xml) into .html.
It will present all editing and document history elements when producing the .html so that it can be applied to either an
ISODocument.xsd-conforming .xml file or an ISODraftDocument.xsd-conforming .xml file and produce an .html that would
have the same "look and feel" as this document.</td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocumentCommentsOnly.xsl</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides an XSL (XML style sheet) that transforms the instance data (.xml) into .html.
It will present only the comments (no history elements) when producing the .html. It can be applied to either an
ISODocument.xsd-conforming .xml file or an ISODraftDocument.xsd-conforming .xml file and produce an .html that would
have the same "look and feel" as this document.</td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocumentWithStyles.xsl</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This file, when/if drafted, will provide an XSL (XML style sheet) that transforms the instance
data (.xml) into .html. It will present all editing elements and encode <code>style</code> attributes that provide sematic
meaning of selected elements when producing the .html so that the .html file can be used as input to WORD if the committe
so desires this functionality. The style sheet can be applied to either an ISODocument.xsd-conforming .xml file or an
ISODraftDocument.xsd-conforming .xml file and will produce an .html that would have a similar "look and feel" to this
document.</td>
</tr>
<tr>
<td colspan="1" align="center">Guidelines.xml</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the instance data for the guidelines document conforming to the
ISODraftDocument.xsd. The XML style sheets is used to produce the desired .html presentation (i.e., with or without
comments). </td>
</tr>
<tr>
<td colspan="1" align="center">GuidelinesWithCommentsAndHistory.html</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the .html encoding of the guidelines document conforming to the
ISODraftDocument.xsd. The XML style sheet, ISODraftDocumentShowAllElements.xsl, is used to produce the .html
presentation (with comments, e.g., this document). </td>
</tr>
<tr>
<td colspan="1" align="center">GuidelinesWithoutComments.html</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the .html encoding of the guidelines document conforming to the
ISODraftDocument.xsd (or the ISODocument.xsd). The XML style sheet, ISODocument.xsl, was used to produced the
.html presentation (without comments). </td>
</tr>
<tr>
<td colspan="1" align="center">GuidelinesCommentsOnly.html</td>
<td colspan="1" align="center">Drafted</td>
<td colspan="1" align="left">This file provides the .html encoding of the guidelines document conforming to the
ISODraftDocument.xsd (or the ISODocument.xsd). The XML style sheet, ISODraftDocumentCommentsOnly.xsl, was used
to produced the .html presentation (only comments, examples and notes.). </td>
</tr>
<tr>
<td colspan="1" align="center">NumberingAndCrossReference.xsl</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This tool, when drafted, will provide the ability to automatically check and update all clause
and annex numbering and associated cross references (hyperlinks). It will also provide automated assistance in validating
defined term, abbreviation, bibliographic, and index reference integrity. </td>
</tr>
<tr>
<td colspan="1" align="center">GuidelinesWithCommentsAndStyles.html</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This tool, when drafted, will provide the .html encoding of the guidelines document conforming
to the ISODraftDocument.xsd and includes<code> style</code> attributes on the <code>&lt;hn&gt;</code> and
<code>&lt;p&gt;</code> elements for major (logical) sections of the document.</td>
</tr>
<tr>
<td colspan="1" align="center">InstanceDocumentConsolidation.java</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This tool, when drafted, would provide an ability for the edtor to merge the comments in multiple
instance (xxx.xml) files conforming to the ISODraftDocument.xsd into a single document with all comments (reviewers shall
put all their input in <code>Comment</code> elements) located appropriately so that he/she and others on the editing
committee can see and address all comments without having to view multiple files or scroll through long documents. The
output of this tool would be an InstanceDocumentConsolidation.xml instance file that would conform to the
ISODraftDocument.xsd. <table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table
used to contain informative text of note from surrounding text.">
<tr>
<td>NOTE -- this may not need to be in java, but some sort of SAX or DOM parsing will likely be used/required. </td>
</tr>
</table><br></td>
</tr>
<tr>
<td colspan="1" align="center">ISODraftDocumentToWORD.xsl</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This file/tool will, when drafted, provide a means to transform an ISODraftDocument.xsd
conforming instance (.xml) file to WORD, WordPerfect, or StarOffice. This may become moot as these
commericial/proprietary word processors incorporate/allow .xml to be produced/imported (promised in their next
versions).</td>
</tr>
<tr>
<td colspan="1" align="center">WORDToISODRAFTDocument.xsl</td>
<td colspan="1" align="center">Not Drafted</td>
<td colspan="1" align="left">This file/tool will, when drafted, provide a means to transform from a WORD or WordPerfect to
an ISODraftDocument.xsd conforming instance (.xml) file. It may be necessary to define a set of WORD/WordPerfect
styles and have the proper styles applied before the transformation. This may become moot as these
commericial/proprietary word processors incorporate/allow .xml to be produced/imported (promised in their next
versions).</td>
</tr>
</table><br><h3 align="center">Table - Files needed in an .xml-based ISO document creation process and their
status</h3>
<h4> Observations and Comments <a name="ClauseRefObservations and Comments"></a>from Nazemetz [<a
href="#0">Top</a>]</h4>
<p>The following are my comments/observations on the document. Additional, specific comments are provided at
appropriate locations in the material. </p>
<h5>       Non-conformance of this Draft to its own Rules <a name="ClauseRefNon-conformance of this Draft to its own
Rules"></a>from Nazemetz [<a href="#0">Top</a>]</h5>
<ul>
<li>It is imperative that the .html Guidelines document conform to its own rules and the applicable portions of the
Supplementary Directives. This is true for both the .html encoding as well as browser presentation. Several failures of this
document to conform to the guidelines its proposes were found:
                  <ul>
<li>No Table of Contents was provided with the 2002-03-13 document. A table of contents has been generated and is
provided in this version of the document. </li>
<li>Definitions in clause 3 as provided in the 2002-03-13 document are in second level clauses. The Supplemental
Directives require these to be at the third level, e.g., 3.n.x </li>
<li>The Guidelines call for the document to validate to HTML 3.2 using the W3C validator. It does not.</li>
<li>The Guidelines call for a special header at the start of each webpage; there is not one in the 2002-03-13 document.
Included on this document.</li>
<li>The Guidelines call for document to be divided into multiple files (see Table <a href="#TableRef10.b">10.b</a>) The
2002-03-13 document is in a single file and does not include the required footer (see Clause <a
href="#ClauseRef6.5.3">6.5.3</a>)</li>
<li>All figures are to have associated <code>alt</code> attributes for accessibility. Not all figures in the 2002-03-13
document have them. Specifically, the only figure example in the document, the one showing the placement of figures in
clause <a href="#ClauseRef7.3.1">7.3.1</a>, does not have the required <code>alt</code> attribute. One was added in
this document.</li>
<li>The use of italics in normative references in the 2002-03-13 document for standard/document names is not consistent
with clause <a href="#ClauseRef8.3">8.3</a>.</li>
<li>Few intradocument hyperlinks (cross-references) are provided. Navigation/hyperlinks to refered to (sub)clauses,
abbreviations, defined term, ... should be provided.</li>
<li>No index is provided in this document -- specific requirements regarding the inclusion of an index or the specification of
when the index can be ommitted must be called out in clause <a href="#ClauseRef8.4">8.4</a>.</li>
<li>Cross references to defined terms, clauses, abbreviations, etc. were not exhaustively coded in the 2002-03-13
document. A text editor that would "Find and Replace" the ClauseIdentifier (e.g., 2.3) with &lt;a
href="#ClauseRef2.3'&gt;2.3lt;/a&gt; should be considered and applied.</li>
<li>Em dashes -- It may be the tool I used (XML Spy) but I had a lot of trouble incorporating the em dashes ,&amp;#8212,
and having them display properly. More investigation of this is needed. I noted that the HTML 3.2 recommendation does
not list the emdash as a printable character.</li>
<li>Some content, generally limited to long lines of code (for example, the first line of the footer tags in clause <a
href="#ClauseRef6.5.3">6.5.3</a> and example note coding of clause <a href="#ClauseRef7.5">7.5</a>) did not print out
correctly as required in clause <a href="#ClauseRef6.1">6.1</a>. These were corrected in this version and the original
should be printed to see the problems - one may wish to observe how the tagging of the entire content of examples, etc. as
done in this documents will clearly show any print problems as the right hand side of the cell will be missing/not printed when
the code lines are too long. If printing on the narrower 8.5 x 11 page size is achieved, the A4 printing requirement will also
be met and the guideline recommendation would accomodate both paper sizes.</li>
</ul>
</li>
</ul>
<h5>       Consistency Concern <a name="ClauseRefConsistency Concern"></a>from Nazemetz [<a
href="#0">Top</a>]</h5>
<p>The authoring of large documents in .html when one is trying to strictly conform to a large set of formatting rules is very
difficult, if not impossible to achieve without some computer assistance. While the use of XML and XSL for ISO documents
is promising and progressing (although not fully mature), an informative annex on how to use XML Schemas and
Stylesheets (along with the .xml and .xsl files) could/should be included so that those who wish to do so may use/test the
XML tools to produce consistently formatted .html more easily.</p>
<h5>         Semantics Capture in HTML <a name="ClauseRefSemantics Capture in HTML"></a>from Nazemetz [<a
href="#0">Top</a>]</h5>
<ul>
<li><ul>
<li>If .xml for ISO documents is the desired longer-term goal, how should (later) upward compatibility requirements for the
.html documents being generated in the interim be assured?
                            <p>One means of capturing/preserving the semantic meaning of the .html elements could be the
use of <code>style</code> attribute of <code>&lt;p&gt;</code> elements. This is not required if no transformations will
ever be applied to the .html documents, but this cannot be guarateed. An example of the possible use of these style tags
as descrbed below:</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td>For example, one could code the editor's information as
                                <pre><code>
&lt;p style='editor_name'&gt;Gerry Radack&lt;/p&gt;
&lt;p style='editor_email'&gt;gradack@address.com&lt;p&gt;</code></pre><br><p>Although it would require later parsing, a
second level clause identifier and title could be coded:</p>
<pre><code>
&lt;h2 style='lvl_2_clause_info'&gt;4.1 Second level subclause
   of document&lt;h2&gt;</code></pre><br><p>The <code>&lt;h2&gt;</code> tag alone may not be sufficient for automatic
processing as other semantic content could be tagged as &lt;h2&gt; such as: </p>
<pre><code>
&lt;h2&gt;A.2 Second level subannex of document&lt;h2&gt;</code></pre><br><p>A set of .xsl style sheets could be written
to transform the .html file to .xml or to proprietary word processors if this style data were available.</p>
<p>As an illustration of the implementation of this concept, the prototype xsl could be modified from:</p>
<pre><code>&lt;tr&gt;
   &lt;xsl:for-each select="Contributor"&gt;
   &lt;td align="center" colspan="1" valign="middle"&gt;
   &lt;h3&gt;&lt;xsl:value-of select="Role"/&gt;&lt;/h3&gt;
    &lt;small&gt;&lt;xsl:value-of select="Name"/&gt; &lt;br/&gt;
   &lt;xsl:apply-templates select="Address"/&gt;&lt;br/&gt;
   &lt;xsl:value-of select="Telephone"/&gt;&lt;br/&gt;
   &lt;xsl:value-of select="Telefacsimile"/&gt;&lt;br/&gt;
   &lt;xsl:apply-templates select="EmailAddress"/&gt;&lt;br/&gt;
   &lt;br/&gt;&lt;/small&gt;
   &lt;/td&gt;
   &lt;/xsl:for-each&gt;
&lt;/tr&gt;
                            </code></pre><br><p>to the following xsl that would attach the Role as a <code>style</code>
attibute in the <code>small</code> tag</p>
<pre><code>&lt;tr&gt;
   &lt;xsl:for-each select="Contributor"&gt;
   &lt;td align="center" colspan="1" valign="middle"&gt;
   &lt;h3&gt;&lt;xsl:value-of select="Role"/&gt;&lt;/h3&gt;
   &lt;small style='{Role}'&gt;&lt;xsl:value-of select="Name"/&gt; &lt;br/&gt;
   &lt;xsl:apply-templates select="Address"/&gt;&lt;br/&gt;
   &lt;xsl:value-of select="Telephone"/&gt;&lt;br/&gt;
   &lt;xsl:value-of select="Telefacsimile"/&gt;&lt;br/&gt;
   &lt;xsl:apply-templates select="EmailAddress"/&gt;&lt;br/&gt;
   &lt;br/&gt;&lt;/small&gt;
   &lt;/td&gt;
   &lt;/xsl:for-each&gt;
&lt;/tr&gt;
                            </code></pre><br><p>and this modified xsl would produce the following .html:</p>
<pre><code>&lt;tr&gt;
&lt;td align="center" colspan="1" valign="middle"&gt;
&lt;h3&gt;Project Leader&lt;/h3&gt;&lt;small style="Project Leader"&gt;
   Gerry Radack&lt;br&gt; CTC Corporation &lt;br&gt;
   Street&lt;br&gt;City, State, nnnnn-nnnn&lt;br&gt;USA&lt;br&gt;
     &lt;br&gt;+01 aaa/lll-nnnn&lt;br&gt;+01 aaa/lll-nnnn&lt;br&gt;&lt;a href=
     "mailto:graddack@ctc.com"&gt;graddack@ctc.com&lt;/a&gt;
     &lt;br&gt;&lt;br&gt;&lt;/small&gt;&lt;/td&gt;
&lt;td align="center" colspan="1" valign="middle"&gt;
&lt;h3&gt;Editor&lt;/h3&gt;&lt;small style="Editor"&gt;Gerry Radack
   &lt;br&gt;CTC Corporation&lt;br&gt;
   Street&lt;br&gt;City, State, nnnnn-nnnn&lt;br&gt;USA&lt;br&gt;
   &lt;br&gt;+01 aaa/lll-nnnn&lt;br&gt;+01 aaa/lll-nnnn&lt;br&gt;
   &lt;a href="mailto:graddack@ctc.com"&gt;
   graddack@ctc.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;/small&gt;&lt;/td&gt;
&lt;/tr&gt;</code></pre><br><p>The style attribute could be used on a number of block level tags (headings, paragraphs, ...
.</p>
</td>
</tr>
</table><br></li>
</ul>
</li>
</ul>
<h5>       Metadata and Use of Background Color <a name="ClauseRefMetadata and Use of Background Color"></a>from
Nazemetz [<a href="#0">Top</a>]</h5>
<ul>
<li><ul>
<li>Metadata, perhaps the Dublin core should be part of the required.html -- Example Dublin core data included with this
file.</li>
<li>Use of table/background color for examples and notes is a good concept -- however, the background color should be
behind the entire example or note (that is, clearly differentiate all informative text from normative using the background
color). The 2002-03-13 document does not include the "EXAMPLE first line of text" within the colored background. <table
align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative text of
note from surrounding text.">
<tr>
<td>Note          The bgcolor atribute is not allowed in HTML 3.2 based on the W3C validator.</td>
</tr>
</table><br></li>
</ul>
</li>
</ul>
<h5>       Guidelines as Example <a name="ClauseRefGuidelines as Example"></a>from Nazemetz [<a
href="#0">Top</a>]</h5>
<ul>
<li>Many editors and authors will look to this document and its .html encoding for guidance and for samples of code that
they can copy/paste/edit. The .html coding of this document should be fully documented/commented so that those who will
look to the code to learn are better served. As many examples of .html coding as possible in the guidelines document
should be from/of the Guidelines.html document encoding. In many cases, instances of cross references are not hyperlinks
and element names are not presented/tagged as <code>&lt;code&gt;</code>.</li>
<li>The use of multiple files and the file naming concepts seems likely to cause tremendous
creation/editing/maintenence/new edition problem. Using the (serially, consecutively numbered) figure/table numbers as
part of the file names will require all succeding files and file references in a document to be changed whenever a new figure
or table is added or one is deleted. Whenever files are renamed, e.g., when a figure is added and figure4.gif becomes
figure5.gif, any/all previous versions of the document/standard will have to be maintained in a separate directory in order to
avoid loss of previous configurations (overwriting the 'old' figure 4 with the 'new' figure) - if this is done, any/all file references
(at least all non-relative ones) in the documents that may provide a link to the changing figure in the document will need to
be reviewed/changed as will any/all references to the figure in other ISO documents that reference it normatively. Consider
this - when a standard references ISO xxxx edition 1 and a second edition comes out -- if file names and location are the
same, the external references to the document will be in error (referencing edition 2 now rather than 1) and these external
references are not and cannot be known to those changing the document editions. These concerns also apply when the
clause numbers are part of the file names. One solution is to reduce the number of files by keeping all clauses and tables
in a single file and the figures as separate files -- I suggest that the figure file names could be (something like)
ISOTC184-SC4nXXX_figureC_SC_..._sequence.ext where C = Clause, SC= Subclause, and a sequence lettering within
subclause is used and the n-number will assure that changes are not put in files of the same name. Thus, during editing,
the second figure in clause 5.6.1 would be ISOTC184-SC4nXXX_figure5_6_1_b.ext and when a figure is added or deleted
during editing only the file names for figures that follow the change in the section need be updated (rather than all
succeeding figure files for the entire document). When changes to a standing/balloted document occur, a new n-number
will be applied (even if it stays in the same directory). We have to be cognizant that the authors and editors who will
generate ISO documents directly in .html or via .xml rather than WORD or WordPerfect will have to be facing these
numbering and referencing problems during initial production and in response to ballot comments. While the single file
concept arguably increases download times, won't the business model for ISO Central Secretariat be download once or
provide on CD?</li>
<li>The three-level Table of contents is long. The Guidelines review may wish to consider adopting the W3C practice of
putting a short ToC at top of the document and links to a more detailed ToC at the bottom/end of the document.
Alternatively, the review may wish to not display the ToC entries using heading styles, preferring to use a series of
text/hyperlinks and <code>&lt;br/&gt;</code><table align="center" width="75%" border="2" bgcolor="#FFFACD"
summary="Single cell table used to separate informative text of example from surrounding text.">
<tr>
<td><p>The current xsl could be modified from:</p>
<pre><code>&lt;!-- --&gt;
&lt;!-- Content Template: Used to Automatically produces
  Table of Contents and presents the content of the
  XML file in HTML.--&gt;
&lt;!-- --&gt;

&lt;xsl:template match="Content"&gt;
&lt;h2&gt;&lt;a name="0"&gt;Table of Contents&lt;/a&gt;&lt;/h2&gt;&lt;br/&gt;

&lt;h3&gt;&lt;a href="#Foreword"&gt;Foreword&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;&lt;a href="#Introduction"&gt;Introduction&lt;/a&gt;&lt;/h3&gt;

&lt;xsl:for-each select="Clause"&gt;
&lt;h3&gt;&lt;xsl:value-of select="ClauseIdentifier"/&gt;&amp;#xA0;
  &amp;#xA0;&lt;a href= "#ClauseRef{ClauseIdentifier}"&gt;
  &lt;xsl:value-of select="ClauseTitle"/&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;xsl:for-each select="descendant::Sub1Clause"&gt;
  &lt;h4&gt;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;
  &lt;xsl:value-of select="Sub1ClauseIdentifier"/&gt;
  &amp;#xA0;&amp;#xA0;
  &lt;a href="#ClauseRef{Sub1ClauseIdentifier}"&gt;
  &lt;xsl:value-of select="Sub1ClauseTitle"/&gt;&lt;/a&gt;&lt;/h4&gt;
     &lt;xsl:for-each select="descendant::Sub2Clause"&gt;
       &lt;h5&gt;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;
       &amp;#xA0;&amp;#xA0;&lt;xsl:value-of select=
       "Sub2ClauseIdentifier"/&gt;&amp;#xA0;&amp;#xA0;
       &lt;a href= "#ClauseRef{Sub2ClauseIdentifier}"&gt;
       &lt;xsl:value-of select="Sub2ClauseTitle"/&gt;&lt;/a&gt;&lt;/h5&gt;
     &lt;/xsl:for-each&gt;
&lt;/xsl:for-each&gt;
&lt;/xsl:for-each&gt;

&lt;xsl:for-each select="Annex"&gt;
...</code></pre><br><p>and be changed to</p>
<pre><code>&lt;!-- --&gt;
&lt;!-- Content Template: Used to Automatically produces
   Table of Contents and presents the content of the
   XML file in HTML.--&gt;
&lt;!-- --&gt;

&lt;xsl:template match="Content"&gt;
&lt;h2&gt;&lt;a name="0"&gt;Table of Contents&lt;/a&gt;&lt;/h2&gt;&lt;br/&gt;

&lt;a href="#Foreword"&gt;Foreword&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;
&lt;a href="#Introduction"&gt;Introduction&lt;/a&gt;&lt;br/&gt;

&lt;xsl:for-each select="Clause"&gt;
&lt;xsl:value-of select="ClauseIdentifier"/&gt;&amp;#xA0;&amp;#xA0;
&lt;a href="#ClauseRef{ClauseIdentifier}"&gt;
  &lt;xsl:value-of select="ClauseTitle"/&gt;&lt;/a&gt;&lt;br/&gt;
&lt;xsl:for-each select="descendant::Sub1Clause"&gt;
  &amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;
  &lt;xsl:value-of select="Sub1ClauseIdentifier"/&gt;
  &amp;#xA0;&amp;#xA0;&lt;a href=
  "#ClauseRef{Sub1ClauseIdentifier}"&gt;
  &lt;xsl:value-of select="Sub1ClauseTitle"/&gt;&lt;/a&gt;&lt;br/&gt;
     &lt;xsl:for-each select="descendant::Sub2Clause"&gt;
       &amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;&amp;#xA0;
       &amp;#xA0;&amp;#xA0;&lt;xsl:value-of select=
       "Sub2ClauseIdentifier"/&gt;
       &amp;#xA0;&amp;#xA0;&lt;a href=
       "#ClauseRef{Sub2ClauseIdentifier}"&gt;
       &lt;xsl:value-of select="Sub2ClauseTitle"/&gt;
       &lt;/a&gt;&lt;br/&gt;
     &lt;/xsl:for-each&gt;
  &lt;/xsl:for-each&gt;
&lt;/xsl:for-each&gt;

&lt;xsl:for-each select="Annex"&gt;
...</code></pre><br><p>which would produce a Table of contents that would be more compact and would look
(something) like the following (the ClauseTitles would be hyperlinks and displayed in blue and underlined):</p>
<p><strong>Table of Contents</strong></p>
<pre><code>
Foreword

Introduction

1 Scope

2 Normative References

3 Term, Definitions, and Abbreviations
   3.1 Hypertext Markup Language (HTML)
   3.2 Other terms and definitions
   3.3 Abbreviations

4 Supported Browsers

5 Overall document preparation
     5.1 Acceptable digital formats
     5.2 Acceptable tags
     5.3 Hyperlinks</code></pre><br></td>
</tr>
</table><br></li>
</ul>
<h5>      Guidelines Document Structure <a name="ClauseRefGuidelines Document Structure"></a>from Nazemetz [<a
href="#0">Top</a>]</h5>
<ul>
<li></li>
<li>The useability and readability of the document would be improved by organizing it so that the clauses and subclauses
reflect the major structural elements of ISO documents in the order they normally appear in ISO doucuments. I would
suggest the following structure for the standing document:
                      <ul>
<li>Cover page</li>
<li>Table of contents</li>
<li>Foreword</li>
<li>Introduction</li>
<li>Scope</li>
<li>Normative references</li>
<li>Definitions, terms, and abbreviations</li>
<li>Purpose (while standards should not justify themselves, standing documents probably should)
                      <ul>
<li>Presentation
                                      <p>Discuss the need for guidelines to assure that the content can be viewable in
browsers and as printed documents in light of the nearly infinite ways they could be produced in .html and the desire for
consistency with non-browser presentations and previously published ISO documents</p>
</li>
<li>Provide (interim) .html solution as well as guidance (non-normative) on the use of .xml and .xsl for production of
documents/migration to .xml. -- see suggestion for additional annex below).</li>
<li>Accessibility
                                  <p>Discuss the need to incorporate W3C WAI Accessibillity requirements into the
documents.</p>
</li>
</ul>
</li>
<li>Presentation requirements
                              <ul>
<li>Applicable Supplemental Directive clauses (with crossreferences)</li>
<li>Accessibility requirements</li>
<li>Browser version compatibility requirements</li>
<li>Print requirements</li>
</ul>
</li>
<li>ISO document markup in .html <table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell
table used to contain informative text of note from surrounding text.">
<tr>
<td>Element names from the prototype schema used; I hope this is not confusing to other reviewers. An html document of
the schema documentation is available from <a
href="www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/GuidelinesDocuments/ISODraftDocumentDocumentation.html">m
y website at OSU.</a>.-- JWN</td>
</tr>
</table><br><ul>
<li>Overview of .html document structure and components
                                   <ul>
<li>Discuss the use of frames, navigation through the document, file naming, and directory structure to support the ISO
document concept.</li>
<li>Define and briefly discuss the component classes (metadata, header, block elements, in-line elements, ...).</li>
</ul>
</li>
<li>Major document components
                                       <ul>
<li>Metadata (Required?) - (use Dublin Core?)
                                               <ul>
<li>Required elements (title, creator (name and e-mail), subject, description, publisher (name and e-mail), contributor, date,
type, format, identifier, source, language, relation)</li>
<li>Optional elements(alternatetitle)</li>
</ul>
</li>
<li>Header (Required)
                                               <ul>
<li>Required elements (status (e.g., draft, CD, DIS, ...), copyright information)</li>
<li>Optional elements(??)</li>
</ul>
</li>
<li>Cover page (Required) - (Need better name for this)
                                               <ul>
<li>Required elements (DocumentNumber, DocumentDate, Supercedes, Document/StandardTitle, CopyrightNotice,
Abstract, Keywords, CommentstoReader, Contibutors (Role (ProjectLeader, Editor), Name, Address
(Company,StreetOrBox, CityStateCode, Country), Telephone, Telefacsimile, EmailAddress)</li>
<li>Optional elements (StandardNumber-optional, may not be a standard document) </li>
</ul>
</li>
<li>Table of contents (Required)
                                               <ul>
<li>Required elements (Listings of Clauses, SubnClauses (where 'n' is the level of the subclause), Annexes, SubnAnnexes,
Bibliography, Index, with hyperlinks to them) </li>
<li>Optional elements (Index)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Unnumbered Clauses (Foreword, Introduction required)
                                               <ul>
<li>Required elements (Foreword, Introduction; each must have ClauseIdentifier, ClauseTitle, and one additional element
(Paragraph or subelement))</li>
<li>Optional elements (text, Paragraphs, Notes, Examples, CodeInserts, Figures, Tables, OrderedLists, UnorderedLists,
LongQuotes, CenteredParagraphs)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Numbered Clauses (at least 3 Required)
                                               <ul>
<li>Required elements (1-Scope, 2-Normative References, 3-Terms, Definitions,...; all must have ClauseIdentifier,
ClauseTitle, and one additional element (Paragraph or subelement))</li>
<li>Optional elements (4th Clause onward)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Bibliography (Required)
                                             <ul>
<li>Required elements (at least one entry, even if it says no Bibliography Entries).</li>
<li>Optional elements (text, Paragraphs, Notes, Examples, CodeInserts, Figures, Tables, OrderedLists, UnorderedLists,
LongQuotes, CenteredParagraphs)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Annexes (Optional)
                                             <ul>
<li>Required elements (AnnexIdentifier, AnnexTitle, at least one subelement (e.g., Paragraph or Sub1Annex)</li>
<li>Optional elements (Sub2Annexes, text, Paragraphs, Notes, Examples, CodeInserts, Figures, Tables, OrderedLists,
UnorderedLists, LongQuotes, CenteredParagraphs)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Index (Optional)
                                             <ul>
<li>Required elements (???)</li>
<li>Optional elements (entries, hyperlinks)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
</ul>
</li>
<li>Block Elements
                                    <ul>
<li>Abbreviations (Optional, must be at third level of clause)
                                             <ul>
<li>Required elements (Abbr, AbbrMeaning, hyperlink anchors)</li>
<li>Optional elements(text, Notes, Paragraphs)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>CodeInserts (Optional) (EXPRESS, Other multiline Listings of Computer Code)
                                             <ul>
<li>Required elements (code, all .html reserved characters must be encoded)</li>
<li>Optional elements (none??)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Comments (Optional in ISODraftDocuments, Prohibited in ISODocuments)
                                             <ul>
<li>Required elements (Source)</li>
<li>Optional elements (most major document component, all other block and inline elements)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Definitions (Optional)
                                             <ul>
<li>Required elements (DefinitionIdentifier, Term, DefiningText, text, Notes)</li>
<li>Optional elements</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Examples (Optional)
                                             <ul>
<li>Required elements ('EXAMPLE' as first word; number if more than one in a (sub)clause or (sub)annex). </li>
<li>Optional elements (text, Paragraphs, CodeInserts, Notes, OrderedLists, UnorderedLists, Tables, in-line elements,
hyperlinked elements)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Figures
                                                <ul>
<li>Required elements (FigureIdentifier, FigureTitle, FigureDescription (for visually impaired), FileLocation)</li>
<li>Optional elements (BiblioRef)</li>
<li>Rules for creation, numbering, titling, and storing (directory and file names) figures</li>
<li>Formatting and Encoding in HTML</li>
<li>Special Rules (Figures in Examples, TableCells, When can be larger than will print without cutoff...)</li>
</ul>
</li>
<li>Lists
                                                <ul>
<li>Required elements (at least one ListItem)</li>
<li>Optional elements (OrderedLists, UnorderedLists, Notes, Examples)</li>
<li>Rules for embedding lists in lists</li>
<li>Formatting and Encoding in HTML
                                                <table align="center" width="75%" border="2" bgcolor="#FFFACD"
summary="Single cell table used to separate informative text of example from surrounding text.">
<tr>
<td>WARNING!! -- The rules and examples stated in the original 2002-03-13 document (see clauses <a
href="#ClauseRef7.2">7.2</a>) will lead to problems when trying to validate to HTML 4.01 (and maybe 3.2, I haven't
checked). To be 4.01 valid, the embedded list must not have two tags of the same type open at the same time.
                                                <pre><code>&lt;ol&gt;
      &lt;li&gt;item one in list&lt;/li&gt;
      &lt;li&gt;item two containing embedded list&lt;/li&gt;
            &lt;ol&gt;
                 &lt;li&gt;item a in embedded list&lt;/li&gt;
                 &lt;li&gt;item b in embedded list&lt;/li&gt;
            &lt;/ol&gt;
      &lt;/ol&gt;
</code></pre><br>


Two &lt;ol&gt; tags would be open at the same time/level if the second &lt;ol&gt; tag is not embedded in the item two list
item. Coding in 2002-03-13 .html appears to be correct, but, example code is not consistent with this requirement. Proper
HTML 4.01 tagging is as shown below:
                                                    <pre><code>&lt;ol&gt;
      &lt;li&gt;item one in list&lt;/li&gt;
      &lt;li&gt;item two containing embedded list
             &lt;ol&gt;
                  &lt;li&gt;item a in embedded list&lt;/li&gt;
                  &lt;li&gt;item b in embedded list&lt;/li&gt;
              &lt;/ol&gt;
      &lt;/li&gt; &lt;!-- this is correct position for
        closing item two --&gt;
&lt;/ol&gt;</code></pre><br><p>All lists are so coded by the prototype xsl. This will be a real problem if not controlled early
so that upward compatibility to HTML 4.01 can be less painful.</p>
</td>
</tr>
</table><br></li>
</ul>
</li>
<li>Notes
                                                    <ul>
<li>Required elements ('NOTE' as first word; number if more than one in a (sub)clause or (sub)annex).</li>
<li>Optional elements (text, Paragraphs, CodeInsers, Notes, OrderedLists, UnorderedLists, Tables, in-line elements,
hyperlinked elements)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Quotations
                                                    <ul>
<li>Required elements (text, BiblioRef)</li>
<li>Optional elements (block elements, in-line elements, hyperlinked elements)</li>
<li>(blockquote) and short (in-line) forms, required BiblioRefs</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Tables
                                               <ul>
<li>Required elements (TableIdentifier, TableTitle, TableDescription (for visually impaired), TableRow, TableCell</li>
<li>Optional elements (ColumnHeading)</li>
<li>Numbering scheme, required and optional attributes</li>
<li>Special Rules (Mapping Tables, Large tables that will be cutoff by printing, ...)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>In-line Elements
                                       <ul>
<li>Bold</li>
<li>Code (Monospaced text)</li>
<li>Emphasized text/expressions using single or double quote marks</li>
<li>Italic</li>
<li>Underline</li>
<li>ShortQuote (required BibloRef)</li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
</ul>
</li>
<li>Hyperlinked elements (Optional)
                                       <ul>
<li>External Links (with and without aliasing text)</li>
<li>E-mail addresses (with and without aliasing text)</li>
<li>References to abbreviations</li>
<li>References to annexes, subannexes</li>
<li>References to biblographic entries</li>
<li>References to clauses, subclauses</li>
<li>References to defined terms</li>
<li>References to figures</li>
<li>References to terms in the index</li>
<li>References to tables</li>
<li>Formatting and Encoding in HTML
                                           <table align="center" width="75%" border="2" bgcolor="#FFF8DC"
summary="Single cell table used to contain informative text of note from surrounding text.">
<tr>
<td>NOTE - I am assuming that the creation of the hyperlink anchors to which these refer are covered in the subclauses on
the required elements of the abbreviations, ... .</td>
</tr>
</table><br></li>
</ul>
</li>
<li>Navigation elements (Required?)
                                       <ul>
<li>Hyperlinks from/toTable of Contents to/from Clauses, SubClauses, ...</li>
<li>Hyperlinks to ExternalLinks (with and without Alias), AbbrRefs, DefinedTerms, BiblioRefs, ...</li>
<li>Navigation to other files/pieces of document, figures, ...
                                           <table align="center" width="75%" border="2" bgcolor="#FFF8DC"
summary="Single cell table used to contain informative text of note from surrounding text.">
<tr>
<td>NOTE - I do not support multiple files (as in one file per clause) because it is difficult to maintain and makes the use of
within document hyperlinks/bookmarks (#clause) between clauses impossible -- since clauses are in different files, longer
links (../Clause5#ClauseRef5.2 and automatic renumbering and maintenance of numerical sequences and correct
references will be very difficult during document creation and editing</td>
</tr>
</table><br></li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Documentation elements (Required?)
                                         <ul>
<li>Methods/Tool(s) Used to Generate</li>
<li>Annotations for Reader Understanding
                                             <table align="center" width="75%" border="2" bgcolor="#FFF8DC"
summary="Single cell table used to contain informative text of note from surrounding text.">
<tr>
<td>NOTE - I am assuming that the some documentation in the .html file will be required (&lt;!-- xxxxx --&gt;)</td>
</tr>
</table><br></li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Editing elements (Optional, Allowed in Drafts, Not Allowed in 'Final' Documents)
                                         <ul>
<li>Comments</li>
<li>Insert</li>
<li>Delete
                                             <table align="center" width="100%" border="2" bgcolor="#FFE4E1"
summary="Single cell table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The folowing NOTE contains inserted and deleted text examples (which are shown
as text with strikeouts (hypen on top of character), it they are not apparent, your browser cannot display these HTML 4.01
elements.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain
informative text of note from surrounding text.">
<tr>
<td>NOTE - I am assuming that one would wish to provide for editing and (multiple) collaboration features. For example,
comments appearing in this document can be aggregated into a single document and all comments from the various
reviewers could be placed within a single document at the places the reviewers inserted the comments (obviously,
comments inserted following the same (original) document element would appear in some arbitrary order). Also, an ability
to denote <ins><strong> --&gt; inserted text <em> -- suggested by: identity of reviewer here </em> &lt;-- </strong></ins>as
well as <del>deleted text <em> -- suggested by: identify of reviewer here </em></del> might be very useful in reviewing
edited documents (so one can see the changes without having to reread and cross reference to a (ballot) comment form and
know the identity of the source of the change.</td>
</tr>
</table><br></li>
<li>Formatting and Encoding in HTML</li>
</ul>
</li>
<li>Printing Considerations/Element Limitations
                                                 <ul>
<li>Limitations on text elements (Define maximum length of text strings for links, e-mail, code before printing cutoff occurs --
This is different at different levels of indention (4th level is limiting, suggest using this as absolute limit).</li>
<li>Table limitations</li>
<li>Figure limitations</li>
</ul>
</li>
<li>Browser Presentation Considerations/Element
                                                 <ul>
<li>Accessibility Element Requirements (alt attributes, ...).</li>
<li>HTML 3.2, 4.01,.. Elements</li>
<li>Figure limitations</li>
<li>Table limitations</li>
</ul>
</li>
<li>Configuration management elements
                                         <ul>
<li>Insertions (to original and subsequent additions)</li>
<li>Deletions (to original and subsequent editions)
                                             <table align="center" width="75%" border="2" bgcolor="#FFF8DC"
summary="Single cell table used to contain informative text of note from surrounding text.">
<tr>
<td>NOTE - I am assuming that one might wish to provide an ability to keep, in a single file all editions, TCs, ... for a
standard/document. -- This could be done by using, for example, the<code> Source</code> element or the
<code>style</code> attribute to contain the version number and use a style sheet to control display or production of the
versioned documents.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>Insertions and Deletion markup, including the the 'Source' tag could be used to store version data so that one
document/file could contain all 'official' versions and the Source tag could be used to control what is displayed (e.g., if want
to see the original document ignore any changes originated by Source = 'version2', 'version3', Technical corregenda 2, ...).
Alternatively, the TimeDate could be used for official versioning/Source in the .html.</p>
<p>This dicussion is XML-oriented. I inculded an example clause in the originally distributed document to illustrate -- see
<a href="#ClauseRefAdd-In">Add-In</a> Example I would keep the 'Source' element (which I am using a global element to
hold identity in <code>Comment</code> and <code>Insertion/Deletion</code> elements) as a string type rather than a
timedate so that multiple collaborator <code>Comment</code>s could still be kept in a single file pending their resolution --
&lt;Source&gt;John Nazemetz&lt;/Source&gt; would differentiate my comments from those of say, &lt;Source&gt; Someone
Else&lt;/Source&gt; or &lt;Source&gt;Technical Corregenda 1&lt;/Source&gt;. Although I haven't really thought much about
how to handle non-text changes (e.g., updates to figures that would reference different files/urls in different versions) -- first
thought is to use the following in second and subsequent official (XML) document versions (I am using my schema element
names for illustration) --</p>
<pre><code>&lt;Deletion&gt;
&lt;Source&gt;Version2&lt;/Source&gt;
&lt;Figure&gt;
  &lt;FigureIdentifier&gt;1&lt;/FigureIdentifier&gt;
  &lt;FigureTitle&gt;Relationship between different markup
  declaration sets included and enabled by this part of
  ISO 10303&lt;/FigureTitle&gt;
  &lt;FigureDescription&gt;This is a sample gif file and shows
    the relationship between different markup declaration
    sets included and enabled by this part of ISO 10303
  This Description is used for the visually impaired.
  &lt;/FigureDescription&gt;
  &lt;FileNameLocation&gt;http://www.okstate.edu/ceat/ie/
  jnazeme/ISO_XML_HTML/
  Figure1.gif&lt;/FileNameLocation&gt;
&lt;/Figure&gt;
&lt;/Deletion&gt;

&lt;Insertion&gt;
&lt;Source&gt;Version2&lt;/Source&gt;
&lt;Figure&gt;
      &lt;FigureIdentifier&gt;1&lt;/FigureIdentifier&gt;
      &lt;FigureTitle&gt;Relationship between different markup
      declaration sets included and enabled by this part of
      ISO 10303&lt;/FigureTitle&gt;
      &lt;FigureDescription&gt;This is a sample gif file and shows
       the relationship between different markup declaration
       sets included and enabled by this part of ISO 10303.
      This Description is used for the visually impaired.
      &lt;/FigureDescription&gt;
  &lt;FileNameLocation&gt;http://www.okstate.edu/ceat/ie/
  jnazeme/ISO_XML_HTML/
  Figure1ver2.gif&lt;/FileNameLocation&gt;
&lt;/Figure&gt;
&lt;/Insertion&gt;</code></pre><br><p>A text example would be:</p>
<pre><code>&lt;Deletion&gt;
&lt;Source&gt;TC1&lt;/Source&gt;
&lt;Paragraph&gt;
  This is the original text in version 1 of the document
  deleted by the TC.
&lt;/Paragraph&gt;
&lt;/Deletion&gt;

&lt;Insertion&gt;
&lt;Source&gt;TC1&lt;/Source&gt;
&lt;Paragraph&gt;
  This is the modified text that would inserted/replace the
  original text in subsequent presentation(s) (.html or
   otherwise) of the document.
&lt;/Paragraph&gt;
&lt;/Insertion&gt;</code></pre><br><p>The .html could use the <code>style</code> attribute to encode the changes, such
as:</p>
<pre><code>&lt;p&gt;Last original text of document before change by approved
ballot&lt;/p&gt;
&lt;p style="InsertionTC1"&gt;Text inserted into document by a
Technical Corrigenda 1.&lt;/p&gt;
&lt;p style="DeletionTC1"&gt;Original text of document deleted
 by Technical Corrigenda 1.&lt;/p&gt;
&lt;p&gt;Next element of original text of document&lt;/p&gt;</code></pre><br><p>Obviously, the required
<code>Source</code> child element would need to be unbounded as future versions may also delete or restore the original
and (some) of the lower version insertions. I have to think about the elements that tags the <code>Deletion</code> and
<code>Insertion</code> tags can/should be allowed to enclose in the XML Schema. As you can see from the above, only
the <code>&lt;FileNameLocation&gt;</code> tag is changed and the other elements are not -- until better tools evolve, I
tend to favor forcing the <code>Insertion/Deletion</code> tags around logical chunks e.g., Clauses, SubnClauses,
Paragraphs, Figures, Notes, and Examples so someone editing in a text editor-like tool can read and understand the
changes in the .xml document more easily and avoid mistakes. The file naming conventions should require the version in
all referenced filenames, e.g., &lt;IMG SCR= 'http://www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/
Figure1ver2.gif'&gt;".</p>
</td>
</tr>
</table><br></li>
</ul>
</li>
</ul>
</li>
<li>Naming conventions
                                   <ul>
<li>Multi-file document sets</li>
<li>Multi version, multi-file document sets</li>
<li>Formatting and Encoding in HTML (relative/absolute links to files)</li>
</ul>
</li>
</ul>
</li>
<li>Conformance
                  <ul>
<li>Conformance to file naming, file/directory structure, review/balloting processes of ISO TC 184/SC4 QC, ... </li>
<li>Required ISO document structure and content validation</li>
<li>HTML specification conformance validation</li>
<li>Conformance to ISO restricted html tag set and HTML documentation requirements</li>
<li>Conformance to WAI accessibility requirements</li>
<li>Conformance testing requirements against supported browser set</li>
<li>Conformance to printed document requirements</li>
</ul>
</li>
<li>Annex A - normative - ISO restricted tag set XSL validator</li>
<li>Annex B - informative - Tools for creation and editing of ISO documents in .html.</li>
<li>Annex C - informative - Generating and editing documents in .html for ISO publication</li>
<li>Annex D - informative - Using XML and XSL for the creation of .html documents.
                          <ul>
<li>D.1 Advantages of using XML and XSL for ISO document creations</li>
<li>D.2 XML Schemas for ISO documents</li>
<li>D.3 Creating instance documents conforming to the XML schema </li>
<li>D.4 An XSL for creating .html from the XML schema for ISO documents</li>
<li>D.5 Using the XML Schema and XSLs
                               <ul>
<li>D.4.1 Coversion of documents in proprietary word processing formats</li>
<li>D.4.2 Generating and editing documents using the XML schema and XSL for ISO documents</li>
<li>D.4.3 Conversion of ISO .html documents to .xml</li>
<li>D.4.4 Validation and other supporting stylesheets </li>
</ul>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>The original text of the draft was not edited as this would usurp the role of the
editor -- in only a few places was the original text modified for illustative purposes and, in all such cases, a comment was
added to annotate the change. I did modify the colors used in the original document as background colors for the tables. I
selected alternate colors based on my perception of contrast and streotyped interpretations (red = high alert, ...).Colors were
selected using a Netscape color website, <a
href="http://users.rcn.com/giant.interport//COLOR/ColorSpecifier.html">http://users.rcn.com/giant.interport//COLOR/ColorSp
ecifier.html</a>. The xml allows a very efficient change to the color scheme and the proper .html coding for the selected
display/presentation.</p>
</td>
</tr>
</table><br><h2><a name="0">Table of Contents</a></h2>
<h3><a href="#Foreword">Foreword</a></h3>
<h3><a href="#Introduction">Introduction</a></h3>
<h3>1 <a href="#ClauseRef1">Scope</a></h3>
<h3>2 <a href="#ClauseRef2">Normative References</a></h3>
<h3>3 <a href="#ClauseRef3">Term, Definitions, and Abbreviations</a></h3>
<h4>       3.1 <a href="#ClauseRef3.1">Hypertext Markup Language (HTML)</a></h4>
<h4>       3.2 <a href="#ClauseRef3.2">Other terms and definitions</a></h4>
<h4>       3.3 <a href="#ClauseRef3.3">Abbreviations</a></h4>
<h3>4 <a href="#ClauseRef4">Supported Browsers</a></h3>
<h3>5 <a href="#ClauseRef5">Overall document preparation</a></h3>
<h4>       5.1 <a href="#ClauseRef5.1">Acceptable digital formats</a></h4>
<h4>       5.2 <a href="#ClauseRef5.2">Acceptable tags</a></h4>
<h4>       5.3 <a href="#ClauseRef5.3">Hyperlinks</a></h4>
<h3>6 <a href="#ClauseRef6">Page size, fonts, and spacing</a></h3>
<h4>       6.1 <a href="#ClauseRef6.1">Page size</a></h4>
<h4>       6.2 <a href="#ClauseRef6.2">Fonts and font sizes</a></h4>
<h4>       6.3 <a href="#ClauseRef6.3">Vertical spacing</a></h4>
<h4>       6.4 <a href="#ClauseRef6.4">Page layout for parts of SC4 standards</a></h4>
<h4>       6.5 <a href="#ClauseRef6.5">Page headers and footers</a></h4>
<h5>           6.5.1 <a href="#ClauseRef6.5.1">General requirements for page headers and footers.</a></h5>
<h5>           6.5.2 <a href="#ClauseRef6.5.2">"Special" header on page 1</a></h5>
<h5>           6.5.3 <a href="#ClauseRef6.5.3">Page footers</a></h5>
<h3>7 <a href="#ClauseRef7">General format and layout instructions</a></h3>
<h4>       7.1 <a href="#ClauseRef7.1">Format and layout of clauses and subclauses</a></h4>
<h5>           7.1.1 <a href="#ClauseRef7.1.1">Clause and subclause headings</a></h5>
<h5>           7.1.2 <a href="#ClauseRef7.1.2">Paragraphs</a></h5>
<h5>           7.1.3 <a href="#ClauseRef7.1.3">Orphans and widows</a></h5>
<h5>           7.1.4 <a href="#ClauseRef7.1.4">Annex headings</a></h5>
<h5>           7.1.5 <a href="#ClauseRef7.1.5">An annex of examples</a></h5>
<h4>       7.2 <a href="#ClauseRef7.2">Format and layout of lists</a></h4>
<h4>       7.3 <a href="#ClauseRef7.3">Format and layout of figures</a></h4>
<h5>           7.3.1 <a href="#ClauseRef7.3.1">Placement of figures</a></h5>
<h5>           7.3.2 <a href="#ClauseRef7.3.2">Format for figures</a></h5>
<h5>           7.3.3 <a href="#ClauseRef7.3.3">Placement of figure captions</a></h5>
<h4>       7.4 <a href="#ClauseRef7.4">Format and layout of tables</a></h4>
<h5>           7.4.1 <a href="#ClauseRef7.4.1">Placement of tables</a></h5>
<h5>           7.4.2 <a href="#ClauseRef7.4.2">Format for tables</a></h5>
<h5>           7.4.3 <a href="#ClauseRef7.4.3">Placement of table numbers and titles</a></h5>
<h4>       7.5 <a href="#ClauseRef7.5">Layout and format of notes</a></h4>
<h4>       7.6 <a href="#ClauseRef7.6">Layout and format of examples</a></h4>
<h3>8 <a href="#ClauseRef8">Format and layout of specific elements</a></h3>
<h4>       8.1 <a href="#ClauseRef8.1">Format and layout of the table of contents</a></h4>
<h4>       8.2 <a href="#ClauseRef8.2">Format and layout of the title element</a></h4>
<h4>       8.3 <a href="#ClauseRef8.3">Layout and format of normative references</a></h4>
<h4>       8.4 <a href="#ClauseRef8.4">Layout and format of terms and definitions</a></h4>
<h4>       8.4 <a href="#ClauseRef8.4">Format for the index</a></h4>
<h3>9 <a href="#ClauseRef9">Main document page</a></h3>
<h3>10 <a href="#ClauseRef10">File naming and directory structure</a></h3>
<h3>11 <a href="#ClauseRef11">Validation and testing</a></h3>
<h3>Add-In <a href="#ClauseRefAdd-In">Example of Document Configuration Managment of Previously Approved
Changes</a></h3>
<h3>Annex A <a href="#AnnexRefA">Use of validtags.xsl stylesheet</a></h3>
<h3><a href="#Bibliography">Bibliography</a></h3><br><br><br><br><br><h3><a name="Foreword"></a>Foreword [<a
href="#0">Top</a>]</h3>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td>Text added so that a Foreword clause was in document.<em> -- suggested by: Nazemetz </em></td>
</tr>
</table><br><p>This standing document provides guidance to those working groups in TC184/SC4 who wish to publish the
standards that they are developing using HTML.</p><br><br><h3><a name="Introduction"></a>Introduction [<a
href="#0">Top</a>]</h3>
<p>The following conventions are used in this document.</p>
<p>A comment about the document is given in a box with a default background, as illustrated below.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Radack </em>Need to add HTML tools to QC N189.</td>
</tr>
</table><br><p>An example showing how a portion of a document would appear is given in a box with a pink background,
as illustrated below.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>I modified the colors of NOTEs and EXAMPLEs (shades of yellow) to improve
contrast and reinforce stereotyped expectations (red means high alert/caution). The original text was also modified so that
all non-normative text is in the box/colored background.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p align="center"><strong>Annex C</strong></p>
<p align="center"><strong>(normative)</strong></p>
<p align="center"><strong>Implementation method specific requirements</strong></p>
HTML code is given as preformatted text, as illustrated below.
<pre><code>
&lt;h2&gt;Annex C&lt;br/&gt;
(normative)&lt;br/&gt;
&lt;br/&gt;
Implementation method specific requirements&lt;/h2&gt;
                      </code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1"
summary="Single cell table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The "extra" spaces in the original document's tags, such as &lt;br /&gt; were
suppressed in this document.</td>
</tr>
</table><br></td>
</tr>
</table><br><br><br><h3>1 <a name="ClauseRef1"></a>Scope [<a href="#0">Top</a>]</h3>
<p>This standing document specifies requirements for the HTML markup of standards developed by ISO TC184/SC4.</p>
<p>This standing document replaces Clause 5 of the SC4 Supplementary Directives for documents published in HTML. It is
only applicable for documents published in HTML.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>If all ISO documents anchors were explicitly tagged, direct hyperlinking into the
content of a document, rather than to the top of the document could be easily achieved. For example, the link could be to
<code>www.xxx. ... \SupplementaryDirectives.html#ClauseRef5</code> and a strictly adhered to tagging and anchor
naming convention would allow document creation without having to view the target file (which, if in WORD or WORD
generated .html would have an anchor of the pattern _2234397). Data query and retrieval technology could be used to
construct documents through knowledge of the tagging and anchors -- consider an ISO public (open) website that would
display the Scope of any standard or standing document XML Spy (the tool I used; this is not a commercial endorsement)
has a ability to create a data base from the schema and this may be used to facilitate this latter process. </p>
</td>
</tr>
</table><br><h3>2 <a name="ClauseRef2"></a>Normative References [<a href="#0">Top</a>]</h3>
<p>The following documents contain provisions which, through reference in this text, constitute provisions of this standing
document. For dated references, subsequent amendments to, or revisions of, such publications do not apply. However,
editors of SC4 standards are encouraged to investigate the possibility of applying the most recent editions of the documents
indicated below. For undated references, the latest edition of the document referred to applies. Members of ISO and IEC
maintain registers of currently valid International Standards.</p>
<p><em>HTML 3.2 reference specification</em>, 1997-01-14, <a
href="http://www.w3.org/TR/REC-html32">http://www.w3.org/TR/REC-html32</a>.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>This document validates to HTML 4.01 Transitional using the W3C validator. It
fails 3.2 validation with respect to the following elements/tags/attibutes:
              <ul>
<li>3.2 does not allow the <code>lang</code> attribute in HTML DTD specification in line 2</li>
<li>3.2 does not allow the <code>scheme</code> attribute on the dc.date in line 33 -- e.g., <code>&lt;meta
name="DC.Date" SCHEME="ISO8601" content="2002-03-18"&gt;</code></li>
<li>3.2 identified an error in <code>bgcolor</code> (element not allowed) in table attributes (for comments, notes,
examples) in line 57, e.g., ... <code>table align="center" width="100%" border" width="100%" border="2"
bgcolor="#FFE4E1" summary="Single ...</code></li>
<li>3.2 identified an error in the <code>summary</code> (element not allowed) attribute, which is used to provide
descriptions for the visually impaired, in line 57, e.g., <code> table align="center" width="100%" border" width="100%"
border="2" bgcolor="#FFE4E1" summary="Single ..</code></li>
<li>3.2 identified an error in the <code>scope</code> attribute needed for proper reading of table headings to the visually
impaired in line 118, e.g., <code>&lt;th scope=col' colspan="1" align="center"&gt;File&lt;/th&gt;</code> (This may/could also
be an error on my part)</li>
<li>3.2 identified the use of <code>&lt;ins&gt;</code> and <code>&lt;del&gt;</code> tags in line 442, e.g., ...
<code>arbitrary order). Also, an ability to denote &lt;ins&gt;&lt;strong&gt; --&gt; insert ... here &lt;/em&gt; &lt;--
&lt;/strong&gt;&lt;/ins&gt; as well as &lt;del&gt;deleted text here &lt;em&gt; ..</code>.</li>
</ul>
<p>All the above were checked against the HTML 3.2 recommendation and are indeed not valid against the
recommendation, HOWEVER -- 2 of the 6 assist in meeting Web Accessibiity requirements, 2 provide useful meta data,
and the other two support (but are not essential) to the editing process. </p>
</td>
</tr>
</table><br><p><em>SC4 Supplementary directives - Rules for the structure and drafting of SC4 standards</em>, ISO
TC184/SC4/QC N200, 2001-06-21.</p>
<h3>3 <a name="ClauseRef3"></a>Term, Definitions, and Abbreviations [<a href="#0">Top</a>]</h3>
<h4> 3.1 <a name="ClauseRef3.1"></a>Hypertext Markup Language (HTML) [<a href="#0">Top</a>]</h4>
<h4> 3.2 <a name="ClauseRef3.2"></a>Other terms and definitions [<a href="#0">Top</a>]</h4>
<dl>
<dt><b><em>3.2.1<a name="Joint Photographic Experts Group"></a> Joint Photographic Experts Group</em></b>
         </dt>
<dd>ISO/IEC JTC1 SC29 Working Group 1, which is producing standards for continuous tone image coding</dd>
</dl>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE - Adapted from<a href=" http://www.jpeg.org/public/jpeghomepage.htm">
http://www.jpeg.org/public/jpeghomepage.htm</a></td>
</tr>
</table><br><dl>
<dt><b><em>3.2.2<a name="page"></a> page</em></b>
         <em> - - Alternate Form(s):
                       webpage<a name="AbbrRefwebpage"></a>;
                       </em></dt>
<dd>an HTML page</dd>
</dl>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Synonyms added -- this is used so that DefinedTerm hyperlink anchors can be
automatically generated for all forms of a word and its synonyms and so all instances of the terms can be hyperlinked back
to their definition (automatically using the .xsl). These anchors and links as well as the specification of synonyms (with
links) should be required as part of the navigation elements required in the .html.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain
informative text of note from surrounding text.">
<tr>
<td>NOTE - An HTML page may correspond to one or more printed pages.</td>
</tr>
</table><br><dl>
<dt><b><em>3.2.3<a name="portable network graphics"></a> portable network graphics</em></b>
         </dt>
<dd>an extensible file format for the lossless, portable, well-compressed storage of raster images.</dd>
</dl>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE 1 - <a href="#AbbrRefPNG">PNG</a>
      provides a patent-free replacement for GIF and can also replace many common uses of TIFF.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain
informative text of note from surrounding text.">
<tr>
<td>NOTE 2 - Adapted from <a href="http://www.w3.org/Graphics/PNG/">http://www.w3.org/Graphics/PNG/</a></td>
</tr>
</table><br><dl>
<dt><b><em>3.2.4<a name="printed page"></a> printed page</em></b>
         </dt>
<dd>the output printed by a browser on a single sheet of paper, when using the default browser settings and magnification
of 100%</dd>
</dl>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The term 100% magnification is more of a Netscape term, Explorer uses smallest,
smaller, medium (I assumed this setting was 100%), ... . The term for the setting at which (or below which) proper printing
occurs must be unambiguously defined. Spellling of magnification corrected from original document.</td>
</tr>
</table><br><dl>
<dt><b><em>3.2.5<a name="Supplementary Directives"></a> Supplementary Directives</em></b>
         </dt>
<dd>SC4 Supplementary directives - Rules for the structure and drafting of SC4 standards</dd>
</dl>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Small 'd' in directives.</td>
</tr>
</table><br><dl>
<dt><b><em>3.2.6<a name="uniform resource locator"></a> uniform resource locator</em></b>
         </dt>
<dd>{no text provided in draft}</dd>
</dl>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Definiton for URL needed. Additional definitions needed -- supported browser,
document, 'same' document, 'different' document, ... </td>
</tr>
</table><br><h4> 3.3 <a name="ClauseRef3.3"></a>Abbreviations [<a href="#0">Top</a>]</h4>
<p>For the purpose of this ISO 10303 standing document, the following abbreviations apply.</p><b>JPEG<a
name="AbbrRefJPEG"></a></b><em> - - Alternate Form(s):
                      jpg<a name="AbbrRefjpg"></a>;
                      .jpg<a name="AbbrRef.jpg"></a>;
                      </em><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table
used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Synonyms added -- this is used so that abbreviation hyperlink anchors can be
automatically generated for all forms of a word and its synonyms and so all instances of the abbreviation can be hyperlinked
back to their definition.</td>
</tr>
</table><br><b> -- <em>Joint Photographic Experts Group</em></b><br><br><b>PNG<a
name="AbbrRefPNG"></a></b><b> -- <em>portable network graphics</em></b><br><br><b>SD<a
name="AbbrRefSD"></a></b><b> -- <em>Supplementary Directives</em></b><br><br><b>URL<a
name="AbbrRefURL"></a></b><b> -- <em>uniform resource locator</em></b><br><br><h3>4 <a
name="ClauseRef4"></a>Supported Browsers [<a href="#0">Top</a>]</h3>
<p>The following browsers are considered to be "supported":</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Supported must be defined if this is term we use.
                   <p>Wouldn't it make more sense to specify the allowable subset of HTML 3.2 or 4.01 and get out of the
browser checking business?</p>
<p>If XML is used only one check is needed, relieving all editors from the checking requirement.</p>
</td>
</tr>
</table><br><ul>
<li>Netscape Communicator version 4.x;</li>
<li>Internet Explorer version 4.x;</li>
<li>Internet Explorer version 5.x; </li>
<li>Internet Explorer version 6.x; </li>
<li>Opera version 5.x; </li>
<li>Mozilla version 0.9.9.</li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Is the meaning of the 'x' understood or does it need to be defined? Are we
supporting all versions (including yet unreleased ones (e.g., Internet Explorer 6.112)? Is this a problem. Suggest that we
explicitly include version numbers in supported browser listing.</td>
</tr>
</table><br><h3>5 <a name="ClauseRef5"></a>Overall document preparation [<a href="#0">Top</a>]</h3>
<h4> 5.1 <a name="ClauseRef5.1"></a>Acceptable digital formats [<a href="#0">Top</a>]</h4>
<p>Documents shall be tagged in accordance with the HTML 3.2 specification.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE 1 It is recommended that the latest version of HTML 3.2 be used.</td>
</tr>
</table><br><p>Editors may use any tool they wish to produce their documents.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE 2 The HTML output translators provided wth word processors such as Microsoft Word and WordPerfect produce
HTML files that do not conform to this standing document, and that will require significant cleanup to be acceptable. The
Quality Committee strongly recommends that editors consider the use of specialized HTML authoring tools.<table
align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment from
reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Word processors changed to word processors in NOTE 2 of clause.</td>
</tr>
</table><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain
informative text of note from surrounding text.">
<tr>
<td>NOTE 3 The Quality Committee has developed lists of tools useful for project teams and editors (see QC N189).</td>
</tr>
</table><br><h4> 5.2 <a name="ClauseRef5.2"></a>Acceptable tags [<a href="#0">Top</a>]</h4>
<p>Only the elements shown as allowed in Table 1 shall be used for document markup.</p><br><a
name="TableRef5.2.a"></a><table width="75%" border="1" summary="A table which lists and describes all HTML elements
and identifies those elemnts that are allowed and those that are not allowed in the mark up of ISO standards documents."
align="center">
<tr>
<th scope="col" colspan="1" align="center">Name</th>
<th scope="col" colspan="1" align="center">Allowed</th>
<th scope="col" colspan="1" align="center">Description</th>
</tr>
<tr>
<td colspan="1" align="center">a</td>
<td colspan="1" align="center">Y</td>
<td colspan="1" align="center">anchor</td>
</tr>
<tr>
<td colspan="1" align="center">abbr</td>
<td colspan="1" align="center">N</td>
<td colspan="1" align="center">abbreviated form (e.g., www, http, etc.)</td>
</tr>
<tr>
<td colspan="1" align="center"></td>
<td colspan="1" align="center"></td>
<td colspan="1" align="center"></td>
</tr>
</table><br><h3 align="center">Table 5.2.a - Elements</h3>
<h4> 5.3 <a name="ClauseRef5.3"></a>Hyperlinks [<a href="#0">Top</a>]</h4>
<p>No normative references or references essential to the understanding of the document shall be hidden in hyperlinks.</p>
<p>A link to another page of the same document shall be a relative link, consisting of the file name only and shall open in
the same browser window.</p>
<p>A link to a page of a different document shall be an absolute link and shall open in a separate browser window.</p>
<h3>6 <a name="ClauseRef6"></a>Page size, fonts, and spacing [<a href="#0">Top</a>]</h3>
<h4> 6.1 <a name="ClauseRef6.1"></a>Page size [<a href="#0">Top</a>]</h4>
<p>A document shall not contain elements that are clipped when then document is printed on A4 (metric standard) paper
stock with the browser's default margins and a magnification of 100%.</p>
<h4> 6.2 <a name="ClauseRef6.2"></a>Fonts and font sizes [<a href="#0">Top</a>]</h4>
<p>Documents shall not contain any markup to force a particular font or font size. In particular, &lt;font&gt; tags shall not be
used.</p>
<h4> 6.3 <a name="ClauseRef6.3"></a>Vertical spacing [<a href="#0">Top</a>]</h4>
<p>Vertical spacing between elements should be used to give a consistent and readable layout to the document without
introducing excessive white space.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE - In general, appropriate spacing is achieved simply by marking text with the appropriate paragraph
(<code>&lt;p&gt;</code>), heading (<code>&lt;h1&gt;</code>, <code>&lt;h2&gt;</code>, etc.) and
<code>&lt;table&gt;</code> tags.</td>
</tr>
</table><br><p>Empty &lt;p&gt; tags shall not be used to introduce additional white space. Instead, &lt;br&gt; tags should
be used.</p>
<h4> 6.4 <a name="ClauseRef6.4"></a>Page layout for parts of SC4 standards [<a href="#0">Top</a>]</h4>
<p>This subclause gives rules and guidelines specific to the layout for all parts of SC4 standards.</p>
<h4> 6.5 <a name="ClauseRef6.5"></a>Page headers and footers [<a href="#0">Top</a>]</h4>
<h5>      6.5.1 <a name="ClauseRef6.5.1"></a>General requirements for page headers and footers. [<a
href="#0">Top</a>]</h5>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>This clause needs to more clearly describe the .html document layout -- it
reads like a description of a printed document. The header I added doesn't match what is written here -- the header I
produced is the "special header" described in clause <a href="#ClauseRef6.5.2">6.5.2</a>. I included it as I only had one
"document" and thus only had one opportunity for a header.</p>
</td>
</tr>
</table><br><p>Except for the cover page and the page on which the title element (see SD Clause 4.2.2) appears and the
scope clause (see SD Clause 4.2.3) begins, a page header shall appear on every page of the document. See clause <a
href="#ClauseRef6.5.2">6.5.2</a> for instructions regarding the special header to be used on page 1 of each standard.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>specific reference added to original document text in the line above (paragraph
1).</td>
</tr>
</table><br><p>The page header shall be the first element following the &lt;head&gt; tag, and shall be tagged as
follows:</p>
<p align="center"><code>&lt;p&gt;document-reference&lt;/p&gt;</code></p>
<p>where document-reference is as given in Table 6 of SD.</p>
<h5>      6.5.2 <a name="ClauseRef6.5.2"></a>"Special" header on page 1 [<a href="#0">Top</a>]</h5>
<p>For the page on which the title element (see 4.2.2) appears and the scope clause (see 4.2.3) begins, the "special"
header specified in SD Clause 5.2.1.2 shall be used. The "special" header consists of two elements, as described in Table 7
of the SD.</p>
<p>The "special" header shall be the first element following the &lt;head&gt; tag, and shall consist of a paragraph containing
a horizontal rule (<code>&lt;hr&gt;</code>), the left-element, the right-element, and a horizontal rule, where left-element and
right-element are as given in Table 7 of the SD.</p>
<p>It shall be tagged as follows:</p>
<pre><code>&lt;p&gt;
&lt;hr /&gt;
left-element&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;right-element
&lt;hr /&gt;
&lt;/p&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table
used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>My tagging for the header is shown below. The <code>align='center'</code>
was used as this displayed much better in less than 100% magnification. Above 100%, the line wraps and 'looks funny no
matter what I did.</p>
<pre><code>
&lt;br&gt;&lt;hr&gt;&lt;h3 align="center"&gt;DRAFT STANDING DOCUMENT
         © ISO 2002 - All rights reserved&lt;/h3&gt;&lt;hr&gt;&lt;br&gt;
&lt;h1&gt;ISO TC184/SC4 Standing Document - Guidelines for
  the format and layout of SC4 standards using HTML&lt;/h1&gt;

 In the .xml instance document, it is coded:

  &lt;HeaderInfo&gt;DRAFT STANDING DOCUMENT &amp;#160;&amp;#160;&amp;#160;
  &amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;
  &amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;
  &amp;#160;&amp;#160;© ISO 2002 - All rights reserved&lt;/HeaderInfo&gt;</code></pre><br><p>Netscape and Explorer
use different size fonts for presentation of (centered) <code>&lt;h1&gt;</code> and the smaller line/larger font of Netscape
determines the spacing that can be used between the elements without printing problems (avoiding line wrap in header -- no
cutoff willl occur, but the line wrap destroys the 'look' of the header.</p>
</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE The following is an example of a special header.</p>
<p>COMMITTEE DRAFT ISO/CD 10303-226</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Poor illlustration presentation, should include a .gif or other file rather than text
(<code>&lt;h1&gt;</code>, <code>&lt;hr&gt;</code> elements not allowed by ISODocument schema. Rather than modify
schema, this example of the header should be a figure (e.g., a .gif file), not in text if created in an .xml/xsl publishing
environment). </p>
</td>
</tr>
</table><br></td>
</tr>
</table><br><h5>         6.5.3 <a name="ClauseRef6.5.3"></a>Page footers [<a href="#0">Top</a>]</h5>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>I did not include footer as I had all-in-one file. Additionally, page counts are not
available within .html -- Most browsers will put a header and footer on the printout but infomation elements and the
placement of the information elements are not controllable through the .html (that I know of). If page is used as defined,
there is only ever one per webpage/file.</td>
</tr>
</table><br><p>All pages apart from the cover page shall have a page footer at the bottom of the page. The page footer
shall be separated from the text on the page by two <code>&lt;br /&gt;</code> tags.</p>
<p>The page footer shall contain:</p>
<ul>
<li>a "Next" link to go to the next page, unless the current page is the last page; </li>
<li>a "Previous" link to go to the previous page, unless the current page is the first page;</li>
<li>the text "Page current-page-number of last-page-number", where current-page-number is the position of the current
page in the sequence of pages making up the document;</li>
<li>a copyright notice, worded "© ISO year-of-publication _ All rights reserved".</li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Bodington </em><p>ISSUE: </p>
<p>AUTHOR: Bodington</p>
<p>CLAUSE: 6.5.3 Page Footers</p>
<p>ALTERNATE CLAUSE: </p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: What does Page mean in the text: "Page current-page-number of last-page-number", where
current-page-number is the position of the current page in the sequence of pages making up the document; It would not be
easy nor appropriate to count printed pages in a Web document. If page means file, then what purpose does the file count
serve? AP214 has many hundreds</p>
<p>PROPOSED SOLUTION: Remove this recommendation.</p>
</td>
</tr>
</table><br><p>The page footer shall be tagged as follows:</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Length of first line in original document had to be shortened (Carriage return
added) to avoid printing cutoff at 100% magnification.</td>
</tr>
</table><br><pre><code>&lt;a href="relative-url-of-previous-page"&gt;Previous&lt;/a&gt;
&lt;p&gt;&lt;a href="relative-url-of-next-page"&gt;Next&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Page current-page-number of last-page-number&lt;/p&gt;
&lt;p&gt;&amp;copy; ISO year-of-publication &amp;#8212; All rights reserved&lt;/p&gt;</code></pre><br><table
align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative text of
example from surrounding text.">
<tr>
<td><p>EXAMPLE The following is an example of a page footer:</p>
<p><a href="#Previous">Previous</a>
      <a href="#Next">Next</a>
     </p>
<p>Page 27 of 341</p>
<p>© ISO 2001 _ All rights reserved</p>
</td>
</tr>
</table><br><h3>7 <a name="ClauseRef7"></a>General format and layout instructions [<a href="#0">Top</a>]</h3>
<h4> 7.1 <a name="ClauseRef7.1"></a>Format and layout of clauses and subclauses [<a href="#0">Top</a>]</h4>
<p>All clauses, subclauses, and subdivisions of subclauses shall begin flush left without indentation. Full justification shall
not be used. Words shall have a single space between them; sentences shall have a single space between them. Words
shall not be hyphenated.</p>
<p>The table of contents, the foreword, the introduction, each top-level clause of the main part of the document, each
annex, the bibliography, and the index shall each begin on a new page.</p>
<h5>      7.1.1 <a name="ClauseRef7.1.1"></a>Clause and subclause headings [<a href="#0">Top</a>]</h5>
<p>A clause or subclause heading is the wording used to introduce a clause or subclause.</p>
<p>Clause and subclause headings shall begin flush left on a line by themselves. Beginning with the scope clause, all
headings shall be numbered with Arabic numbers in sequence. The number for each clause headings shall be followed by at
least two spaces and the text of the headings.</p>
<p>The first word in all headings shall be capitalized. All other words in the heading shall be lower case unless they are
proper nouns.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td>EXAMPLE The following illustrates the format and capitalization of a first level subclause heading.
                          <p><strong>4.1 Units of functionality</strong></p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td>If the .xml document is to be the master, this need to be a figure/illustration rather than text to give proper
display.<em> -- suggested by: JWN </em></td>
</tr>
</table><br><p>This requirement may be superseded by specific requirements for clauses that contain the definitions of
EXPRESS elements (see SD Clause 6.4).</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>would it not be better to state the requirements here, especially if different (different
level) than SDs specify.</td>
</tr>
</table><br><p>Headings shall not contain line breaks. Long titles that wrap around should be avoided, if possible.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Wrap around is a function of magnification; either the magnification level must be
specified for this or it should not be controlled. Even if it looks good at one magnification, other magnifications could look
bad/much worse.</td>
</tr>
</table><br><p>Layout of text on the printed page is highly dependent on the browser and user settings. Therefore, no
attempt should be made to force a heading from the bottom of one printed page to the top of the next. In particular, manual
page break shall not be inserted for this purpose.</p>
<h5>       7.1.2 <a name="ClauseRef7.1.2"></a>Paragraphs [<a href="#0">Top</a>]</h5>
<p>Paragraphs are subdivisions of clauses or subclauses. Paragraphs shall be unnumbered and untitled. Each paragraph
shall be enclosed within a &lt;p&gt; element.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE - Clause 5.1 of an AP starts as follows (see Clause 9.7.1 of the SD):</p>
<p>This clause contains the mapping table that shows how each UoF and application object of this part of ISO 10303 (see
clause <a href="#ClauseRef4">4</a>) maps to one or more AIM constructs (see annex A). The mapping table is organized
in five columns.</p>
<p>Column 1) Application element: Name of an application element as it appears in the application object definition in <a
href="#ClauseRef4.2">4.2</a>. Application object names are written in uppercase. Attribute names and assertions are listed
after the application object to which they belong and are written in lower case.</p>
<p>Column 2) AIM element: Name of an AIM element as it appears in the AIM (see annex <a href="#ClauseRefA">A</a>),
the term "IDENTICAL MAPPING", or the term "PATH". AIM entities are written....</p>
<p>This would be tagged as follows:</p>
<p><code>&lt;p&gt;This clause contains the mapping table that shows how each UoF and application object of this part of
ISO 10303 (see clause &lt;a href=#ClauseRef4&gt;4&lt;/a&gt;) maps to one or more AIM constructs (see annex
&lt;ClauseRef&gt;A&lt;/ClauseRef&gt;). The mapping table is organized in five columns.&lt;/p&gt;</code></p>
<p><code>&lt;p&gt;Column 1) Application element: Name of an application element as it appears in the application object
definition in &lt;a href=#ClauseRef4.2&gt;4.2&lt;/a&gt;. Application object names are written in uppercase. Attribute names
and assertions are listed after the application object to which they belong and are written in lower
case.&lt;/p&gt;</code></p>
<p><code>&lt;p&gt;Column 2) AIM element: Name of an AIM element as it appears in the AIM (see annex &lt;a
href=#AnnexRefA&gt;A&lt;/a&gt;), the term "IDENTICAL MAPPING", or the term "PATH". AIM entities are
written....&lt;/p&gt;</code></p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Clauseref tagging added in above.</td>
</tr>
</table><br></td>
</tr>
</table><br><h5>          7.1.3 <a name="ClauseRef7.1.3"></a>Orphans and widows [<a href="#0">Top</a>]</h5>
<p>Layout of text on the printed page is highly dependent on the browser and user settings. Therefore, no attempt should
be made to prevent widows and orphans (see SD Clause 5.3.1.3) from occuring on the printed page.</p>
<h5>       7.1.4 <a name="ClauseRef7.1.4"></a>Annex headings [<a href="#0">Top</a>]</h5>
<p>Annex headings shall be centered and enclosed within &lt;h2&gt; tags.</p>
<p>The first word of the first heading in each annex shall be "Annex" followed by a space and a capital letter designating the
serial order of the annex. This order shall begin with the letter "A" and continue through the alphabet bypassing the letter "I".
On the next line, the word "normative" or "informative" shall appear in parentheses. The title of the annex shall appear on
the next line. These three lines shall all be enclosed within a single <code>&lt;h2&gt;</code> element and shall be
separated by break (<code>&lt;br&gt;</code>) elements. An extra break element shall be included after the word
"(normative)" or "(informative)" to force a blank line.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Radack </em><p>ISSUE: 5</p>
<p>AUTHOR: Radack</p>
<p>CLAUSE: 7.1.4</p>
<p>ALTERNATE CLAUSE:</p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: The example shows the annex heading centered, but the HTML code in the example does not produce
centering. Also, the normative text does not describe how to center the annex heading.</p>
<p>PROPOSED SOLUTION: Add to normative text to explain how the annex heading is centered, and add necessary
HTML code to the example.</p>
<p>DISCUSSION:</p>
<p>RESOLUTION:</p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>I used a slightly different format -- see Annex <a
href="#AnnexRefA">A</a>.</p>
</td>
</tr>
</table><br><p>A single annex shall be called "Annex A".</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td>EXAMPLE The following illustrates the format of a top-level annex heading.
                          <table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table
used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Again, this needs to be a figure rather than text due to the restriction of the
XML schema -- it doesn't allow <code>AnnexTitles</code> and <code>AnnexIdentifier</code>s in Examples, nor does it
allow insertion of <code>&lt;h2&gt;</code> markup/in-line elements.</p>
</td>
</tr>
</table><br><p align="center"><strong>Annex C</strong></p>
<p align="center"><strong>(normative)</strong></p>
<p align="center"><strong>Implementation method specific requirements</strong></p>
<p>The above would be tagged as follows:</p>
<pre><code>&lt;h2&gt;Annex C&lt;br /&gt;
(normative)&lt;br /&gt;
&lt;br /&gt;
Implementation method specific requirements&lt;/h2&gt;</code></pre><br></td>
</tr>
</table><br><h5>        7.1.5 <a name="ClauseRef7.1.5"></a>An annex of examples [<a href="#0">Top</a>]</h5>
<p>When an annex only contains examples, the text of the annex shall be formatted as normal clause text. It shall not be
formatted as normally required for examples. This annex shall be informative.</p>
<h4> 7.2 <a name="ClauseRef7.2"></a>Format and layout of lists [<a href="#0">Top</a>]</h4>
<p>Each unordered list shall be enclosed within a &lt;ul&gt; element.</p>
<p>Each ordered list shall be enclosed within a &lt;ol&gt; element.</p>
<p>Each item in a list shall be enclosed within a &lt;li&gt; element.</p>
<p>The following summarizes requirements for the format of unordered and ordered lists:</p>
<ul>
<li>Lists may be nested up to four levels (although lists with more than two levels are discouraged).</li>
<li>For ordered lists, use lower case letters, Arabic numerals for level 2, lower case Roman numerals for level 3, and upper
case Roman numerals for level 4. </li>
<li>Use ordered lists when there is a requirement to make reference to specific items in the list; use unordered lists
otherwise. </li>
<li>For unordered lists, use the default symbols to introduce items at any level </li>
</ul>
<p>For ordered lists, the type attribute should be set as shown in Table 2.</p><br><a name="TableRef7.2.a"></a><table
width="50%" border="1" summary="Table showing the numbering styles to be used for multiply embeddedlists."
align="center">
<tr>
<th scope="col" colspan="1" align="center">Level</th>
<th scope="col" colspan="1" align="center">Type</th>
<th scope="col" colspan="1" align="center">Numbering Style</th>
</tr>
<tr>
<td colspan="1" align="center">1</td>
<td colspan="1" align="center">a</td>
<td colspan="1" align="center">lower alpha -- a, b, c, ...</td>
</tr>
<tr>
<td colspan="1" align="center">2</td>
<td colspan="1" align="center">1</td>
<td colspan="1" align="center">arabic numbers -- 1, 2, 3, ....</td>
</tr>
<tr>
<td colspan="1" align="center">3</td>
<td colspan="1" align="center">i</td>
<td colspan="1" align="center">lower roman -- i, ii, iii, ...</td>
</tr>
<tr>
<td colspan="1" align="center">4</td>
<td colspan="1" align="center">I</td>
<td colspan="1" align="center">upper roman -- I, II, III, ...</td>
</tr>
</table><br><h3 align="center">Table 7.2.a - Type attribute setting</h3>
<p>The following examples illustrate the correct formats for lists.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE 1 The following items form an unordered list.</p>
<p>Text xxxx:</p>
<ul>
<li>xxxxx;</li>
<li>xxxxx;</li>
<li>xxxxx.</li>
</ul>
<p>This would be tagged as follows:</p>
<pre><code>
&lt;p&gt;Text xxxx:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;xxxxx;&lt;/li&gt;
  &lt;li&gt;xxxxx;&lt;/li&gt;
  &lt;li&gt;xxxxx.&lt;/li&gt;
&lt;/ul&gt;</code></pre><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td>EXAMPLE 2 The following unordered list includes items at two levels.
<p>Text xxxxx:</p>
<ul>
<li> xxxxx;
 <ul>
<li>yyyyy; </li>
<li>yyyyy;</li>
</ul>
</li>
<li> xxxxx.</li>
</ul>
<p>This would be tagged as follows:</p>
<pre><code>&lt;p&gt;Text xxxxx:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;xxxxx;&lt;/li&gt;
     &lt;ul&gt;
          &lt;li&gt;yyyyy;&lt;/li&gt;
          &lt;li&gt;yyyyy;&lt;/li&gt;
     &lt;/ul&gt;
   &lt;li&gt;xxxxx.&lt;/li&gt;
&lt;/ul&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table
used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>The tagging of this produces parsing complaints when using the W3C browser
AMAYA -- Embedded lists should be part of the <code>&lt;li&gt;</code> and should be coded as follows:</p>
<pre><code>&lt;ul&gt;
   &lt;li&gt;xxxxx;
     &lt;ul&gt;
          &lt;li&gt;yyyyy;&lt;/li&gt;
          &lt;li&gt;yyyyy;&lt;/li&gt;
     &lt;/ul&gt;
   &lt;/li&gt; &lt;!-- Proper Placement --&gt;
   &lt;li&gt;xxxxx.&lt;/li&gt;
&lt;/ul&gt;</code></pre><br><p>This change, if accepted must be reflected in all other examples (the .html code of the
2002-03-13 Draft is correct).</p>
</td>
</tr>
</table><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE 3 - The following items form an ordered list.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>The XSD and XSL needs to be adjusted to reflect <code>type</code>
attributes in lists once numbering hierarchy is decided -- this will give faithful presentation of example lists of this type.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>The use of type for this purpose is deprecated in HTML 4.01.</td>
</tr>
</table><br></td>
</tr>
</table><br><p>Text xxxx:</p>
<p> a. xxxxx; </p>
<p> b. xxxxx; </p>
<p> c. xxxxx.</p>
<p>This would be tagged as follows:</p>
<pre><code>
&lt;p&gt;Text xxxx:&lt;/p&gt;

&lt;ol&gt;
&lt;li type="a"&gt;xxxxx;&lt;/li&gt;
&lt;li type="a"&gt;xxxxx;&lt;/li&gt;
&lt;li type="a"&gt;xxxxx.&lt;/li&gt;
&lt;/ol&gt;</code></pre><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE 4 - The following ordered list includes items at two levels.</p>
<p>Text xxxx:</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>XSL and XML prototype does not currently support this numbering. Will modify
when decided.</td>
</tr>
</table><br><p> a. xxxxx</p>
<p> 1. yyyyy;</p>
<p> 2. yyyyy;</p>
<p>b. xxxxx.</p>
<p>This would be tagged as follows: </p>
<pre><code>&lt;p&gt;Text xxxx:&lt;/p&gt;

&lt;ol&gt;
   &lt;li type="a"&gt;xxxxx&lt;/li&gt;
     &lt;ol&gt;
         &lt;li type="1"&gt;yyyyy;&lt;/li&gt;
         &lt;li type="1"&gt;yyyyy;&lt;/li&gt;
     &lt;/ol&gt;
   &lt;li type="a"&gt;xxxxx.&lt;/li&gt;
&lt;/ol&gt;</code></pre><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE 5 The following ordered list includes items at four levels.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>XSL and XML need to be modified to suppport this numbering once a hierarchy
decision is made/finalized.
                                 <p>Also shouldn't the hierarchy of the symbols be capital Roman numerals, Arabic numerals,
letters, and then small Roman numerals? This is more in keeping with documents I have worked with. A three-level
hierarchy should be Arabic numerals, letters, small Roman numerals, and the two-level should be Arabic numerals and
either letters or small Roman numerals, shouldn't they?.</p>
</td>
</tr>
</table><br><p> a. xxxxx</p>
<p>        1. xxxxx</p>
<p>            i. xxxxx</p>
<p>          ii. xxxxx</p>
<p>                I. xxxxx</p>
<p>              II. xxxxx</p>
<p>        iii. xxxxx</p>
<p>        2. xxxxx</p>
<p>            i. xxxxx</p>
<p>                I. xxxxx</p>
<p>              II. xxxxx</p>
<p>          ii. xxxxx</p>
<p>        3. xxxxx</p>
<p> b. xxxxx</p>
<p>        1. xxxxx</p>
<p>        2. xxxxx</p>
<p> c. xxxxx</p>
<p>This would be tagged as follows:</p>
<pre><code>&lt;ol&gt;
   &lt;li type="a"&gt;xxxxx&lt;/li&gt;
     &lt;ol&gt;
     &lt;li type="1"&gt;xxxxx&lt;/li&gt;
         &lt;ol&gt;
           &lt;li type="i"&gt;xxxxx&lt;/li&gt;
           &lt;li type="i"&gt;xxxxx&lt;/li&gt;
               &lt;ol&gt;
                   &lt;li type="I"&gt;xxxxx&lt;/li&gt;
                   &lt;li type="I"&gt;xxxxx&lt;/li&gt;
                   &lt;li type="I"&gt;xxxxx&lt;/li&gt;
               &lt;/ol&gt;
           &lt;li type="i"&gt;xxxxx&lt;/li&gt;
               &lt;/ol&gt;
                   &lt;li type="1"&gt;xxxxx&lt;/li&gt;
               &lt;ol&gt;
          &lt;li type="i"&gt;xxxxx&lt;/li&gt;
               &lt;ol&gt;
                &lt;li type="I"&gt;xxxxx&lt;/li&gt;
                &lt;li type="I"&gt;xxxxx&lt;/li&gt;
              &lt;/ol&gt;
           &lt;li type="i"&gt;xxxxx&lt;/li&gt;
         &lt;/ol&gt;
      &lt;li type="1"&gt;xxxxx&lt;/li&gt;
    &lt;/ol&gt;
&lt;li type="a"&gt;xxxxx&lt;/li&gt;
   &lt;ol&gt;
      &lt;li type="1"&gt;xxxxx&lt;/li&gt;
      &lt;li type="1"&gt;xxxxx&lt;/li&gt;
   &lt;/ol&gt;
&lt;li type="a"&gt;xxxxx&lt;/li&gt;
&lt;/ol&gt;</code></pre><br></td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE 6 - The following unordered list contains a list item with two paragraphs and an example.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Shouldn't this read - "The following unordered list contains three items. The first
item in the list is composed of two paragraphs, the second item is composed of a paragraph and an Example, and the third
is composed of a single paragraph"?</td>
</tr>
</table><br><ul>
<li><p>xxxxx</p>
<p>xxxxx</p>
</li>
<li><p> xxxxx</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td>EXAMPLE xxxxx </td>
</tr>
</table><br></li>
<li><p>xxxxx</p>
</li>
</ul>
<p>This would be tagged as follows:</p>
<pre><code>&lt;ul&gt;
   &lt;li&gt;
      &lt;p&gt;xxxxx&lt;/p&gt;
      &lt;p&gt;xxxxx&lt;/p&gt;
   &lt;/li&gt;
  &lt;li&gt;
   &lt;p&gt;xxxxx&lt;/p&gt;
   &lt;small&gt;&lt;p&gt;EXAMPLE xxxxx&lt;/p&gt;&lt;/small&gt;
   &lt;/li&gt;
   &lt;li&gt;
      &lt;p&gt;xxxxx&lt;/p&gt;
   &lt;/li&gt;
&lt;/ul&gt;</code></pre><br></td>
</tr>
</table><br><h4> 7.3 <a name="ClauseRef7.3"></a>Format and layout of figures [<a href="#0">Top</a>]</h4>
<h5>         7.3.1 <a name="ClauseRef7.3.1"></a>Placement of figures [<a href="#0">Top</a>]</h5>
<p>Each figure shall appear in one of the following places:</p>
<ul>
<li>immediately following the first paragraph in which it is referenced;</li>
<li>in a separate page containing only the figure and its caption.</li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Use of <em>page</em> here is incompatible with definition in clause <a
href="#ClauseRef3.2.2">3.2.2</a> (<a href="#page">page</a>
     ).</p>
</td>
</tr>
</table><br><p>When a figure is placed in mid-page, it shall be separated from the text by two blank lines before the figure,
one blank line between the figure and the title, and one blank line between the title and the text that follows. A figure shall
not be placed in the middle of a paragraph.</p>
<p>Each figure shall be centered on the page.</p>
<p>Each figure shall consist of an image in GIF (.gif), <a href="#AbbrRefJPEG">JPEG</a>
      (.jpg) or <a href="#AbbrRefPNG">PNG</a>
      (.png) format.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Need to insert cross references after providing for GIF in abbreviations.</td>
</tr>
</table><br><p>The image for a figure shall be referenced by an <code>&lt;img&gt;</code> element. The img element shall
have an alt attribute containing, at a minimum, the figure caption followed by a period. This may be followed by additional
text describing the figure. The <code>alt= ' '</code> attribute should give as complete a description of the figure as
possible.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE - This is important to ensure that the document is understandable when accessed via speech-based or text-only
user agents.</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>I strongly suggest that the <code>alt</code> description "shall give" a
complete description and that it clearly conveys the content of the figure when such information is critical to the visually
impaired user/user agent.</p>
</td>
</tr>
</table><br><p>A figure shall be tagged as follows:</p>
<pre><code>&lt;div align="center"&gt;
&lt;img src="relative-url-of-image-file" alt="figure-caption. description-of-image"&gt;
&lt;/div&gt;</code></pre><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell
table used to separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE - An example of a figure is shown below.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The schema elements in Nazemetz schema are used/included in the figure so
additional elements are shown compared to the original -- identifier, title, description, and location are required in the .xml
file by the schema.</td>
</tr>
</table><br><br><a name="FigRef7.3.1.ex-a"></a><center><img
src="http://www.okstate.edu/ceat/ie/jnazeme/ISO_XML_HTML/Figure1.gif" alt="This is a sample illustration. It has no
normative content."></center><br><h3 align="center">Figure. 7.3.1.ex-a Example</h3><br></td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>While figure is resized from its original page wide display in Part 28 to fit in the
browser display, it will be cutoff during printing as the print driver (at least the ones I tested -- a Xerox copier/printer and an
HP Laser) cut it off. If anyone knows of printer driver settings that will resize when printing to fit the paper, we need to know
and include in this document (at least informatively).</td>
</tr>
</table><br><h5>        7.3.2 <a name="ClauseRef7.3.2"></a>Format for figures [<a href="#0">Top</a>]</h5>
<p>Figures shall be in the form of line drawings. Black and white photographs may be used if such photographs enhance
the understandability and use of the standard and it is not possible to convert them into line drawings (see 6.6.4.2 of the
ISO/IEC Directives Part 3). The content of the figure shall be centered. Text in figures shall be in 8 to 11 point. The point
size of text shall be consistent across a set of figures.
</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Bodington </em><p>ISSUE: </p>
<p>AUTHOR: Bodington</p>
<p>CLAUSE: 7.3.2 Format for figures</p>
<p>ALTERNATE CLAUSE: </p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: Why prevent colour images? There are situations where this is required, e.g. to illustrate colours, layers
and groups in a CAD model.</p>
<p>PROPOSED SOLUTION: </p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Discussion of point sizes, etc. should be in the (suggested) additional subclause on
illustration creation.</td>
</tr>
</table><br><h5>         7.3.3 <a name="ClauseRef7.3.3"></a>Placement of figure captions [<a href="#0">Top</a>]</h5>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Avoid the word "<em>caption</em>"; it has specific meaning in .html (Table
caption).</p>
</td>
</tr>
</table><br><p>Figure captions shall be centered below the figure in bold face. The figure number shall follow the word
"Figure" and shall be followed by a blank space, an em dash, another blank space, and the title of the figure. Only the first
word in the title is capitalized. The figure number, and title shall be on the same line.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE The following is an example of a figure caption:</p><br><a name="FigRef1"></a><center><img src=""
alt=""></center><br><h3 align="center">Figure. 1 Data planning model</h3><br><p>This would be tagged as follows:</p>
<pre><code>&lt;p align="center"&gt;&lt;b&gt;Figure 1 &amp;#8212; Data planning
model&lt;/b&gt;&lt;/p&gt;</code></pre><br></td>
</tr>
</table><br><h4> 7.4 <a name="ClauseRef7.4"></a>Format and layout of tables [<a href="#0">Top</a>]</h4>
<h5>       7.4.1 <a name="ClauseRef7.4.1"></a>Placement of tables [<a href="#0">Top</a>]</h5>
<p>Each table shall appear in one of the following places:</p>
<ul>
<li>immediately following the first paragraph in which it is referenced;</li>
<li>in a separate page containing only the table and its caption. </li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Use of term '<a href="#page">page</a>
     ' in sentence above and in sentence below (mid-page) conflicts with definition in clause <a
href="#ClauseRef3.2.2">3.2.2</a>. It will also result in a printing problem as the separate window/page figure will not be
printed.</p>
</td>
</tr>
</table><br><p>When a table is placed in mid-page, it shall be separated from the text by two blank lines before the figure,
one blank line between the figure and the title, and one blank line between the title and the text that follows. A table shall not
be placed in the middle of a paragraph.</p>
<h5>       7.4.2 <a name="ClauseRef7.4.2"></a>Format for tables [<a href="#0">Top</a>]</h5>
<p>Each table shall be bordered by single lines unless the addition of these lines causes a table that would fit on a single
page to be continued on another page. The headings for each column shall be in bold-face, centred within the column, and
separated from the elements of the column by a double line. All other table columns and rows shall be separated by single
lines. There are two exceptions to this rule:</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Concept of page and continuation to another page/webpage is irrelevant for
html webpages (suggest striking) and number of lines displayed by <code>border='1'</code> etc. is browser-dependant
(Netscape displays one line while Explorer displays two lines for this document (same encoding))</p>.</td>
</tr>
</table><br><ul>
<li>mapping tables of ISO 10303 application protocols shall use double lines to separate mappings for each application
object (see SD clause 9.7.1);</li>
<li>test case input specification tables in ISO 10303 abstract test suites shall use double lines to sepa-rate groups of data
related to individual application objects (see SD clause 9.6.2). </li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Hyphen needs to be removed from sepa-rate; discussion of number of lines is
browser-dependent.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE             The following is an example of a table.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The word 'EXAMPLE' was added to original document in preceding line.</td>
</tr>
</table><br><br><a name="TableRef7.4.2-ex-a"></a><table width="50%" border="1" summary="This is an example table
for illustration only. It has no normative content." align="center">
<tr>
<th scope="col" colspan="1" align="center">Type</th>
<th scope="col" colspan="1" align="center"><p>Linear density</p>
<p>kg/m</p>
</th>
<th scope="col" colspan="1" align="center"><p>Inside diameter</p>
<p>mm</p>
</th>
<th scope="col" colspan="1" align="center"><p>Outside diameter</p>
<p>mm</p>
</th>
</tr>
<tr>
<td colspan="1" align="center">1</td>
<td colspan="1" align="center">3.5</td>
<td colspan="1" align="center">25.0</td>
<td colspan="1" align="center">30.0</td>
</tr>
<tr>
<td colspan="1" align="center">2</td>
<td colspan="1" align="center">4.0</td>
<td colspan="1" align="center">35.0</td>
<td colspan="1" align="center">42.0</td>
</tr>
<tr>
<td colspan="1" align="center">3</td>
<td colspan="1" align="center">4.8</td>
<td colspan="1" align="center">48.0</td>
<td colspan="1" align="center">55.0</td>
</tr>
</table><br><h3 align="center">Table 7.4.2-ex-a - Example table</h3>
</td>
</tr>
</table><br><h5>         7.4.3 <a name="ClauseRef7.4.3"></a>Placement of table numbers and titles [<a
href="#0">Top</a>]</h5>
<p>A table caption shall be centred above the table. The number shall follow the word "Table" and be followed by a space,
an emdash, a space, and the title of the table on the same line.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Avoid use of term table <em>caption</em> (implies tagging as CAPTION) and
the numbering scheme needs to be specified somewhere in this clause. Again, I had problems with the emdash -- I noted it
is not listed as a printable character in HTML 3.2 recommendation</p>.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td><p>EXAMPLE - The following is an example of a table caption:</p><br><a name="TableRef7.4.3-ex-a"></a><table
width="50%" border="1" summary="This is an illustration of a table caption only. No table content is provided."
align="center">
<tr>
<th scope="col" colspan="1" align="center"></th>
</tr>
<tr>
<td colspan="1" align="center"></td>
</tr>
</table><br><h3 align="center">Table 7.4.3-ex-a - Thingamajiggy types</h3>
<p>This would be tagged as follows: </p>
<pre><code>&lt;p align="center"&gt;&lt;b&gt;Table 1 &amp;#8212; Thingamajiggy
types&lt;/b&gt;&lt;/p&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1"
summary="Single cell table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Use of emdash and general presentation needs to be reconsidered.</td>
</tr>
</table><br></td>
</tr>
</table><br><h4> 7.5 <a name="ClauseRef7.5"></a>Layout and format of notes [<a href="#0">Top</a>]</h4>
<p>Each note shall be separated from the body of the clause, subclause, or paragraph to which it refers by a single blank
line. Each note shall be followed by a single blank line. Use a smaller size of the same typeface as used for normal text.</p>
<p>Notes shall not be indented from the left margin.</p>
<p>Use white space to separate the word "NOTE" (and the accompanying number, if present) from the text of the note. This
white space shall be accomplished with five non-breaking space (nbsp) entities. Do not use a hyphen to separate the word
"NOTE" from the text.</p>
<p>Each note shall be enclosed within a <code>&lt;small&gt;</code> element. Each paragraph of the note shall be
enclosed within a <code>&lt;p&gt;</code> element, within the <code>&lt;small&gt;</code> element.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE An example of the format and layout for notes is shown below. The first note would be tagged as follows:
</p>
<pre><code>
&lt;small&gt;&lt;p&gt;NOTE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp:&amp;nbsp;This note is in a "small" font size,
     distinguishing it from surrounding (normative) body text that is set in
     the normal font size.&lt;/p&gt;&lt;/small&gt; </code></pre><br><table align="center" width="100%" border="2"
bgcolor="#FFE4E1" summary="Single cell table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>Formating called out here and as programmed in the XSL does not correspond
-- I did not use the <code>&lt;small&gt;</code> tag as shown below because it will not validate -- the
<code>&lt;small&gt;</code> tag is an in-line element and cannot contain any block elements, such as
<code>&lt;p&gt;</code> -- this is a problem for editors who will have to tag inside each and every block element in a note or
example. In addition, length/line wrap had to be adjusted for printing to avoid cutoff. I suggest that notes and examples be
differentiated by indentation and colored backgrounds rather than font size -- this is especially true when the user is
displaying the page(s) using the smallest font size settings on his /her browser -- the size differential may not be easily
distinguishable.</p>
</td>
</tr>
</table><br><br><a name="TableRef7.5-ex-a"></a><table width="100%" border="1" summary="Table showing the format
that notes should conform to." align="center">
<tr>
<th scope="col" colspan="1" align="center">Type of NOTE</th>
<th scope="col" colspan="1" align="center">Example format</th>
</tr>
<tr>
<td colspan="1" align="left">A "singleton" note</td>
<td colspan="1" align="left"><p>Normative text preceding the note. </p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE This note is in a "small" font size, distinguishing it from surrounding (normative) body text that is set in the normal
font size.</td>
</tr>
</table><br><p>Normative text following the note.</p>
</td>
</tr>
<tr>
<td colspan="1" align="left">Numbered notes</td>
<td colspan="1" align="left"><p>Normative text preceding the note. </p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE 1 First numbered note in a (sub)clause.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain
informative text of note from surrounding text.">
<tr>
<td>NOTE 2 Note that the start of the text of this note is indented further than that of the unnumbered note in the previous
example, but is consistent with other numbered notes. Also, the second and subsequent lines of any note or example are
not indented from the left margin.</td>
</tr>
</table><br><p>             ...</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE 99 Using tab settings rather than space characters allows the text of numbered notes to be aligned even when
there are large numbers of them. </td>
</tr>
</table><br><p>Normative text following the note.</p>
</td>
</tr>
</table><br><h3 align="center">Table 7.5-ex-a - Note formating examples</h3>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Tom Warren </em>'that that' changed to 'than that' in NOTE 2</td>
</tr>
</table><br></td>
</tr>
</table><br><h4> 7.6 <a name="ClauseRef7.6"></a>Layout and format of examples [<a href="#0">Top</a>]</h4>
<p>Each example shall be separated from the body of the clause, subclause, or paragraph to which it refers by a single
blank line. Each example shall be followed by a single blank line. Use a smaller size of the same typeface as used for
normal text.</p>
<p>Examples shall not be indented from the left margin.</p>
<p>Use white space to separate the word "EXAMPLE" (and the accompanying number, if present) from the text of the
example. This white space shall be accomplished with five non-breaking space (nbsp) entities. Do not use a hyphen to
separate the word "EXAMPLE" from the text.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE An example of the format and layout of examples is shown below.</p><br><a
name="TableRef7.6-ex-a"></a><table width="100%" border="1" summary="Table showing the format that examples should
conform to." align="center">
<tr>
<th scope="col" colspan="1" align="center">Type of Example</th>
<th scope="col" colspan="1" align="center">Illustration of formatting</th>
</tr>
<tr>
<td colspan="1" align="left">A "singleton" example</td>
<td colspan="1" align="left"><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table
used to separate informative text of example from surrounding text.">
<tr>
<td>EXAMPLE The text of this example is set flush left.</td>
</tr>
</table><br></td>
</tr>
<tr>
<td colspan="1" align="left">Numbered examples</td>
<td colspan="1" align="left"><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table
used to separate informative text of example from surrounding text.">
<tr>
<td>EXAMPLE 1 First numbered example.</td>
</tr>
</table><br><p> Normative text within the (sub)clause containing examples 1 and 2.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td> EXAMPLE 2 Numbering of notes or examples is continuous within a (sub)clause, even if there is intervening text.</td>
</tr>
</table><br></td>
</tr>
</table><br><h3 align="center">Table 7.6-ex-a - Example formatting samples</h3>
</td>
</tr>
</table><br><h3>8 <a name="ClauseRef8"></a>Format and layout of specific elements [<a href="#0">Top</a>]</h3>
<h4> 8.1 <a name="ClauseRef8.1"></a>Format and layout of the table of contents [<a href="#0">Top</a>]</h4>
<p>The table of contents shall contain the entries specified in SD Clause 4.1.3, without page numbers or dot leaders. Each
entry shall be hyperlinked to the corresponding heading in the document.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE An example of the format and layout of the table of contents is given below.</p>
<p>Contents</p>
<p><a href="#ClauseRef1 Scope">1 Scope</a></p>
<p><a href="#ClauseRef2 Normative references">2 Normative references</a></p>
<p><a href="#ClauseRef3 Terms, definitions and abbreviations">3 Terms, definitions and abbreviations</a></p>
<p><a href="#ClauseRef3.1 Terms defined in ISO 10303-1">3.1 Terms defined in ISO 10303-1</a></p>
<p><a href="#ClauseRef3.2 Terms defined in ISO 10303-31">3.2 Terms defined in ISO 10303-31</a></p>
<p><a href="#ClauseRef3.3 Terms defined in ISO 10303-42">3.3 Terms defined in ISO 10303-42</a></p>
<p><a href="#ClauseRef3.4 Other terms and definitions">3.4 Other terms and definitions</a></p>
<p><a href="#ClauseRef3.5 Abbreviations ">3.5 Abbreviations </a></p>
<p><a href="#ClauseRef4 Information requirements">4 Information requirements</a></p>
<p><a href="#ClauseRef4.1 Units of functionality">4.1 Units of functionality</a></p>
<p><a href="#ClauseRef4.1.1 basic_geometry ">4.1.1 basic_geometry </a></p>
<p><a href="#ClauseRef4.1.2 configuration_management">4.1.2 configuration_management</a></p>
<p><a href="#ClauseRef4.1.3 definitions">4.1.3 definitions</a></p>
<p><a href="#ClauseRef4.1.4 external_references">4.1.4 external_references</a></p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>My style sheet produces a ToC with only the ClauseTitles, not the numbers as
the hyperlinks and indentation of lower items in the hierarchy -- which is better? See my General Comments, <a
href="#ClauseRefGuidelines As Example">Guidelines As Example</a> (bullet three) for an alternative (condensed
format) option and tagging example code for this alternate format ToC. Code example below was reformatted to avoid
printer cutoff.</p>
</td>
</tr>
</table><br><p>This would be tagged as follows:</p>
<pre><code>&lt;h2&gt;Contents&lt;/h2&gt;
&lt;p&gt;&lt;a href="Clause1.html#clause1"&gt;1 Scope&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause2.html#clause2"&gt;2 Normative references
   &lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3"&gt;3 Terms, definitions and
   abbreviations&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3.1"&gt;3.1 Terms defined in
  ISO 10303-1&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3.2"&gt;3.2 Terms defined in
  ISO 10303-31&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3.3"&gt;3.3 Terms defined in
    ISO 10303-42&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3.4"&gt;3.4 Other terms and
   definitions&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause3.html#clause3.5"&gt;3.5 Abbreviations
   &lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4"&gt;4 Information
  requirements&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4.1"&gt;4.1 Units of functionality
   &lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4.1.1"&gt;4.1.1 basic_geometry
   &lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4.1.2"&gt;4.1.2 configuration_
   management&lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4.1.3"&gt;4.1.3 definitions
   &lt;/a&gt;&lt;br&gt;
&lt;a href="Clause4.html#clause4.1.4"&gt;4.1.4 external_
  references&lt;/a&gt;&lt;/p&gt;</code></pre><br></td>
</tr>
</table><br><h4> 8.2 <a name="ClauseRef8.2"></a>Format and layout of the title element [<a href="#0">Top</a>]</h4>
<p>All titles shall have a capital letter on the first word of each section. All other words in the section shall be lower case.
The title shall be contained within a <code>&lt;h1&gt;</code> element. The sections of the title shall be separated by break
(<code>&lt;br&gt;</code>) elements. Break elements shall only be used to separate the sections of the title. "Part :" shall
always appear on a line by itself.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE The title element for ISO 10303-11 is as follows:</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The emdash is a problem here. <table align="center" width="75%" border="2"
bgcolor="#FFF8DC" summary="Single cell table used to contain informative text of note from surrounding text.">
<tr>
<td>The title element in the .xsl file is used as part of the header when the .html is printed -- I used this to put a copyright
symbol on each page rather than the title of the document on each <a href="#printed page">printed page</a>
     .</td>
</tr>
</table><br></td>
</tr>
</table><br><p><strong>Industrial automation systems and integration -</strong></p>
<p><strong>Product data representation and exchange -</strong></p>
<p><strong>Part 11: Description methods: The EXPRESS language reference manual</strong></p>
<p>This would be tagged as follows:</p>
<pre><code>&lt;h1&gt;Industrial automation systems and integration &amp;#8212;&lt;br /&gt;
Product data representation and exchange &amp;#8212;&lt;br /&gt;
Part 11: Description methods: The EXPRESS language reference manual
&lt;/h1&gt;</code></pre><br></td>
</tr>
</table><br><p>The title shall appear at the top of the first page of the main body of text (the page on which the scope
clause begins). The punctuation at the end of the first two sections is an emdash (long dash), character entity _. There shall
be one blank space after the colon that follows the series designator.
</p>
<h4> 8.3 <a name="ClauseRef8.3"></a>Layout and format of normative references [<a href="#0">Top</a>]</h4>
<p>Normative references shall be presented in the following format (conforming to ISO 690). The standard reference
number shall appear in Roman (non-italic) typeface followed by a colon, the date of publication, a comma, and the title of the
standard in italic. Each normative reference shall finish with a period.
</p>
<p>Each normative reference shall be contained within a separate &lt;p&gt; element.</p>
<h4> 8.4 <a name="ClauseRef8.4"></a>Layout and format of terms and definitions [<a href="#0">Top</a>]</h4>
<p>Each term being defined shall occupy its own numbered subclause. The heading for the subclause shall be the term
being defined. The subclause number, the term (together with any synonyms or ab-breviations), and the definition of the
term shall appear on separate lines. Do not place a colon after term. Do not place a period after the definition.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE The following example illustrates the format and layout of a definition:</p>
<p><strong>3.2.3</strong></p>
<p><strong>widget</strong></p>
<p>small part that is left over at the end of every re-assembly process </p>
<p>This would be tagged as follows:</p>
<pre><code>&lt;h3&gt;3.2.3&lt;br&gt;
widget&lt;/h3&gt;
&lt;p&gt;small part that is left over at the end of every re-assembly process
&lt;/p&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table
used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>This is at heading '<code>h4</code>' not '<code>h3</code>' in my
prototype.</p>
</td>
</tr>
</table><br></td>
</tr>
</table><br><h4> 8.4 <a name="ClauseRef8.4"></a>Format for the index [<a href="#0">Top</a>]</h4>
<p>The index shall begin on a new page. The title "Index" be enclosed within a <code>&lt;h2&gt;</code> element. The
terms contained in the index shall be presented as a single column and shall consist of an alphabetical list of terms
addressed in the standard. Each term shall be followed by a list of the clause numbers containing the referenced document
elements, separated by commas. Each entry in the list shall be a hyperlink to the beginning of the heading or paragraph
being referenced.</p>
<p>Each level 2 index entry shall be preceded by five nonbreaking space (&amp;nbsp) character entities.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE The following example illustrates a portion of an index:</p>
<p>        person <a href="#ClauseRef3.3">3.3</a></p>
<p>Person</p>
<p>        application assertion <a href="#ClauseRef4.3.12">4.3.12</a>, <a href="#ClauseRef4.3.19">4.3.19</a></p>
<p>        application object <a href="#ClauseRef4.2.61">4.2.61</a></p>
<p>        ARM diagrams <a href="#FigRefG">G</a></p>
<p>        mapping specification <a href="#ClauseRef5.1.8.4">5.1.8.4</a></p>
<p>person_and_organization <a href="#ClauseRef3.3 ">3.3 </a></p>
<p>This would be tagged as follows:</p>
<pre><code>&lt;div&gt;person &lt;a href="clause3.htm#3.3"&gt;3.3&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;Person &lt;/div&gt;
&lt;div&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;application&amp;nbsp;assertion
   &lt;a href="clause4.htm#4.3.12"&gt;4.3.12&lt;/a&gt;,&lt;a
   href="clause4.htm#4.3.19"&gt;4.3.19&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;application&amp;nbsp;object
   &lt;a href="clause4.htm#4.2.61"&gt;4.2.61&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ARM&amp;nbsp;diagrams
   &lt;a href="figureG_14.htm"&gt;G&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;mapping&amp;nbsp;
  specification &lt;a href="clause5_1#5.1.8.4"&gt;5.1.8.4&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;person_and_organization &lt;a href="clause3.htm#3.3"&gt;
   3.3&lt;a&gt;&lt;/div&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1"
summary="Single cell table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>I really don't understand what you are trying to show here -- why are
<code>&lt;div&gt;</code> tags used rather than <code>&lt;p&gt;</code> tags? I do not discern any hierarchy/classification
from the example. The code was modified to avoid printing problems/cutoff.</p>
</td>
</tr>
</table><br></td>
</tr>
</table><br><h3>9 <a name="ClauseRef9"></a>Main document page [<a href="#0">Top</a>]</h3>
<p>The main page of the document shall contain the following two frames:</p>
<ul>
<li>a frame named "menu" containing a navigation menu; </li>
<li>a frame named "info" in which pages containing the document content are to be displayed. </li>
</ul>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Radack </em><p>ISSUE: 6</p>
<p>AUTHOR: Radack</p>CLAUSE: 9.1
                 <p>ALTERNATE CLAUSE: </p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: There is an inconsistency between the format used for anchors for document clauses in the table of
contents example and the index example.</p>
<p>PROPOSED SOLUTION: Use the same format for anchors for document clauses in both the table of contents and index
examples. Add normative text to specify the format for anchors for document clauses.</p>
<p>DISCUSSION: (NAZEMETZ) -- Anchors not only for clauses need to be specified, but also for annexes, terms (and their
synonyms), abbreviations, bibliography, to/from Table of contents. I kept all references separate by type in the xml
prototype.</p>
<p>RESOLUTION:</p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The HTML 3.2 recommendation makes no mention of frames. Will frames
documents validate? What W3C validator settings should be used for documents containing frames (if any)? Use of frames
will not give a unique url to content mapping; nor will it meet/facilitate web accessibility. I suggest that the use of frames
be prohibited or at least very strongly discouraged.</td>
</tr>
</table><br><p>The navigation menu shall consist of the headings for the main sections of the document.</p>
<p>The main page shall have a title element consisting of document-reference, as defined in Table 6 of the SD.</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td><p>EXAMPLE For the Committee Draft of ISO 10303-226, published in 2001, the main page would be tagged as
follows:
</p>
<pre><code>&lt;html&gt;
&lt;head&gt;
&lt;title&gt;ISO/CD 10303-226:2001(E)&lt;/title&gt;
&lt;/head&gt;

&lt;frameset frameborder="NO" cols="23%,77%" /&gt;
&lt;noframe&gt;You must use a browser that can display frames to see this page.
     &lt;/noframe&gt;
&lt;frame name="menu" src="mainmenu.html"&gt;
&lt;frame name="info" src="cover.html"&gt;
&lt;/frameset&gt;
&lt;/html&gt;</code></pre><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell
table used to separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p><code>&lt;noframe&gt;</code> line modified to avoid printing cutoff
problems.</p>
</td>
</tr>
</table><br></td>
</tr>
</table><br><h3>10 <a name="ClauseRef10"></a>File naming and directory structure [<a href="#0">Top</a>]</h3>
<p>All files for a document shall be in the same directory.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Bodington </em><p>ISSUE:</p>
<p>AUTHOR: Bodington</p>
<p>CLAUSE: 10 File naming and directory structure</p>
<p>ALTERNATE CLAUSE: </p>
<p>CLASSIFICATION: MINOR/TECHNICAL</p>
<p>DESCRIPTION: Why enforce all files for a document to be in one directory? Why not allow sub directories. If an
Application Protocol is considered one document you will end up hundreds of files in a single directory.</p>
<p>PROPOSED SOLUTION: Reword to: All files for a document shall be in one directory, or organized into
itssub-directories. </p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Using Part 25 ballot materials as a counter example, the zipped files are in one
directory and the links won't work -- are additional requirements needed here?</td>
</tr>
</table><br><p>A file name shall contain only the following characters:</p>
<ul>
<li>lower case letters (a-z);
                  </li>
<li>digits (0-9); </li>
<li>underscore (_); </li>
<li>dash (-); </li>
<li>period (.). </li>
</ul>
<p>A file name shall contain only one period. The period separates main part of the file name from the file extension.</p>
<p>Each file shall have an extension of between one and three characters. For the file types in Table <a
href="#TableRef7.2-a">7.2-a</a>, the extensions shown in Table 3 shall be used.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Table number changed to reflect numbering scheme in XML schema. References
to defined terms added to the table to show capability to cross reference.</td>
</tr>
</table><br><br><a name="TableRef10.a"></a><table width="50%" border="1" summary="List of file types and extensions
that shall be used." align="center">
<tr>
<th scope="col" colspan="1" align="center">File type</th>
<th scope="col" colspan="1" align="center">Extension</th>
</tr>
<tr>
<td colspan="1" align="center">GIF</td>
<td colspan="1" align="center">gif</td>
</tr>
<tr>
<td colspan="1" align="center">HTML</td>
<td colspan="1" align="center">gif</td>
</tr>
<tr>
<td colspan="1" align="center"><a href="#JPEG">JPEG</a>
     </td>
<td colspan="1" align="center">jpg</td>
</tr>
<tr>
<td colspan="1" align="center"><a href="#PNG">PNG</a>
     </td>
<td colspan="1" align="center">png</td>
</tr>
<tr>
<td colspan="1" align="center">TIFF</td>
<td colspan="1" align="center">tif</td>
</tr>
</table><br><h3 align="center">Table 10.a - File extensions</h3>
<p>The main part of the file name for a file containing a clause of a document shall consist of the word "clause" followed by
the clause number, with periods replaced by underscores.</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Bodington </em><pre><code>ISSUE:
AUTHOR: Bodington
CLAUSE: 10 File naming and directory structure
ALTERNATE CLAUSE:
CLASSIFICATION: MINOR/TECHNICAL
DESCRIPTION:
Why be prescriptive about the naming of files?
It may be appropriate to name the file "armdiag1" or "armdiag2"
Why prevent the use of index.htm? That way a user will know which is the
primary document to open to start browsing.
If you have to have a WGnumber.htm then set up a meta tag
to redirect to the index
&lt;meta http-equiv="Refresh" content="10; URL=./index.htm"&gt;

PROPOSED SOLUTION:
Recommend the naming convention given but allow other conventions.</code></pre><br></td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>If all clauses are contained in a single file, file naming becomes irrelevant -- I
favor single file approach for reasons stated earlier in General Comments <a href="#ClauseRefGuidelines As Example
">Guidelines As Example </a>(bullet 2).</p>
</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td>EXAMPLE 1 The file name for a file containing Clause 5.2 of a document would be "clause5_2.htm".</td>
</tr>
</table><br><p>The main part of the file name for a file containing a figure shall consist of the word "figure" followed by the
figure number. The figure number may be padded with leading zeroes.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE By padding figure numbers with sufficient leading zeroes, the editor can ensure that figures appear in proper
numeric order when the directory is listed in alphabetic order.</td>
</tr>
</table><br><table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to
separate informative text of example from surrounding text.">
<tr>
<td>EXAMPLE 2 A document contains 37 figures. The file name for Figure 2, which is in JPEG format, is be "figure02.jpg".
             <table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>The consecutive numbering convention defined in this clause can/will cause
significant problems during editing, On behalf of editors who will need to renumber all figure filenames, hyperlinks, and
identifiers upon the addition or deletion of a figure, I urge you to consider consecutive numbering within clause (or help
develop a tool to automatically update numbering and crossreferences in an .html or .xml document or set of
files/documents.</td>
</tr>
</table><br></td>
</tr>
</table><br><p>No file of the document, as delivered by the editor, shall be named "index.htm" or "default.htm".</p>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>This statement directly conflicts with Table <a href="#TableRef10.b">10.b</a> -
the last row calls for an "index.htm" file. A clear place to start in a set of files (consider the Part 25 files in its zip archive) is
needed.</p>
</td>
</tr>
</table><br><p>The main part of the file name for the main document page shall be the document's N-number followed by
an underscore, followed by the word "main".</p>
<table align="center" width="75%" border="2" bgcolor="#FFFACD" summary="Single cell table used to separate informative
text of example from surrounding text.">
<tr>
<td>EXAMPLE The file name for the main document page of WG3 N9999 would be "wg3n9999_main.htm".
             <table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Should be EXAMPLE 3 </td>
</tr>
</table><br></td>
</tr>
</table><br><p>The file names in Table 4 shall be used for the document components specified.</p><br><a
name="TableRef10.b"></a><table width="50%" border="1" summary="List of file types and extensions that shall be used."
align="center">
<tr>
<th scope="col" colspan="1" align="center">Component</th>
<th scope="col" colspan="1" align="center">File name</th>
</tr>
<tr>
<td colspan="1" align="center">Cover page</td>
<td colspan="1" align="center">cover.htm</td>
</tr>
<tr>
<td colspan="1" align="center">Foreword</td>
<td colspan="1" align="center">foreword.htm</td>
</tr>
<tr>
<td colspan="1" align="center">Introduction</td>
<td colspan="1" align="center">introduction.htm</td>
</tr>
<tr>
<td colspan="1" align="center">Table of contents</td>
<td colspan="1" align="center">contents.htm</td>
</tr>
<tr>
<td colspan="1" align="center">List of figures</td>
<td colspan="1" align="center">figures.htm</td>
</tr>
<tr>
<td colspan="1" align="center">List of tables</td>
<td colspan="1" align="center">tables.htm</td>
</tr>
<tr>
<td colspan="1" align="center">Bibliography</td>
<td colspan="1" align="center">bibliography.htm</td>
</tr>
<tr>
<td colspan="1" align="center">Index</td>
<td colspan="1" align="center">index.htm</td>
</tr>
</table><br><h3 align="center">Table 10.b - File extensions</h3>
<h3>11 <a name="ClauseRef11"></a>Validation and testing [<a href="#0">Top</a>]</h3>
<p>The editor shall test the document on at least one of the supported browsers. The editor should test the document on as
many of the supported browsers as is feasible. The editor should test the document on at least one supported version of
Netscape Communicator and one supported version of Internet Explorer.
</p>
<p>The editor shall test all hyperlinks within the document.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>NOTE It is recommended that a tool be used for this purpose.</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em>Conditions for a successful (passing) of the test is required here, requiring the
conducting of a test is insufficient.</td>
</tr>
</table><br><p>The editor shall check for disallowed tags using the validtags.xsl stylesheet, as described in Annex <a
href="#ClauseRefA">A</a>.</p>
<p>The editor shall validate the document using the World Wide Web Consortium's HTML Validation Service <a
href="http://validator.w3.org/">http://validator.w3.org/</a> with the following settings:</p><br><a
name="TableRef11.a"></a><table width="50%" border="1" summary="Listing of settings to be used for validation"
align="center">
<tr>
<th scope="col" colspan="1" align="center">Parameter</th>
<th scope="col" colspan="1" align="center">Setting</th>
</tr>
<tr>
<td colspan="1" align="center">Document type</td>
<td colspan="1" align="center">HTML 3.2</td>
</tr>
<tr>
<td colspan="1" align="center">Character encoding</td>
<td colspan="1" align="center">Auto detect</td>
</tr>
</table><br><h3 align="center">Table 11.a - Validation setting</h3>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><p>A minor point, but the setting is "<code>Detect automatically</code>" not
'<code>Auto detect</code>' on the W3C page and the character encoding should specified to be ISO 8859-1 shouldn't
it?</p>
</td>
</tr>
</table><br><table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to
separate comment from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: JWN </em><h3>Add-In <a name="ClauseRefAdd-In"></a>Example of Document
Configuration Managment [<a href="#0">Top</a>]</h3>
<p>This clause was added to illustrate the concept of a single file/document that could contain and correctly display various
versions of the document, for example, changes brought about through the introduction of a technical corregenda.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>The schema and the xsl in the prototype need to be changed to allow the existance of the Insertion and Deletion
elements in CoverPage, Metadata, and Bibliography if that is what committee desired to do -- confirm that and any/all
other major elements that can include 'replaceable by TC/new edtion' elements (Paragraphs, Examples, Notes, ...) are
correct in schema and stylesheets.</td>
</tr>
</table><br><p>This is the original text in the clause that preceded the content that needed to be corrected.</p>
<table bgcolor="#FA8072" alt="Table used for formatting of Deletion text. No normative interpretation of tabular form.">
<td>
<h3>Deletion Authorized by: Proposed Technical Corrigenda<br></h3>
<p>This is an example of a section of text that is changed/deleted by the approval of the Technical
Corrigenda..</p><br></td>
</table><br><table bgcolor="#F0FFF0" alt="Table used for formatting of Insertion text. No normative interpretation of
tabular form">
<td>
<h3>Insertion Authorized by: Proposed Technical Corrigenda<br></h3>
<p>This is an example of a section of text that was added by the approval of a Technical Corrigenda 1.</p><br></td>
</table><br><p>This is the first line of the original text that follows the changes made by the TC.</p>
</td>
</tr>
</table><br><h3>Add-In <a name="ClauseRefAdd-In"></a>Example of Document Configuration Managment of Previously
Approved Changes [<a href="#0">Top</a>]</h3>
<p>This clause was added to illustrate the presentation of previously approved changes (that is, those that would be in the
document at the time of a third or subsequent review/revision (whether by TC, SEDS, or later editions) within the normative
text when the changes are embedded in a single file/document that contains all changes (approved as well as suggested
changes/comments generated during this round of review.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>The schema and the xsl in the prototype need to be changed to allow the existance of the Insertion and Deletion
elements in CoverPage, Metadata, and Bibliography if that is what committee desired to do -- confirm that and any/all
other major elements that can include 'replaceable by TC/new edtion' elements (Paragraphs, Examples, Notes, ...) are
correct in schema and stylesheets.</td>
</tr>
</table><br><p>This is the original (pre- first TC, SEDS, or edition changes) text in the clause that preceded the content that
is being deleted by TC2 (previously corrected by SEDS 1.</p>
<table bgcolor="#FA8072" alt="Table used for formatting of Deletion text. No normative interpretation of tabular form.">
<td>
<h3>Deletion Authorized by: Technical Corrigenda 2<br></h3>
<p>This is a section of text that was deleted by the previous approval of Technical Corrigenda 2.</p>
<table bgcolor="#FA8072" alt="Table used for formatting of Deletion text. No normative interpretation of tabular form.">
<td>
<h3>Deletion Authorized by: SEDS 1<br></h3>
<p>Text/material deleted by SEDS 1.</p><br></td>
</table><br><table bgcolor="#F0FFF0" alt="Table used for formatting of Insertion text. No normative interpretation of
tabular form">
<td>
<h3>Insertion Authorized by: SEDS 1<br></h3>
<p>This is material that was inserted by SEDS 1 and subsequently deleted by TC 2.</p><br></td>
</table><br><br></td>
</table><br><table bgcolor="#F0FFF0" alt="Table used for formatting of Insertion text. No normative interpretation of
tabular form">
<td>
<h3>Insertion Authorized by: Technical Corrigenda 2<br></h3>
<p>Example of text added by TC 2.</p><br></td>
</table><br><p>Intervening normative original text that is followed by a TC 1 addition.</p>
<table bgcolor="#F0FFF0" alt="Table used for formatting of Insertion text. No normative interpretation of tabular form">
<td>
<h3>Insertion Authorized by: Technical Corrigenda 1<br></h3>
<p>This is an example of a section of text that was added by the previous approval of Technical Corrigenda
1.</p><br></td>
</table><br><p>This is the first line of the original (pre-first TC,SEDS, or edition changes) text that follows the changes
made by TC 1.</p>
<table align="center" width="75%" border="2" bgcolor="#FFF8DC" summary="Single cell table used to contain informative
text of note from surrounding text.">
<tr>
<td>If desired by the committee, the presentation could be modified to show only the current version of the document and
remove any/all colored backgrounds. It was suggested by Tom Warren (2002-03-28) that during review and revision, the
entire history of the doucment be visible/presented to the reviewers/editors so that they could better
understand/remember/comment on revisions.</td>
</tr>
</table><br><h3 align="center">Annex A <a name="AnnexRefA"></a> Use of validtags.xsl stylesheet [<a
href="#0">Top</a>]</h3>
<h5 align="center">This annex and any/all of its subannexes is normative.</h5>
<table align="center" width="100%" border="2" bgcolor="#FFE4E1" summary="Single cell table used to separate comment
from reviewer from surrounding text.">
<tr>
<td><em> -- suggested by: Radack </em>The content of this annex will be added in the next version. <p></p>
</td>
</tr>
</table><br><br><br><h3><a name="#Bibliography">Bibliography</a></h3>
<p> [1] <a name="BibRef1"></a>No Entries Provided in Draft.<br><br></p>
</html>

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:11/13/2012
language:Unknown
pages:46
About Good!!!NICE!!! The best document database!