[osis-core] User's Manual - .09! comments
Steven J. DeRose
osis-core@bibletechnologieswg.org
Wed, 19 Nov 2003 12:40:30 -0500
--============_-1142858769==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Nice caveats at the beginning, but lose the "!"s.
Let's call it "Draft" rather than alpha or beta.
"This manual is meant to be a guide for all user's of the OSIS" lose
the apostrophe.
Do we have a CSS we can refer from a stylesheet PI, so the doc can be
loaded as-is and at least somewhat display in browsers?
Should we have comments directed to the osis user list as
well/instead of us? Should we list you as (at least) primary editor)?
And the inner core me, troy, todd, chris?) as co-editors?
Can we get vspace between LIs?
"recognized by form-aware processors" -- probably need a note
pointing to some info on what an architectural form is -- or, we
could add a glossary at some point.
"See Appendix ***, Validating Your OSIS Document" -- resolve stars,
and set title italic
(BTW, I have a real nice Goudy cursive 18pt you could use for that --
is lead truetype-compatible?)
"(for example, you can't insert a Bible book within a footnote)" --
isn't that untrue, because books are a type of div, and div is
probably (?) allowed in footnote? not sure.
" can be downloaded as a package from the OSIS website." let's at
least put in the link and a dummy page.
"Most such programs also read an XML schema" -- should we note in
passing that there are three schema languages, and that OSIS is at
this time only provided in XML-Schema form? And maybe a pointer to
trang?
Nice that you've bolded tag names in the text.
"The value will generally be the short name of what is being encoded,
in this case the Contemporary English Version, or CEV." -- Mention
":The short name is defined in the *work* declaration for the work,
described later."
"that it number the proscriptions" -- "s"
" It is called "canonical", and always have a value" -- have/has
"Note that the match between osisIDWork="CEV" in osisText and
osisWork="CEV" in the work element links this osisText to this
particular work element. " -- add after: This *work* element should
(must?) be the first work element."
"See Appendix G: USMARC Relator Codes for the complete list of role
codes provided by the USMARC organization." This list covers an
enormous range, and it should seldom if ever be necessary to use a
code not from this list.
"Publisher element in the work element" -- Prepend "The"
"The type attribute must be set to "ISO-639," "ISO-639-2," or "SIL,""
-- bold theattribute values (and throughout)
Under "type" attribute: Add "Note that the Dublin Core type element
is distinct from the OSIS type attribute (the latter can occcur on
any OSIS element, to distinguish relevant subdivisions of the type).
Under Identifier: All the abbreviations are all-caps except the
*first* one, "Dewey". Suggestions: Change to "DEWEY"; put some
delimiter between the abbrevvs and their descriptions; note that as
with other names and values, these are case-sensitive
"Note that without the proper type attribute" -- bold type
"HOwever,"
"(particular older works)," --> "ly"
NB: We may want to write an LC-scraper that takes a pointer to a
directory full of OSIS texts, grabs out the author names, and looks
them up in LC to find their authority entry, and copy that entry for
us. We could also introduce a standard authority-list format (say,
topic maps/PSIs in a particular form? And a tool to convert LC
authority entries into that form? nice shot in the arm for us, topic
maps, and for stdzn of auth lists, which LC has not yet managed....
7.5. Date formats" -- this appears to be the third distinct date
format we introduce -- Can we collapse the prior syntaxes with this
one? (mostly an issue of colons vs. dots, and what truncations are
allowed, I think)?
"In such works, use the osisID attribute to identify the retrievable
portions" -- bold attr name.
"as found in standard work easier" -- s
"so long as verses and chapter " -- s
"The paragraph need not give an osisID for the set of verse " -- s
"there are exceptions to this, " append "elsewhere in the Bible"
"Sometimes a verse or chapter starts or end " -- s
"Elements that are "milestoneable" in the OSIS schema are" -- Prepend
" Empty elements are indicated in XML by a tag with "/" preceding the
final ">": thus "<verse/>" rather than <verse> or </verse>. Elements
used in this way are commonly called "milestones", and those
particular elements in OSIS that permit this alternate encoding are
thus called "milestoneable".
"A way to declare the list of characters, or castList;" bold element name
"to be listed separatelyl; "
"of an individualmaking an"
"Note that in this example the high priest's short speech in verse 1
is marked up as a normal container element with normal start- and
end-tags, because it fits within the bounds of the verse. However,
Stephen's speech starts in the middle of verse 2 and continues to the
end of verse 53. This necessitates marking up verse 2 using a
milestone pair, as shown. The other verses are entirely enclosed
within the speech, and so need not be marked up using milstone pairs.
When a conflict arises between the scope of chapter/verse units and
other units, the chapter/verse units give way by being represented as
milestones. If a conflict arises between two other units (say, a
quote that encompasses part but not all of each of two paragraphs),
it is left to the encoder's discretion which or them is represented
via milestones." -- Did we prohibit this a little earlier where we
said you can't mixed milestoned and non-milestoned elements? or was
that just for verses and chapters? Have to clarify this or it looks
like a contradiction.
"Thus, like TEI, markup of poetry refers to lines and line groups. "
-- quote or embolden
"The lg or "line group" element " -- bold
"Thus it covers for units like couple" -- append "t"
"The l element " -- bold
NB: Can we reduce the vertical space above and below examples?
Add example for <lb/>. Also add bold in description where appropriate.
"12.6.4. table" -- we should at least say whether nested tables are permitted.
"rather then just within either" s/then/than/
" For example, <milestone type="page> n="3"/>" -- turn gt into quote
to fix syntax.
Lay out predefined types the same everywhere -- I like the way the
milestone types are done, and would match the others to it. Except,
I'd also bold the labels.
"The start of the first column need not be marked " -- Prepend
"Assuming page boundaries are also marked,"
Reference: add example?
"<verse osisID="NRSV:Mark.5.41">He took her by the hand and said to
her: <q><foreign xml:lang="arc">Talitha cum</foreign></q>, which
means, <q>Little girl, get up!</q></verse>" -- preformatted line too
line -- break it up so it stays visible.
"Provides simple text highlighting capability; types can " -- s/types
can/types that can
" the <hi> element" -- lose brackets and gain bold (likewise anywhere
else this happens)
"If it is known why a word or phrase " -- s/known/known with
reasonable certainty"
At end of "hi" section append: If needed, additional types may be
added, but must begin with "x-".
"Your are Simon sone of John" -- s/sone/son/
"Remember that a computer cannot distinguish Job, as in the man from
Ur, from job, as in 'I have a job for you...' without your
assistance" -- append (at least at the beginning of a sentence)
"Any use of any form of the name of the Deity is marked with
divineName. " -- In that case, how do we formally distinguish the
tetragrammaton? type on divinename? should we enumerate the extant
Biblical phrases as types, such as el, el shaddai, el elyon, ado---,
y---, etc.?
"boudnaries"
" At this time it is intended for use within notehi> elements." -- fix
"This example illustrates (or reinforces several points):" -- move
")" left 2 words
"A note appear" -- s
Under "w": at least list permitted attributes and their meanings, and
note that we're working on a linguistic annotation module..
"To identify a reference ito</i> a" -- fix
"For example, pThe correctness" -- fix
" The scope element " -- bold
"(without the colon, it would be interpreted as a top-level
identifier within the work)." -- s/the work/the default work/
"(introded by Whittingham about ????)," -- typo, finish & add ref?
"The parts of an osisID may contain any mixture of numbers, letters,
hyphens, and underscore. However, to avoid conflict with the other
punctuations used (such as ":" to separate the work from the in-work
location, "@" to separate fine-grained references in osisRefs, and
"!" to separate work-specifiec extensions to a versification scheme),
no other characters are allowed. " -- is it true hyphens are allowed?
Doesn't that croak range syntax?
""!" as the terminator (after which encoders may append names and/or
numbers to provide finer-grained reference points)." -- Explain what
this is doing here -- too abrupt transition.
NB: We should state that there is no need for an explicit work
element to declare the reference systems whose names we have
predefined. Probably say that here, and earlier where they are listed.
"or a section heading in the Mark " -- lose "the"
"within a given canonically-reference unit." -- d
"To refer to specific locations within a named canonical reference
element" -- prepend subhead "Fine-grained references".
"No markup included within the element specifies" -- d
NB: Under this section, what shall we say about ignorable whitespace?
"purposes of layout or printing" -- add ", indexing, "
"Thus, the intuitive count will not be changed by the insertion of
notes, references, critical apparatus, and the like)." -- balance ()
"Grains: s finds " -- replace with "s (short for "string") finds"
"BTG intends to develop an XML schema for declaration files that can
express such systems, and their mapping to other systems. This work
has not been completed. However, we reserve the following names for
versification schemes we already know to be relevant:
Hebrew
NA27
SamPent
LXX" -- synchronize this list with the earlier one (perhaps just
by cross-referencing and deleting it here).
"The header must include work declarations for the document itself,
and for the versification system it uses.
" -- perhaps append "except that the predefined versification systems
need not have work declarations."
"actualloy"
"unproofead"
"Howeve,"
That's all I got. It's looking pretty good; very few bits missing,
good examples, etc.
Hurrah!
S
--
Steve DeRose -- http://www.derose.net
Chair, Bible Technologies Group -- http://www.bibletechnologies.net
Email: sderose@acm.org or steve@derose.net
--============_-1142858769==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [osis-core] User's Manual - .09!
comments</title></head><body>
<div>Nice caveats at the beginning, but lose the "!"s.</div>
<div><br></div>
<div>Let's call it "Draft" rather than alpha or beta.</div>
<div><br></div>
<div>"This manual is meant to be a guide for all user's of the
OSIS" lose the apostrophe.</div>
<div><br></div>
<div>Do we have a CSS we can refer from a stylesheet PI, so the doc
can be loaded as-is and at least somewhat display in browsers?</div>
<div><br></div>
<div>Should we have comments directed to the osis user list as
well/instead of us? Should we list you as (at least) primary editor)?
And the inner core me, troy, todd, chris?) as co-editors?</div>
<div><br></div>
<div>Can we get vspace between LIs?</div>
<div><br></div>
<div>"<font face="Times New Roman" size="+1"
color="#000000">recognized by form-aware processors</font>" --
probably need a note pointing to some info on what an architectural
form is -- or, we could add a glossary at some point.</div>
<div><br></div>
<div><font face="Times New Roman" size="+1" color="#000000">"See
Appendix ***, Validating Your OSIS Document</font>" -- resolve
stars, and set title italic</div>
<div><br></div>
<div>(BTW, I have a real nice Goudy cursive 18pt you could use for
that -- is lead truetype-compatible?)</div>
<div><br></div>
<div>"<font face="Times New Roman" size="+1" color="#000000">(for
example, you can't insert a Bible book within a footnote)</font>"
-- isn't that untrue, because books are a type of div, and div is
probably (?) allowed in footnote? not sure.</div>
<div><br></div>
<div>"<font face="Times New Roman" size="+1" color="#000000"> can
be downloaded as a package from the OSIS website.</font>" let's
at least put in the link and a dummy page.</div>
<div><br></div>
<div>"<font face="Times New Roman" size="+1" color="#000000">Most
such programs also read an XML schema" -- should we note in
passing that there are three schema languages, and that OSIS is at
this time only provided in XML-Schema form? And maybe a pointer to
trang?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Nice that
you've bolded tag names in the text.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
value will generally be the short name of what is being encoded, in
this case the Contemporary English Version, or CEV." -- Mention
":The short name is defined in the *work* declaration for the
work, described later."</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"that
it number the proscriptions" -- "s"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" It
is called "canonical", and always have a value" --
have/has</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"Note
that the match between<b> osisIDWork="CEV"</b> in<b>
osisText</b> and<b> osisWork="CEV"</b> in the<b> work</b>
element links this<b> osisText</b> to this particular<b> work</b>
element. " -- add after: This *work* element should (must?)
be the first work element."</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"See
Appendix G: USMARC Relator Codes for the complete list of role codes
provided by the USMARC organization." This list covers an
enormous range, and it should seldom if ever be necessary to use a
code not from this list.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Publisher element in the work element" --
Prepend "The"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
type attribute must be set to "ISO-639," "ISO-639-2,"
or "SIL,"" -- bold theattribute values (and
throughout)</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Under
"type" attribute: Add "Note that the Dublin Core
type element is distinct from the OSIS type attribute (the latter can
occcur on any OSIS element, to distinguish relevant subdivisions of
the type).</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Under
Identifier: All the abbreviations are all-caps except the *first* one,
"Dewey". Suggestions: Change to "DEWEY"; put some
delimiter between the abbrevvs and their descriptions; note that as
with other names and values, these are case-sensitive</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"Note
that without the proper type attribute" -- bold type</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"HOwever,"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"(particular older works)," -->
"ly"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">NB: We may
want to write an LC-scraper that takes a pointer to a directory full
of OSIS texts, grabs out the author names, and looks them up in LC to
find their authority entry, and copy that entry for us. We could also
introduce a standard authority-list format (say, topic maps/PSIs in a
particular form? And a tool to convert LC authority entries into that
form? nice shot in the arm for us, topic maps, and for stdzn of auth
lists, which LC has not yet managed....</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+2" color="#000000"><b>7.5.
Date formats"</b></font> -- this appears to be the third distinct
date format we introduce -- Can we collapse the prior syntaxes with
this one?<font face="Times New Roman" size="+1" color="#000000">
(mostly an issue of colons vs. dots, and what truncations are allowed,
I think)?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"In
such works, use the osisID attribute to identify the retrievable
portions" -- bold attr name.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"as
found in standard work easier" -- s</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"so
long as verses and chapter " -- s</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
paragraph need not give an<b> osisID</b> for the set of verse "
-- s</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"there are exceptions to this, " append
"elsewhere in the Bible"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Sometimes a<b> verse</b> or<b> chapter</b>
starts or end " -- s</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Elements that are "milestoneable" in
the OSIS schema are" -- Prepend " Empty elements are
indicated in XML by a tag with "/" preceding the final
">": thus "<verse/>" rather than
<verse> or </verse>. Elements used in this way are
commonly called "milestones", and those particular elements
in OSIS that permit this alternate encoding are thus called
"milestoneable".</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"A
way to declare the list of characters, or castList;" bold element
name</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"to
be listed separatelyl; "</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"of
an individualmaking an"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"Note
that in this example the high priest's short speech in verse 1 is
marked up as a normal container element with normal start- and
end-tags, because it fits within the bounds of the verse. However,
Stephen's speech starts in the middle of verse 2 and continues to the
end of verse 53. This necessitates marking up verse 2 using a
milestone pair, as shown. The other verses are entirely enclosed
within the speech, and so need not be marked up using milstone pairs.
When a conflict arises between the scope of chapter/verse units and
other units, the chapter/verse units give way by being represented as
milestones. If a conflict arises between two other units (say, a quote
that encompasses part but not all of each of two paragraphs), it is
left to the encoder's discretion which or them is represented via
milestones." -- Did we prohibit this a little earlier where we
said you can't mixed milestoned and non-milestoned elements? or was
that just for verses and chapters? Have to clarify this or it looks
like a contradiction.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Thus, like TEI, markup of poetry refers to lines
and line groups. " -- quote or embolden</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
lg or "line group" element " -- bold</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"Thus
it covers for units like couple" -- append
"t"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
l element " -- bold</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">NB: Can we
reduce the vertical space above and below examples?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Add
example for <lb/>. Also add bold in description where
appropriate.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"<b>12.6.4. table</b>"</font> -- we should
at least say whether nested tables are permitted.</div>
<div><br></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"rather then just within either"
s/then/than/</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" For
example, <milestone type="page> n="3"/>"
-- turn gt into quote to fix syntax.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Lay out
predefined types the same everywhere -- I like the way the milestone
types are done, and would match the others to it. Except, I'd also
bold the labels.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
start of the first column need not be marked " -- Prepend
"Assuming page boundaries are also marked,"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Reference:
add example?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"</font><font face="Courier New" size="-3"
color="#000000"><verse osisID="NRSV:Mark.5.41">He took
her by the hand and said to her: <q><foreign
xml:lang="arc">Talitha cum</foreign></q>,
which means, <q>Little girl, get up!</q></verse>"
-- preformatted line too line -- break it up so it stays
visible.</font></div>
<div><font face="Courier New" size="-3"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Provides simple text highlighting capability;
types can " -- s/types can/types that can</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" the
<hi> element" -- lose brackets and gain bold (likewise
anywhere else this happens)</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"If
it is known why a word or phrase " -- s/known/known with
reasonable certainty"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">At end of
"hi" section append: If needed, additional types may be
added, but must begin with "x-".</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"</font><font face="Courier New" size="-3"
color="#000000">Your are Simon sone of John</font><font
face="Times New Roman" size="+1" color="#000000">" --
s/sone/son/</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Remember that a computer cannot distinguish<i>
Job,</i> as in the man from Ur, from<i> job,</i> as in 'I have a job
for you...' without your assistance" -- append (at least at the
beginning of a sentence)</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"Any
use of any form of the name of the Deity is marked with<i>
divineName</i>. " -- In that case, how do we formally distinguish
the tetragrammaton? type on divinename? should we enumerate the extant
Biblical phrases as types, such as el, el shaddai, el elyon, ado---,
y---, etc.?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"</font>boudnaries<font face="Times New Roman"
size="+1" color="#000000">"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" At
this time it is intended for use within<b> note</b>hi> elements."
-- fix</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"This
example illustrates (or reinforces several points):" -- move
")" left 2 words</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"A
note appear" -- s</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">Under
"w": at least list permitted attributes and their meanings,
and note that we're working on a linguistic annotation
module..</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"To
identify a reference<b> i</b>to</i> a" -- fix</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"For
example,<b> p</b>The correctness" -- fix</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" The
scope element " -- bold</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"(without the colon, it would be interpreted as a
top-level identifier within the work)." -- s/the work/the default
work/</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"(introded by Whittingham about ????)," --
typo, finish & add ref?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
parts of an osisID may contain any mixture of numbers, letters,
hyphens, and underscore. However, to avoid conflict with the other
punctuations used (such as ":" to separate the work from the
in-work location, "@" to separate fine-grained references in
osisRefs, and "!" to separate work-specifiec extensions to a
versification scheme), no other characters are allowed. " -- is
it true hyphens are allowed? Doesn't that croak range
syntax?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">""!" as the terminator (after which
encoders may append names and/or numbers to provide finer-grained
reference points)." -- Explain what this is doing here -- too
abrupt transition.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">NB: We
should state that there is no need for an explicit work element to
declare the reference systems whose names we have predefined. Probably
say that here, and earlier where they are listed.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"or a
section heading in the Mark " -- lose
"the"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"within a given canonically-reference unit."
-- d</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"To
refer to specific locations within a named canonical reference
element" -- prepend subhead "Fine-grained
references".</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"No
markup included within the element specifies" -- d</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">NB: Under
this section, what shall we say about ignorable
whitespace?</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"purposes of layout or printing" -- add
", indexing, "</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Thus, the intuitive count will not be changed by
the insertion of notes, references, critical apparatus, and the
like)." -- balance ()</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Grains: s finds " -- replace with "s
(short for "string") finds"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"BTG
intends to develop an XML schema for declaration files that can
express such systems, and their mapping to other systems. This work
has not been completed. However, we reserve the following names for
versification schemes we already know to be relevant:<br>
<br>
</font><font face="Courier New" size="-3" color="#000000"><br>
Hebrew<br>
NA27<br>
SamPent</font></div>
<div><font face="Courier New" size="-3" color="#000000">
LXX" -- synchronize this list with the earlier one (perhaps just
by cross-referencing and deleting it here).</font></div>
<div><font face="Courier New" size="-3"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">"The
header must include work declarations for the document itself, and for
the versification system it uses.</font></div>
<div><font face="Times New Roman" size="+1" color="#000000">" --
perhaps append "except that the predefined versification systems
need not have work declarations."</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"actualloy"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"unproofead"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">"Howeve,"</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1" color="#000000">That's all
I got. It's looking pretty good; very few bits missing, good examples,
etc.</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">Hurrah!</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><font face="Times New Roman" size="+1"
color="#000000">S</font></div>
<div><font face="Times New Roman" size="+1"
color="#000000"><br></font></div>
<div><br></div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Steve DeRose -- http://www.derose.net<br>
Chair, Bible Technologies Group --
http://www.bibletechnologies.net<br>
Email: sderose@acm.org or steve@derose.net</div>
</body>
</html>
--============_-1142858769==_ma============--