[osis-core] notes from our discussions on Friday
Harry Plantinga
osis-core@bibletechnologieswg.org
Fri, 29 Aug 2003 15:05:53 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_0000_01C36E3F.0ABBCA20
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_0001_01C36E3F.0AC05E00"
------=_NextPart_001_0001_01C36E3F.0AC05E00
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
These are the raw notes I took during our discussions on Friday.
Enjoy.
-Harry
------=_NextPart_001_0001_01C36E3F.0AC05E00
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'>These are the raw notes I took during our discussions =
on
Friday.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Enjoy.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Harry<o:p></o:p></span></font></p>
</div>
</body>
</html>
------=_NextPart_001_0001_01C36E3F.0AC05E00--
------=_NextPart_000_0000_01C36E3F.0ABBCA20
Content-Type: application/octet-stream;
name="monograph-markup"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="monograph-markup"
*** Best Practices for Monograph Markup ***
Issues
- how to mark TOC entries
- question: is the info at the top or spread through the document
- div types: <div type=3D"originalTOC"> -- at the top, containing =
original TOC.=20
<div type=3D"generatedTOC">
original vs. generated. You can always mark up an original or a =
generated one as a div.
Question: do we suggest some means of specifying one that can be =
auto-generated?
1 <index type=3D"TOC1Entry" title=3D"Chapter 1"/>
2 <div type=3D"chapter" n=3D"1" > [build TOC out of some set of div =
types listed in stylesheet]
<title>Chapter 1</title>
3 <title goesinTOC=3D"true">
preference: 2, if you really want to try to auto-generate, but the =
endpoint
should be a <div> with the toc.=20
=20
- how frequently to use osisIDs: every element?
- use osisID on all paragraphs, e.g., if you want to address all =
paragraphs via a refsystem.
- since they are hierarchical, there is some fallback capability
- try to use standard systems. You might even encode two different =
reference systems.
- how to identify particular types/formats of metadata, e.g. LC call =
number,=20
LC control number (LCCN)
- add <identifier type=3D"LCCall"> for LC call number =
(osisIdentifier of LCCall)
- osisIdentifier of SICI
- how to handle canonical and short-form author names
- osisIdentifier of file-as; use the exact string from the Library =
of Congress canonical form
- use type for file-as, short-form, other usage qualifiers
- use subType to identify data type? (but do we want to suggest this =
as a best practice?
- metadata in the header is in standard format, e.g. ISO for dates =
(with added negative sign? )
maybe use subType for BC
- how to create/define a unique identifier for a work or document
- you can't.=20
- use ISBN
- use PURL
- a library, such as the CCEL, could do it, but not individual =
authors
- how to attach page images
- use <figure type=3D"original">; stylesheet says not to display =
until it's clicked on or whatever.
- how to make a horizontal rule, or some other general physical break
- <milestone type=3D"divider" subType=3D"x-rowOfSevenAsterixes"/>
- what about version control: who made what changes
Initial best practice proposals
Classify matters for discussion by importance
Best practice recommendations
Conformance level recommendations
Level 1
Level 2
Level 3
Level 4
------=_NextPart_000_0000_01C36E3F.0ABBCA20
Content-Type: application/octet-stream;
name="daily-markup"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="daily-markup"
* Best practices for docs organized by time *
Issues -=20
- define one general date scheme (ref. Steve's proposal)
e.g. dateTime:2003.08.29.T13.50.49(GMT-5)
- define a few particular versification schemes
e.g. dayOfYear:03.01
e.g. dayOfWeek:Monday
e.g. dayOfMonth:22
e.g. dayOfLunarMonth:Fullmoon
e.g. dayOfYearABC:A.02.29
e.g. dateTimeBabylonian, dateTimeJewish, dateTimeEgyptian
- name to match our calendar systems
- add a time suffix (a la steve proposal) to each?
- <div type=3D"devotional"> ?
- <div type=3D"lectionary"> ?
- <div type=3D"annals"> ?
- <div type=3D"dated"> ?
- <div type=3D"devotion" osisID=3D"dayOfYear:02.29">
- <div type=3D"meditation" osisID=3D"dayOfYear:02.29">
- <div type=3D"reading" osisID=3D"dayOfYear:02.29">
- <div type=3D"datedReading" osisID=3D"dayOfYear:02.29">
Somebody should go off and write this up.
- How do I say that this is a book of daily devotions?
<work>
...
<type type=3D"OSIS">DailyDevotional</type>
</work>
Types of documents: Bible, Commentary, Monograph, Devotional.Daily,
Devotional.Monthly, Lectionary, Lectionary.TriAnnual, Dictionary, =
Atlas,=20
TopicalReference, Aggregate, Article, Book [of bible], Concordance,
Doctrinal,=20
CBD list: Apologetics, Bibles, Bible Reference/Guide/Study, Biography, =
church/pastoral, commentaries, devotionals, fiction, personal growth,=20
theology
There is a standard set of such categories from some group of =
christian
publishers (Book categories from cpsg.org?)
Types of document structure: Bible, Commentary [anything keyed by =
scripture
reference], Monograph, Time-organized, Dictionary [anything keyed by =
term/def]
<type type=3D"Key">Dictionary</type>
<type type=3D"Genre">Concordance</type> -- use cpsg.org?=20
- deprecate OSIS as a type?
- question: should the type attribute in <type type=3D"xxx"> accept the =
same
attribute values as <div type=3D"xxx"> ?
------=_NextPart_000_0000_01C36E3F.0ABBCA20
Content-Type: application/octet-stream;
name="sermons-markup"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sermons-markup"
* Sermon markup best practices *
Issues
- standard way of marking up a topic or topic passage at the top of
the sermon
<div type="annotant">
- the topic/subject of sections of a sermon
- <div><index type="canonicalSubject" level1="Judgment"/>
- point: <index vocabulary="OSIS" level1="Judgment"/>
- point: <index annotateRef="canonicalSubjects:Christ.Nativity"
level1="Christmas" />
- range: <div annotateRef="canonicalSubjects:Christ.Nativity"/>
- proposal A:
- for now, use <p type="x-venue">
- plan: add more <titlepage> markup later
- proposal B:
- add <titlePage> element that can contain dublin core elements
(repeatable but unordered); and <fig> <milestone> <p>
as an optional first element in a <div>
- <div type="titlepage"> is deprecated
B1. <div type="sermon">
<titlePage>..</titlePage>
<div type="Chapter" n="1"></div>
</div>
B2. <osisText>
<titlePage>..</titlePage>
<div>..</div>
</osisText>
- person speaking [as content]
- <by>by <name type="speaker">C.H. Spurgeon</name></by>
- date given [as content]
- institution where it was delivered (church/location) [as content]
<div type="titlePage">
<title>Christmas in August?</title>
<byline>by <name>C.H. Spurgeon</name></byline>
<p>of</p>
<institution>The Metropolitan Tabernacle</institution>
<venue>Given at Church of the Servant CRC<lb/>
<place>Grand Rapids, MI</place></venue>
<date>August 31, 2003</date>
<div type="titlePage">
<title>Christmas in August?</title>
<title type="x-byline">by <name>C.H. Spurgeon</name></title>
<p>of</p>
<title type="x-institution">The Metropolitan Tabernacle</title>
<title type="x-venue>Given at Church of the Servant CRC</title>
<place>Grand Rapids, MI</place></venue>
<date>August 31, 2003</date>
- sermon collections: should the collection be a work or the
individual sermons (i.e. div, osisText, etc.)
[no comment]
- is there a way to mark an outline that gets projected?
[same answer as table of contents]
- reference to audio
<figure mediaType="application/mp3" type="x-audio" src="tick.mp3" /> --
<figure mediaType="application/smell" type="x-smell" src="tick.sml" /> --
- add mediaType attribute to <figure>
- speaker notes
- <note type="speaker">
[add "speaker" to typelist]
- handouts [separate document]
------=_NextPart_000_0000_01C36E3F.0ABBCA20--