[osis-core] (no subject)

Thu, 28 Aug 2003 12:40:14 -0400

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C36D61.87143690
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0007_01C36D61.87143690"

------=_NextPart_001_0007_01C36D61.87143690
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

------=_NextPart_001_0007_01C36D61.87143690
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_001_0007_01C36D61.87143690--

------=_NextPart_000_0006_01C36D61.87143690
Content-Type: application/octet-stream;
	name="items"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="items"

General issues with respect to texts other than bibles.

 1. Whitespace: 
    - double spacing after the end of a sentence?

    - do we allow xml:space="preserve" ?
    - xml whitespace handling: whitespace in element content context
      is superfluous -- deleted.
    - do we want to enumerate a set of rules on what whitespace to preserve? 
        E.g. handle intra- and inter-element whitespace differently
    - how to handle tabs in a document?
    - <p xml:space="preserve"><w>hello</w> 
    	<w>world!</w>&#160; </p>
      <z>hel</z> <z>lo</z>
      may lose its inter-word spacing
    - what does the schema allow for whitespace handling?
    - what are best practices for whitespace handling?
    - Are there different specifications for different conformance levels?

Hello world. Here's my contact info:
^T	Harry Plantinga
^T	1740 Kight Circle

<p>Hello world.</p>
<lg>
  <l>Harry Plantinga</l>
  <l>1740 Knight Circle</l>
</lg>

<p>Hello world.<lb/>
  Harry Plantinga<lb/>
  1740 Knight Circle
</p>

<p>Hello world.</p>
<list>
  <item>Harry Plantinga</item>
  <item>1740 Knight Circle</item>
</list>

 The w case: <w>hello</w> <w>world</w> <w>how</w> <w>are</w>
 	<w>you</w>?

 * The Todd Proposal:
    - assume HTML semantics of whitespace within an element
    - inter-element whitespace is deleted 
    - use <w>word </w> or 
          <w>word</w><seg> </seg> or 
	  <w>word</w>&#160;

 * The Troy Proposal:
    - <w>hello</w> <w>world</w> -- the space there is not deleted
    - whitespace  nodes are collapsed to a space if they contain a return.

 * The Harry Proposal:
    - add xml:space="preserve" to the schema for all elements
    - note that the default behavior is up to the application;
      if you are using a stylesheet mechanism such as CSS or XSLT, 
      it may have its own whitespace controls
    - to handle <w>hello</w> <w>world</w>, use e.g. 
      <p xml:space="preserve"><w>hello</w> <w>world</w></p>
      And<seg xml:space="preserve">  he  </seg>said, "let there be light."

 2. Conformance levels
    - level 1
      - Valid OSIS XML
    - level 2
    - level 3
    - level 4

 3. Presentation-level formatting 
    - do we allow <hi type="bold">?
    - can we attach a CSS stylesheet somehow?
      * use XML stylesheet recommendation
    - does it vary according to conformance level?

---- after discussing specific document types ----

 4. Are there any general principles emerging from specific document
    type guidelines?

 5. Should there be any schema changes for particular sorts of documents?

 ----------------------
 Notes for an OSIS editor:
   - should be able to hide tags, e.g. <w>

------=_NextPart_000_0006_01C36D61.87143690--