[osis-core] osis_0108 released!
Todd Tillinghast
osis-core@bibletechnologieswg.org
Thu, 11 Apr 2002 13:28:31 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0024_01C1E15C.C6475910
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
(NOTE THIS IS NOT THE OFFICIAL PATRICK RELEASE.)
I checked into the schema with the IBM Schema checker. I have modified
both schema a little (Idea is the same just better Schema (maybe I
should say "now valid").
I put simple versions of OSISID, OSISIDREF, OSISIDREFS, and
ReferenceType in OSISCore_01081.xsd and then "xs:redefine"d them in
OSISScripture_01081.xsd.
(Sorry about taking up the OSIS_0107 name, hope using OSIS_01081 is more
acceptable.)
I also added "startNote" and "stopNote" to <note> as ReferenceType and
added "reference" and "referenceEnd" to <div> as ReferenceType.
I have not had a chance to run my usual test on this version but am
going to be out for the next few hours and wanted to get you a valid
version since I have one.
I will update the OSISJosephus version later.
The main issue I see at present is that <div> has both "type" and
"divType" attributes and <note> has "noteType" and "type" attribute.
These cases have their own list of types and they are getting the "type"
attribute for "globalAttributes".
Todd
> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Thursday, April 11, 2002 6:44 AM
> To: osis-core
> Subject: [osis-core] osis_0108 released!
>
> Guys,
>
> Todd has come up with an extension mechanism that beats all that
legacy
> COBOL code he is always bragging about still being in use. ;-)
>
> Basic notion is that we have a core set of elements that can then be
> extended or restricted depending upon the type of literature that you
> are encoding. Should give us more flexibility in dealing with Bible
> related literature.
>
> Since Todd used osis_0107 for that modification, I have iterated to
the
> next number so there will be no confusion about the mistakes I have
> introduced! ;-)
>
> Basically took Todd's idea and simply made two files (Todd had types
> split into another file but I suspect easier to extend/modify if we
have
> a single core file and all mods held in a second file.) The
> OSISScripture_0108.xsd file is the one to load. It calls the other
file
> and adds ReferenceType, etc. to the osisCore_0108.xsd.
>
> Added roles into the main file since they are rather short.
>
> Generated all the usual documentation.
>
> Anyone interested in a conference call say Friday or Saturday? (Please
> refresh my supply of phone numbers. Still catching up from the laptop
> that died.)
>
> Looks stronger every time we go around!
>
> I will try to clean out the headers and move revision history to a
> separate document. Need to desparately do some user manual type stuff
> and documentation.
>
> Going into the office today to meet with the user documentation writer
> so will be both offline and away from phones for most of the day (say
> about 8 AM to 4 PM).
>
> Patrick
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
------=_NextPart_000_0024_01C1E15C.C6475910
Content-Type: text/xml;
name="osisCore_01081.xsd"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="osisCore_01081.xsd"
<?xml version=3D"1.0" encoding=3D"UTF-8"?>=0D<xs:schema =
xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" =
elementFormDefault=3D"unqualified">=0D <xs:annotation>=0D =
<xs:documentation> Revision History <p>=0D =
<date>2002-01-31</date>=0D <version>.01</version>=0D =
<resp>PLD</resp>First draft of schema following Dallas meeting, 24-27 =
January 2002. Comments for drafters will be removed prior to public =
release.</p>=0D <p>=0D <date>2002-02-06</date>=0D =
<version>.02</version>=0D <resp>PLD</resp>Added =
annotation/documentation to schema. Began constructing with incremental =
validation using SchemaValidator from IBM. Began using group elements =
for content models and attributes.</p>=0D <p>=0D =
<date>2002-02-08</date>=0D <version>.03</version>=0D =
<resp>PLD</resp>Completed header except for <refsDecl> and =
possible elements for translation and version (both of which should be =
in the <refsDecl> element? Note the notion of using <title> =
instead of head and similar elements for other title like portions of =
the text.</p>=0D <p>=0D <date>2002-02-10</date>=0D =
<version>.04</version>=0D <resp>PLD</resp>Work began in earnest on =
the body and related elements. Note the use of <titleGroup> within =
<body>, <div>, <book>, <chapter>. I am using =
that instead of a free floating <head> element. I think it will =
give authors the flexibility to add whatever title/head like content to =
the text at any point without the confusion of <head>, plus =
<title>, plus whatever other header type structure we could =
invent.</p>=0D <p>=0D <date>2002-02-11</date>=0D =
<version>.04</version>=0D <resp>PLD</resp>Content models sans the =
reference materials. Should be enough to start debugging the schema as a =
whole.</p>=0D <p>=0D <date>2002-02-14</date>=0D =
<version>.05</version>=0D <resp>PLD</resp>After much email =
correspondence over the last two days, substantially reforming the =
content model to allow for recursive nesting of div elements. Also added =
enumerated types for divs, which should simplify the content models by =
eliminating book, chapter and similar group elements. Note that =
lineGroup has been swallowed up by div, where it actually =
belongs.</p>=0D <p>=0D <date>2002-02-18</date>=0D =
<version>.06</version>=0D <resp>PLD</resp>Finished the revisions =
noted for version .05 and am working on validation. Note that the ID =
attribute on milestones are also used as keys for the key/keyRef =
mechanism. This means that all keys are unique and all keyrefs are also =
declared to be unique. Should result in requiring a matching keyref that =
is unique within the relevant div structure.</p>=0D <p>=0D =
<date>2002-03-01</date>=0D <version>.07</version>=0D =
<resp>PLD</resp>Major as well as minor changes: ID is now optional; =
created translationGroup for elements such as ampRead, changedTense, =
ntProphecy, otProphecy, supplied, since they are all claims about the =
text; need a reduced set on roles for this version and move to a =
separate file (eventually), roles will also become 3-letter =
abbreviations and the explanatory text will be in documentation =
elements; new element, lineGroup to contain line; list (now an orphan) =
will be add to div element, name element becomes mixed content to allow =
Mr., Dr., The Most Honored, Reverend, etc.; new element, divineName, =
with enumerated set (closed); attribute on name becomes =
human/nonhuman</p>=0D <p>=0D <date>2002-03-03</date>=0D =
<version>.08</version>=0D <resp>PLD</resp>Final cleanup before =
release of first public beta! Will release with version number .10, =
since planning on one more revision for general approval tomorrow before =
the public release. I think I have finally remembered all the orphans! =
Please check carefully, that would be a very bad thing for the public =
release!</p>=0D <p>=0D <date>2002-03-06</date>=0D =
<version>.095</version>=0D <resp>PLD</resp>Opps! Skipped a version in =
the log. Will reconstruct. New addtions as the separate includes for =
book names, one universal milestone element, fixed title to remove mixed =
=3D true, minor typo fixes to the book names so they will be valid =
IDs.</p>=0D <p>=0D <date>2002-03-07</date>=0D =
<version>.096</version>=0D <resp>PLD</resp>Added Todd's reference =
schema and Protestant canon for reference testing. Added Chris's =
corrected set of book names. Cleaned up the content model (some) to =
remove B-C-V as an alternative hierarchy. Makes the data model cleaner =
anyway. Set default value on calendar to ISO, added other types as per =
Chris.</p>=0D <p>=0D <date>2002-03-10</date>=0D =
<version>.097</version>=0D <resp>PLD</resp>Cleaned up attribute names =
(case) and corrected the content model on milestones (should be called =
allowing 0 or unbounded but within the group as xs:choice).</p>=0D =
<p>=0D <date>2002-03-11</date>=0D <version>.098</version>=0D =
<resp>PLD</resp>Added attachement to note, double ended pointing with =
both ends optional. Included Catholic scripture reference as default =
since it is the larger set of books. Due to the`reference validation I =
have not included the other works.</p>=0D <p>=0D =
<date>2002-03-12</date>=0D <version>.099</version>=0D =
<resp>PLD</resp>Corrected typo in reference "or" list (thanks to =
Chris!), modified the naming on the cathScriptureReference.xsd to be =
compScriptureReference.xsd. Move reference inside the main =
schema.</p>=0D <p>=0D <date>2002-03-16</date>=0D =
<version>.0100</version>=0D <resp>PLD</resp>Numerous corrections as =
submitted by Todd. Added notePart to make the note model more =
robust.</p>=0D <p>=0D <date>2002-03-18</date>=0D =
<version>.0101</version>=0D <resp>PLD</resp>Hopefully last version =
before public beta. More corrections from Todd. Suggested opening =
paragraph for documentation follows.</p>=0D <p>=0D =
<date>2002-03-18</date>=0D <version>.0101</version>=0D =
<resp>PLD</resp>Welcome to the first beta release of the OSIS schema! =
Comments, corrections, etc., should be directed to: =
osis-editors@bibletechnologies.org.</p>=0D <p>The OSIS schema is an =
effort to build an extensible schema for Bible (primarily) encoding but =
can be used for other works related to the Bible. This first schema does =
not have all the mechanisms that would be desired by a publisher, =
translator or scholar. That is by design and and it is intended to =
provide a reasonable learning curve for anyone wishing to use markup to =
encode biblical texts. Later modules will build upon this basis so that =
users can leverage their knowledge of this schema in mastering more =
advanced modules.</p>=0D <p>This schema would not have been possible =
without the generous contributions of time and resources by SIL, LOGOS, =
Hosanna Foundation, ABSi, ABS, SBL, as well as the following =
individuals; Dennis Drescher, Nathan Miles, Alan Conner, Bob Pritchett, =
Mike Perez, John Walter, Trevon Gross, Adina Hamik, Robert Hogdson, Kees =
De Blois, Kent Richards, Troy Griffiths, Chris Little, Todd Tillinghast, =
Steven DeRose and others. If poor memory or records has caused your name =
to be omitted here, please excuse the oversight and contact the editors =
to have it added.</p>=0D <p>The editorial team that has been doing =
almost daily iterations and testing of the beta release: Chris Little, =
chrislit@crosswire.org, Troy Griffiths, scribe@crosswire.org, Todd =
Tillinghast, todd@contentframeworks.com, Steven DeRose, =
sderose@speakeasy.net, and Patrick Durusau, pdurusau@emory.edu.</p>=0D =
<p>=0D <date>2002-03-21</date>=0D <version>.0102</version>=0D =
<resp>PLD</resp>Added derivations on <divineName>, =
<foreign>, <inscription>, <name>, <speaker>, and =
<w> as per Todd (included test file as well, much =
appreciated!).</p>=0D <p>=0D <date>2002-03-27</date>=0D =
<version>.0103</version>=0D <resp>PLD</resp>Fixed content models =
(simpleContent) for foreName, head, item, head, orgName, pubPlace, =
publisher, reference, surName (all from Chris). Deleted groupLine and =
caption, plus fixed item to add annotationGroup, added attributes to =
referenceGroup, fixed titlePart (all from Todd).</p>=0D <p>=0D =
<date>2002-04-02</date>=0D <version>.0104</version>=0D =
<resp>PLD</resp>Nearing the end of any substantial changes (hopefully!). =
Front matter: copyright, Todd proposes following XSEM's model. =
copyrightStmt/copyright(container for work, copyrightDate (container for =
year), year, holder). Suggested model: keep current copyright, add =
elements for work, copyrightDate, year, holder and place in the current =
copyright element. </p>=0D <p>=0D <date>2002-04-08</date>=0D =
<version>.0105</version>=0D <resp>PLD</resp>Unfortunately a major =
revision due to uncaught syntax errors by XMLSpy! Allowed multiple =
datatypes of ID on a single element! Bad joss! Numerous other tweaks and =
changes as well. Tried for better linking model in milestones. Added =
some documentation inside the schema for various elements.</p>=0D =
<p>=0D <date>2002-04-09</date>=0D <version>.0106</version>=0D =
<resp>PLD</resp>Another major re-write, this time on attributes as well =
as the promised referencing scheme. Consolidated all global attributes, =
moving what were types under elements to elementType attribute =
names.</p>=0D <p>=0D <date>2002-04-10</date>=0D =
<version>.0107</version>=0D <resp>DTT</resp>Major architectural =
changes to make adaptation easier, core module now called by literature =
specific modules.</p>=0D <p>=0D <date>2002-04-11</date>=0D =
<version>.0108</version>=0D <resp>PLD</resp>Adaptation of =
architectural revision from .0107. Primary change was to incorporate =
types of lists into OSIS so future changes would only require one new =
driver file for changes.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:simpleType name=3D"attributeExtension">=0D =
<xs:annotation>=0D <xs:documentation>=0D <p>Where attribute values =
are declared, users can extend the allowed values by prepending the =
string "x-" to the values they desire to use. Attribute values =
are declared as the union of an enumerated set of values and this =
attributeExtension type.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:restriction base=3D"xs:string">=0D =
<xs:pattern value=3D"x-([^\s]+)"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D <xs:simpleType name=3D"calendar">=0D =
<xs:restriction base=3D"xs:string">=0D <xs:enumeration =
value=3D"Chinese"/>=0D <xs:enumeration value=3D"Gregorian"/>=0D =
<xs:enumeration value=3D"Islamic"/>=0D <xs:enumeration =
value=3D"ISO"/>=0D <xs:enumeration value=3D"Jewish"/>=0D =
<xs:enumeration value=3D"Julian"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D <xs:simpleType name=3D"divsOSIS">=0D =
<xs:annotation>=0D <xs:documentation>=0D <p>Enumerated list of =
types of div elements in an OSIS text. Note that users can add types of =
divs using the x- extension prefix on their type names.</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:restriction =
base=3D"xs:string">=0D <xs:enumeration value=3D"appendix"/>=0D =
<xs:enumeration value=3D"book"/>=0D <xs:enumeration =
value=3D"chapter"/>=0D <xs:enumeration value=3D"concordance"/>=0D =
<xs:enumeration value=3D"glossary"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D <xs:attributeGroup name=3D"globalAttributes">=0D =
<xs:attribute name=3D"lang" type=3D"languageType" use=3D"optional"/>=0D =
<xs:attribute name=3D"reference" type=3D"ReferenceType" =
use=3D"optional"/>=0D <xs:attribute name=3D"referenceEnd" =
type=3D"ReferenceType" use=3D"optional"/>=0D <xs:attribute =
name=3D"type" type=3D"xs:string" use=3D"optional"/>=0D =
</xs:attributeGroup>=0D <xs:attributeGroup =
name=3D"startMilestoneAttributes">=0D <xs:attribute name=3D"OSISID" =
type=3D"OSISID" use=3D"required"/>=0D <xs:attribute name=3D"OSISIDREF" =
type=3D"OSISIDREF" use=3D"optional"/>=0D </xs:attributeGroup>=0D =
<xs:attributeGroup name=3D"endMilestoneAttributes">=0D <xs:attribute =
name=3D"OSISID" type=3D"OSISID" use=3D"optional"/>=0D <xs:attribute =
name=3D"OSISIDREF" type=3D"OSISIDREF" use=3D"required"/>=0D =
</xs:attributeGroup>=0D <xs:simpleType name=3D"languageType">=0D =
<xs:annotation>=0D <xs:documentation>=0D <p>A regex to validate ISO =
and Ethnologue language codes.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:restriction base=3D"xs:string">=0D =
<xs:pattern value=3D"(x|i|[A-Za-z]{2,3})(-[A-Za-z0-9]{2,8}){0,}"/>=0D =
</xs:restriction>=0D </xs:simpleType>=0D <xs:simpleType =
name=3D"namesOSIS">=0D <xs:annotation>=0D <xs:documentation>=0D =
<p>Enumerated list of name types commonly found in biblical =
texts.</p>=0D </xs:documentation>=0D </xs:annotation>=0D =
<xs:restriction base=3D"xs:string">=0D <xs:enumeration =
value=3D"geographic"/>=0D <xs:enumeration value=3D"holiday"/>=0D =
<xs:enumeration value=3D"nonhuman"/>=0D <xs:enumeration =
value=3D"person"/>=0D <xs:enumeration value=3D"ritual"/>=0D =
</xs:restriction>=0D </xs:simpleType>=0D <xs:simpleType =
name=3D"notesOSIS">=0D <xs:annotation>=0D <xs:documentation>=0D =
<p>Enumerated list of note types for biblical texts.</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:restriction =
base=3D"xs:string">=0D <xs:enumeration value=3D"allusion"/>=0D =
<xs:enumeration value=3D"alternative"/>=0D <xs:enumeration =
value=3D"background"/>=0D <xs:enumeration value=3D"citation"/>=0D =
<xs:enumeration value=3D"devotional"/>=0D <xs:enumeration =
value=3D"exegesis"/>=0D <xs:enumeration value=3D"explanation"/>=0D =
<xs:enumeration value=3D"study"/>=0D <xs:enumeration =
value=3D"translation"/>=0D <xs:enumeration value=3D"variant"/>=0D =
</xs:restriction>=0D </xs:simpleType>=0D <xs:simpleType =
name=3D"role">=0D <xs:annotation>=0D <xs:documentation>=0D <p>This =
is a selected set of the most common role names likely to be needed for =
basic encoding. Users who need the fuller set of role names should =
modify the include statement to load: fullRoleNames.xsd. Note that only =
this file or fullRoleNames.xsd should be loaded in any one =
schema.</p>=0D </xs:documentation>=0D </xs:annotation>=0D =
<xs:restriction base=3D"xs:string">=0D <xs:enumeration =
value=3D"adp">=0D <xs:annotation>=0D <xs:documentation>Adapter: =
Use for a person who 1) reworks a musical composition,usually for a =
different medium, or 2) rewrites novels or stories for motionpictures or =
other audiovisual medium.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"ann">=0D =
<xs:annotation>=0D <xs:documentation>Annotator: Use for a person who =
writes manuscript annotations on a printed item.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"art">=0D <xs:annotation>=0D <xs:documentation>Artist: =
Use for a person (e.g., a painter) who conceives, and perhaps also =
implements, an original graphic design or work of art, =
</xs:documentation>=0D </xs:annotation>=0D </xs:enumeration>=0D =
<xs:enumeration value=3D"aut">=0D <xs:annotation>=0D =
<xs:documentation>Author: Use for a person or corporate body chiefly =
responsiblefor the intellectual or artistic content of a work, usually =
printed text. This term may also be used when more than one person or =
body bears such responsibility.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"aqt">=0D <xs:annotation>=0D <xs:documentation>Author in =
quotations or text extracts : Use for a person whose work is largely =
quoted or extracted in a works to which he or she did not contribute =
directly. Such quotations are found particularly in exhibition =
catalogs, collections of photographs, etc.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"aft">=0D <xs:annotation>=0D <xs:documentation>Author of =
afterword, colophon, etc. : Use for a person or corporate body =
responsible for an afterword, postface, colophon, etc. but who isnot the =
chief author of a work.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"aui">=0D =
<xs:annotation>=0D <xs:documentation>Author of introduction, etc. : =
Use for a person or corporate body responsible for an introduction, =
preface, foreword, or other critical introductory matter, but who is not =
the chief author.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"bnd">=0D =
<xs:annotation>=0D <xs:documentation>Binder: </xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"bdd">=0D <xs:annotation>=0D <xs:documentation>Binding =
designer: Designer of binding</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"bkd">=0D <xs:annotation>=0D <xs:documentation>Book =
designer: Use for the person or firm responsible for the entire graphic =
design of a book, including arrangement of type and illustration,choice =
of materials, and process used.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"bkp">=0D <xs:annotation>=0D <xs:documentation>Book =
producer: Use for the person or firm responsible for the production of =
books and other print media, if specific codes</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"bjd">=0D <xs:annotation>=0D <xs:documentation>Bookjacket =
designer : Designer of bookjacket</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"bpd">=0D <xs:annotation>=0D <xs:documentation>Bookplate =
designer: Designer of bookplate</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"ctg">=0D <xs:annotation>=0D =
<xs:documentation>Cartographer: </xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"clb">=0D <xs:annotation>=0D =
<xs:documentation>Collaborator: Use for a person or corporate body that =
takes a limited part in the elaboration of a work of another person or =
corporate body that brings complements (e.g., appendices, notes) to the =
work.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"cmm">=0D =
<xs:annotation>=0D <xs:documentation>Commentator: Use for a person =
who provides interpretation, analysis,or a discussion of the subject =
matter on a recording, motion picture, or other audiovisual =
medium.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"cwt">=0D =
<xs:annotation>=0D <xs:documentation>Commentator for written text: =
Use for a person or corporate body responsible for the commentary or =
explanatory notes about a text. For the writer of manuscript =
annotations in a printed book, use Annotator</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"com">=0D <xs:annotation>=0D <xs:documentation>Compiler: =
Use for a person who produces a work or publication by selecting and =
putting together material from the works of various persons or =
bodies.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"ctb">=0D =
<xs:annotation>=0D <xs:documentation>Contributor : Use for one =
whose work has been contributed to a larger work, such as an anthology, =
serial publication, or other compilation of individual works. Do not use =
for someone whose sole function in relation to a work is as author, =
editor, compiler or translator.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"cre">=0D <xs:annotation>=0D <xs:documentation>Creator : =
Use for a person or corporate body responsible for the intellectual or =
artistic content of a work.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"edt">=0D =
<xs:annotation>=0D <xs:documentation>Editor: Use for a person who =
prepares for publication a work not primarily his/her own, such as by =
elucidating text, adding introductory or other critical matter, or =
technically directing an editorial staff.</xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"ilu">=0D <xs:annotation>=0D =
<xs:documentation>Illuminator: </xs:documentation>=0D =
</xs:annotation>=0D </xs:enumeration>=0D <xs:enumeration =
value=3D"ill">=0D <xs:annotation>=0D =
<xs:documentation>Illustrator: Use for the person who conceives, and =
perhaps also implements, a design or illustration, usually to accompany =
a written text.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D <xs:enumeration value=3D"pbl">=0D =
<xs:annotation>=0D <xs:documentation>Publisher: =
</xs:documentation>=0D </xs:annotation>=0D </xs:enumeration>=0D =
<xs:enumeration value=3D"trl">=0D <xs:annotation>=0D =
<xs:documentation>Translator: Use for a person who renders a text from =
one language into another, or from an older form of a language into the =
modern form.</xs:documentation>=0D </xs:annotation>=0D =
</xs:enumeration>=0D </xs:restriction>=0D </xs:simpleType>=0D =
<xs:element name=3D"text">=0D <xs:complexType>=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>Front and body element are required and =
in that sequence. This is implied by the sequence content model. Note =
that back is optional, but if occurs, only once.</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:sequence>=0D =
<xs:element ref=3D"front"/>=0D <xs:element ref=3D"body"/>=0D =
<xs:element ref=3D"back" minOccurs=3D"0"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"front">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>Note to working group. To be removed before =
pubication. Note that this particular front matter model requires the =
initial sequence as shown. Once all these elements have occurred, you =
could have a variety of divs for front matter. Question: should not only =
the sequence be required but the occurrences as well?</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:complexType>=0D =
<xs:sequence>=0D <xs:group ref=3D"titleGroup"/>=0D <xs:element =
ref=3D"author" maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"date" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"copyright" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"publisher" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"pubPlace" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"revisionDesc" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"div" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"body">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>Note the use of the xs:choice group between =
<div> and <chapter>. In one sense I think we need to be =
clear that you can have <chapter> elements inside <div> =
elements but that you should not mix them under the <body> =
element, at least at the same level. I can imaging cases where OSIS will =
be applied to texts with only a single <div> element as understood =
in TEI semantics and it seems easier to let users to choose =
<chapter> for such works. Note that this allows us to declare both =
the <div> and <chapter> elements elsewhere and use in this =
(as well as other) content models.</p>=0D <p>Note that milestones are =
constrained with unique properties throughout the <body>. The =
relevant content models also provide that either a container or =
milestone version of certain elements, such as <verse>, =
<line>, <p>, and <chapter> can be chosen in =
appropriate contexts.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:complexType>=0D <xs:sequence>=0D <xs:group =
ref=3D"titleGroup" minOccurs=3D"0"/>=0D <xs:element ref=3D"div" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D <xs:attribute name=3D"TEIform" =
fixed=3D"body"/>=0D </xs:complexType>=0D </xs:element>=0D <xs:element =
name=3D"back">=0D <xs:complexType>=0D <xs:sequence>=0D <xs:group =
ref=3D"titleGroup"/>=0D <xs:element ref=3D"div" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D <xs:attribute name=3D"TEIform" =
fixed=3D"back"/>=0D </xs:complexType>=0D </xs:element>=0D <xs:group =
name=3D"annotationGroup">=0D <xs:annotation>=0D <xs:documentation>=0D =
<p>A group for common annotations recorded on a text.</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:sequence>=0D =
<xs:element ref=3D"divineName" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"foreign" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"inscription" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"name" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"note" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"q" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"reference" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"speaker" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"w" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
</xs:group>=0D <xs:group name=3D"milestones">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>Milestones are used to mark the traditional =
book, chapter, verse divisions, which are the most likely to cross other =
divisions commonly used in translations. In addition to these =
milestones, there is a generic milestone marker for cases not forseen by =
the encoding team. Note that the refStart and refEnd milestones are the =
generic form of the milestone marker.</p>=0D <p>The attributes of the =
milestone markers require some comment for proper use. Note that all =
elements may, but are not required to bear an ID attribute. The ID =
attribute answers the question of "whoami?" and not =
"where am I pointing?" That is an important distinction since =
milestones will most often be used to indicate a division in the text =
that is composed of other parts of the text. For example, to mark =
Matthew:1.2-6a (Abraham to David) it could be marked as <refStart =
id=3D"div.003" reference=3D"Matt.1.2" =
referenceEnd=3D"Matt.1.6a" type=3D"geneaology" /> =
text of Matthew here <refEnd IDREF=3D"div.003" Note that =
the ID on refStart was not required, but in order for the IDREF on =
refStop to validate, it must be used. This is a good way to catch common =
typing mistakes. The reference and referenceEnd point to the portions of =
the text that the milestone "surrounds" in a very =
non-technical sense.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:choice>=0D <xs:element name=3D"bookStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"bookEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"chapterStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"chapterEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"lineStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"lineEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"qStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"qEnd">=0D <xs:complexType>=0D =
<xs:attributeGroup ref=3D"endMilestoneAttributes"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"seg">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"segEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"speechStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"speechEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"verseStart">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"startMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"verseEnd">=0D =
<xs:complexType>=0D <xs:attributeGroup =
ref=3D"endMilestoneAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D </xs:choice>=0D </xs:group>=0D <xs:group =
name=3D"titleGroup">=0D <xs:annotation>=0D <xs:documentation>=0D =
<p>The titleGroup provides title and titlePart models both for front =
matter (as traditionally understood in the sense of title pages) as well =
as heading such as appear in other divisions of the text. The use of =
head and similar mechanisms seems to complicate the semantics of the =
markup with no real benefit to the user.Structurally, titles interrupt =
the flow of the text for some purpose, such as the beginning of a new =
theme, section, chapter or other division of the text.</p>=0D <p>The =
<title> mixed attribute is set to true and <titlePart> =
element is optional to allow for use of the <title> element in =
cases where <titlePart> is not desired. Thus the average user can =
simply input the title of a work without the added complexity of =
specifying parts of the title. The <titlePart> element is not =
recursive, in other words it cannot occur within =
<titlePart>.</p>=0D </xs:documentation>=0D </xs:annotation>=0D =
<xs:sequence>=0D <xs:element ref=3D"title" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D </xs:group>=0D <xs:group =
name=3D"translationGroup">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>A group that gathers claims made about a =
text in the process of translation.</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:sequence>=0D <xs:element ref=3D"ampRead" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"changedTense" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"ntProphecy" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"otPassage" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"supplied" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D </xs:group>=0D <xs:element name=3D"ampRead">=0D =
<xs:complexType mixed=3D"true">=0D <xs:sequence minOccurs=3D"0" =
maxOccurs=3D"unbounded">=0D <xs:element ref=3D"note" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"author">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>The author element has been defined globally =
to allow its use in a number of contexts. Users should note that the =
role of an author, i.e,, as editor, translator, etc., is =
required.</p>=0D </xs:documentation>=0D </xs:annotation>=0D =
<xs:complexType>=0D <xs:choice>=0D <xs:element =
ref=3D"persName"/>=0D <xs:element ref=3D"orgName"/>=0D =
</xs:choice>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
<xs:attribute name=3D"role" type=3D"role" use=3D"required"/>=0D =
<xs:attribute name=3D"TEIform" fixed=3D"author"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element =
name=3D"changedTense">=0D <xs:complexType>=0D <xs:sequence =
minOccurs=3D"0" maxOccurs=3D"unbounded">=0D <xs:element ref=3D"note" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"copyright">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>Not entirely happy with the content model =
requiring <p> for this element. Should I declare it mixed =3D yes? =
and make the <p> element optional?</p>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:complexType>=0D <xs:sequence>=0D =
<xs:element ref=3D"work"/>=0D <xs:element ref=3D"copyrightDate"/>=0D =
<xs:element ref=3D"holder"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"status" type=3D"xs:string" use=3D"optional"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"availability"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"copyrightDate">=0D =
<xs:complexType>=0D <xs:sequence>=0D <xs:element ref=3D"year" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"date">=0D <xs:complexType>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D <xs:attribute name=3D"calendar" =
type=3D"calendar" use=3D"optional" default=3D"ISO"/>=0D <xs:attribute =
name=3D"value" use=3D"optional"/>=0D <xs:attribute name=3D"TEIform" =
fixed=3D"date"/>=0D </xs:complexType>=0D </xs:element>=0D <xs:element =
name=3D"div">=0D <xs:complexType>=0D <xs:sequence =
maxOccurs=3D"unbounded">=0D <xs:group ref=3D"titleGroup" =
minOccurs=3D"0"/>=0D <xs:group ref=3D"milestones" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"figure" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"div" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"lineGroup" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"list" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"note" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"p" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"reference" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attribute =
name=3D"divTitle" type=3D"xs:string" use=3D"optional"/>=0D =
<xs:attribute name=3D"type" type=3D"divType" use=3D"optional"/>=0D =
<xs:attribute name=3D"TEIform" fixed=3D"div"/>=0D <xs:attribute =
name=3D"reference" type=3D"ReferenceType" use=3D"optional"/>=0D =
<xs:attribute name=3D"referenceEnd" type=3D"ReferenceType" =
use=3D"optional"/>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:simpleType name=3D"divType">=0D <xs:union memberTypes=3D"divsOSIS =
attributeExtension"/>=0D </xs:simpleType>=0D <xs:element =
name=3D"divineName">=0D <xs:complexType>=0D <xs:simpleContent>=0D =
<xs:extension base=3D"xs:string">=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"figure">=0D <xs:complexType>=0D <xs:sequence>=0D =
<xs:element name=3D"caption" minOccurs=3D"0"/>=0D </xs:sequence>=0D =
<xs:attribute name=3D"src" type=3D"xs:string" use=3D"required"/>=0D =
<xs:attribute name=3D"attachFigure" type=3D"ReferenceType" =
use=3D"optional"/>=0D <xs:attribute name=3D"endAttachFigure" =
type=3D"ReferenceType" use=3D"optional"/>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"foreign">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"foreName">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"foreName"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"head">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"holder">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"inscription">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"item">=0D <xs:complexType mixed=3D"true">=0D =
<xs:sequence maxOccurs=3D"unbounded">=0D <xs:group =
ref=3D"annotationGroup" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:group ref=3D"milestones" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:group ref=3D"translationGroup" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"line">=0D <xs:complexType =
mixed=3D"true">=0D <xs:sequence maxOccurs=3D"unbounded">=0D =
<xs:group ref=3D"annotationGroup" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:group ref=3D"milestones" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:group =
ref=3D"translationGroup" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"lineGroup">=0D =
<xs:complexType>=0D <xs:sequence>=0D <xs:element ref=3D"line" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"list">=0D <xs:complexType>=0D <xs:sequence>=0D =
<xs:element ref=3D"head" minOccurs=3D"0"/>=0D <xs:element =
ref=3D"item" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"name">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p>An element with an attribute simiar to role =
that allows a semi-open attribute for specifying what type of name is =
being recorded in the markup. Examples include person, geographic, etc. =
Note the general format for enumerated values: a list is declared as a =
simpleType and then followed by a union statement combining that list =
with the attributeExtension simpleType which contains a regular =
expression constraining additions to the OSIS enumerated list to begin =
with the string "x-". This allows OSIS to speify a list of =
values and yet allow users to extend that list.</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attribute name=3D"nameType" type=3D"nameType" use=3D"required"/>=0D =
<xs:attribute name=3D"regular" type=3D"xs:string" =
use=3D"optional"/>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:simpleType name=3D"nameType">=0D <xs:union memberTypes=3D"namesOSIS =
attributeExtension"/>=0D </xs:simpleType>=0D <xs:element =
name=3D"note">=0D <xs:annotation>=0D <xs:documentation>=0D <p>Has =
enumerated list of note types and a fairly loose content model. Need to =
add reference mateirals. Should I add the placement attribute?</p>=0D =
</xs:documentation>=0D </xs:annotation>=0D <xs:complexType>=0D =
<xs:sequence maxOccurs=3D"unbounded">=0D <xs:element ref=3D"p" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"notePart" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D <xs:attribute name=3D"startNote" =
type=3D"ReferenceType" use=3D"optional"/>=0D <xs:attribute =
name=3D"stopNote" type=3D"ReferenceType" use=3D"optional"/>=0D =
<xs:attribute name=3D"noteType" type=3D"noteType" use=3D"required"/>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"note"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"notePart">=0D <xs:annotation>=0D =
<xs:documentation>=0D <p/>=0D </xs:documentation>=0D =
</xs:annotation>=0D <xs:complexType mixed=3D"true">=0D <xs:sequence =
minOccurs=3D"0" maxOccurs=3D"unbounded">=0D <xs:element ref=3D"p" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"notePart" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"reference" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D <xs:attribute =
name=3D"type" type=3D"noteTypePart" use=3D"required"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:simpleType =
name=3D"noteTypePart">=0D <xs:union memberTypes=3D"notesOSIS =
attributeExtension"/>=0D </xs:simpleType>=0D <xs:simpleType =
name=3D"noteType">=0D <xs:union memberTypes=3D"notesOSIS =
attributeExtension"/>=0D </xs:simpleType>=0D <xs:element =
name=3D"ntProphecy">=0D <xs:complexType>=0D <xs:sequence =
minOccurs=3D"0" maxOccurs=3D"unbounded">=0D <xs:element ref=3D"note" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attribute name=3D"target" type=3D"xs:string" use=3D"optional"/>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"orgName">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"orgName"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"otPassage">=0D <xs:complexType mixed=3D"true">=0D =
<xs:sequence minOccurs=3D"0" maxOccurs=3D"unbounded">=0D <xs:element =
ref=3D"note" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D <xs:attribute name=3D"target" type=3D"xs:string" =
use=3D"optional"/>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"p">=0D =
<xs:complexType mixed=3D"true">=0D <xs:sequence minOccurs=3D"0" =
maxOccurs=3D"unbounded">=0D <xs:group ref=3D"annotationGroup" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:element =
ref=3D"figure" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
<xs:element ref=3D"lineGroup" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:element ref=3D"list" minOccurs=3D"0" =
maxOccurs=3D"unbounded"/>=0D <xs:group ref=3D"milestones" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D <xs:group =
ref=3D"translationGroup" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"persName">=0D =
<xs:complexType>=0D <xs:sequence>=0D <xs:element ref=3D"foreName" =
minOccurs=3D"0"/>=0D <xs:element ref=3D"surName" minOccurs=3D"0"/>=0D =
</xs:sequence>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
<xs:attribute name=3D"TEIform" fixed=3D"persName"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"publisher">=0D =
<xs:complexType>=0D <xs:simpleContent>=0D <xs:extension =
base=3D"xs:string">=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D <xs:attribute name=3D"TEIform" =
fixed=3D"publisher"/>=0D </xs:extension>=0D </xs:simpleContent>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"pubPlace">=0D =
<xs:complexType>=0D <xs:simpleContent>=0D <xs:extension =
base=3D"xs:string">=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D <xs:attribute name=3D"TEIform" =
fixed=3D"pubPlace"/>=0D </xs:extension>=0D </xs:simpleContent>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"q">=0D =
<xs:complexType mixed=3D"true">=0D <xs:sequence>=0D <xs:element =
ref=3D"q" minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D =
</xs:sequence>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"reference">=0D =
<xs:complexType>=0D <xs:simpleContent>=0D <xs:extension =
base=3D"xs:string">=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"revisionDesc">=0D <xs:complexType>=0D =
<xs:sequence>=0D <xs:element name=3D"p" maxOccurs=3D"unbounded">=0D =
<xs:simpleType>=0D <xs:restriction base=3D"xs:string"/>=0D =
</xs:simpleType>=0D </xs:element>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"revisionDesc"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"speaker">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attribute name=3D"who" type=3D"xs:string"/>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"supplied">=0D <xs:complexType>=0D <xs:sequence =
minOccurs=3D"0" maxOccurs=3D"unbounded">=0D <xs:element ref=3D"note" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"surName">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"surName"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"title">=0D <xs:complexType>=0D <xs:sequence =
maxOccurs=3D"unbounded">=0D <xs:element ref=3D"titlePart"/>=0D =
</xs:sequence>=0D <xs:attributeGroup ref=3D"globalAttributes"/>=0D =
<xs:attribute name=3D"TEIform" fixed=3D"title"/>=0D =
</xs:complexType>=0D </xs:element>=0D <xs:element name=3D"titlePart">=0D =
<xs:complexType mixed=3D"true">=0D <xs:sequence minOccurs=3D"0" =
maxOccurs=3D"unbounded">=0D <xs:group ref=3D"annotationGroup" =
minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0D </xs:sequence>=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D <xs:attribute =
name=3D"TEIform" fixed=3D"title"/>=0D </xs:complexType>=0D =
</xs:element>=0D <xs:element name=3D"w">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attribute name=3D"POS" type=3D"attributeExtension" =
use=3D"optional"/>=0D <xs:attribute name=3D"morph" =
type=3D"attributeExtension" use=3D"optional"/>=0D <xs:attribute =
name=3D"lemma" type=3D"attributeExtension" use=3D"optional"/>=0D =
<xs:attribute name=3D"gloss" type=3D"xs:string" use=3D"optional"/>=0D =
<xs:attribute name=3D"xlit" type=3D"xs:string" use=3D"optional"/>=0D =
<xs:attribute name=3D"TEIform" fixed=3D"w"/>=0D <xs:attributeGroup =
ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"work">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D =
<xs:element name=3D"year">=0D <xs:complexType>=0D =
<xs:simpleContent>=0D <xs:extension base=3D"xs:string">=0D =
<xs:attributeGroup ref=3D"globalAttributes"/>=0D </xs:extension>=0D =
</xs:simpleContent>=0D </xs:complexType>=0D </xs:element>=0D <!-- Start =
of pieces that should be redefined -->=0D <xs:simpleType =
name=3D"ReferenceType">=0D <xs:restriction base=3D"xs:string">=0D =
<xs:pattern value=3D"([^.]+)((.[^.]+){0,})?"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D <xs:simpleType name=3D"OSISID">=0D <xs:restriction =
base=3D"xs:ID">=0D <xs:pattern value=3D"([^.]+)((.[^.]+){0,})?"/>=0D =
</xs:restriction>=0D </xs:simpleType>=0D <xs:simpleType =
name=3D"OSISIDREF">=0D <xs:restriction base=3D"xs:IDREF">=0D =
<xs:pattern value=3D"([^.]+)((.[^.]+){0,})?"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D <xs:simpleType name=3D"OSISIDREFS">=0D <xs:list =
itemType=3D"OSISIDREF"/>=0D </xs:simpleType>=0D <!-- End of things that =
should be defined -->=0D</xs:schema>=0D
------=_NextPart_000_0024_01C1E15C.C6475910
Content-Type: text/xml;
name="OSISScripture_01081.xsd"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="OSISScripture_01081.xsd"
<?xml version=3D"1.0" encoding=3D"UTF-8"?>=0D<xs:schema =
xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" =
elementFormDefault=3D"unqualified">=0D =0D <xs:redefine =
schemaLocation=3D"OSISCore_01081.xsd">=0D <xs:simpleType =
name=3D"ReferenceType">=0D <xs:restriction base=3D"ReferenceType">=0D =
<xs:pattern =
value=3D"((Bible.Prot|Bible.Cath|Bible.NIV|Bible.KJV|Bible.TEV|Bible.NSAB=
|(Bible.([^.]+)))..((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1K=
gs|_2Kgs|_1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek=
|Dan|Hos|Joel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Be=
l|Sus|_1Esd|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps1=
51|Sir|Tob|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Co=
l|_1Thess|_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2Joh=
n|_3John|Jude|Rev))((.[^.]+){0,})?)"/>=0D <xs:pattern =
value=3D"((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1Kgs|_2Kgs|_=
1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek|Dan|Hos|J=
oel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Bel|Sus|_1Es=
d|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps151|Sir|Tob=
|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Col|_1Thess|=
_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2John|_3John|J=
ude|Rev))((.[^.]+){0,})?"/>=0D </xs:restriction>=0D </xs:simpleType>=0D =
<xs:simpleType name=3D"OSISID">=0D <xs:restriction base=3D"OSISID">=0D =
<xs:pattern =
value=3D"((Bible.Prot|Bible.Cath|Bible.NIV|Bible.KJV|Bible.TEV|Bible.NSAB=
|(Bible.([^.]+)))..((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1K=
gs|_2Kgs|_1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek=
|Dan|Hos|Joel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Be=
l|Sus|_1Esd|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps1=
51|Sir|Tob|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Co=
l|_1Thess|_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2Joh=
n|_3John|Jude|Rev))((.[^.]+){0,})?)"/>=0D <xs:pattern =
value=3D"((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1Kgs|_2Kgs|_=
1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek|Dan|Hos|J=
oel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Bel|Sus|_1Es=
d|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps151|Sir|Tob=
|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Col|_1Thess|=
_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2John|_3John|J=
ude|Rev))((.[^.]+){0,})?"/>=0D </xs:restriction>=0D </xs:simpleType>=0D =
<xs:simpleType name=3D"OSISIDREF">=0D <xs:restriction =
base=3D"OSISIDREF">=0D <xs:pattern =
value=3D"((Bible.Prot|Bible.Cath|Bible.NIV|Bible.KJV|Bible.TEV|Bible.NSAB=
|(Bible.([^.]+)))..((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1K=
gs|_2Kgs|_1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek=
|Dan|Hos|Joel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Be=
l|Sus|_1Esd|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps1=
51|Sir|Tob|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Co=
l|_1Thess|_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2Joh=
n|_3John|Jude|Rev))((.[^.]+){0,})?)"/>=0D <xs:pattern =
value=3D"((Gen|Exod|Lev|Num|Deut|Josh|Judg|Ruth|_1Sam|_2Sam|_1Kgs|_2Kgs|_=
1Chr|_2Chr|Ezra|Neh|Esth|Job|Ps|Prov|Eccl|Song|Isa|Jer|Lam|Ezek|Dan|Hos|J=
oel|Amos|Obad|Jonah|Mic|Nah|Hab|Zeph|Hag|Zech|Mal|Bar|PrAzar|Bel|Sus|_1Es=
d|_2Esd|AddEsth|EpJer|Jdt|_1Macc|_2Macc|_3Macc|_4Macc|PrMan|Ps151|Sir|Tob=
|Wis)|(Matt|Mark|Luke|John|Acts|Rom|_1Cor|_2Cor|Gal|Eph|Phil|Col|_1Thess|=
_2Thess|_1Tim|_2Tim|Titus|Phlm|Heb|Jas|_1Pet|_2Pet|_1John|_2John|_3John|J=
ude|Rev))((.[^.]+){0,})?"/>=0D </xs:restriction>=0D =
</xs:simpleType>=0D<!-- <xs:simpleType name=3D"OSISIDREFS">=0D <xs:list =
itemType=3D"OSISIDREF"/>=0D </xs:simpleType>-->=0D =0D </xs:redefine>=0D =
<xs:element name=3D"referenceB" type=3D"OSISID"/> =0D</xs:schema>=0D
------=_NextPart_000_0024_01C1E15C.C6475910--