[osis-core] Valid Regex! globalAttributes, inReferenceAttributes, outReferenceAttributes
Patrick Durusau
osis-core@bibletechnologieswg.org
Wed, 22 May 2002 21:51:51 -0400
--------------090804090808030309010005
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Todd,
Todd Tillinghast wrote:
>Patrick,
>
>I am a little unclear about all of the attributes that are a part of
>globalAttributes, inReferenceAttributes, outReferenceAttributes?
>
>I don't want to assume the intended use and distinction between the
>various options. Can you give a short explanation of the various
>attributes?
>
Sure,
globalAttributes:
<xs:attribute name="ews" type="xs:string" use="optional"/>
Electronic writing system: something Eric suggested so we would have a
hook to place a value for a value representing the writing system we are
using to represent a text. Note the same thing as lang since I could be
using Western ASCII to represent Hebrew as a language using CCAT (a
transcription system).
<xs:attribute name="ID" type="xs:ID" use="optional"/>
What you would expect, just an ID.
<xs:attribute name="lang" type="xs:string" use="optional"/>
The conventional notion of language (as opposed to a writing system).
What most people will use to say, German, French, Greek, etc.
<xs:attribute name="resp" type="xs:string" use="optional"/>
Responsibility: The discussion was about how people could indicate who
authored a note about a text and since markup is a claim about the text
("I think the the speaker is ..." in cases where that is unstated is a
type of responsibility situation) I thought it would be simpler to put
on all the elements. Doesn't cost us anything and allows people to
record who used what element if that is important to them.
<xs:attribute name="type" type="xs:string" use="optional"/>
Holdover from my experience with TEI. Allows the user to declare
whatever typology they care to have for an element and its usage. Note
that we give notes, for example, enumerated types plus the attribute x-
plus value. This actually allows the user to use our noteType or to add
some other type if they are interested.
<xs:attribute name="n" type="xs:string" use="optional"/>
Holder for values that appear in the text, where we might autogenerate.
For example in a list, the text could have 1, 2, 3 or i, ii, iii, and if
that is important to you, n can record how the text numbered a list for
example. The list might not have the 1, 2, 3 in the actual text since
that can be autogenerated for display purposes.
Attributes of work, cite and grain vary for "in" and "out" only in terms
of where they are pointing so I will treat them together for purpose, etc.
work: What we were calling Bible.KJV that sort of thing. Usually would
only appear on the top level element and default down.
cite: The common verse reference, Matt.1.1. Note that we have changed
the datatype so we can avoid the leading digit problem.
grain: Steve suggested the first part of the syntax to be XPointer
offset (which I like) but I added the string alternative since there may
be other grain mechanims in the markup of another document that a user
wishes to use.
Note that I have tried to only specify the syntax for references and not
to validate the actual values placed in the syntax.
My reasoning for that was that our old system seemed (to me) to be
problematic in that it combines two distinct questions: 1. Is this in
valid form (the syntax question) and 2. Is this a valid reference value
(the content question) which both form the answer to 3. Is this a valid
reference (in the sense of yes to #1 and #2)?
I think we know enough to validate #1 in a schema, but the range of
references is too large and unconstrained to answer #2, at least in
terms of the base schema. We could have a separate schema that we
recommend to people that they use that answers the content question. In
other words, have the base schema, which allows them to author with
valid syntax and then (this is partially a return to the scripture
reference model) use a Validate Scripture schema, to validate all their
Scripture references. Actually that might satisfy both needs and do so
rather elegantly since it splits the validation into its actual components.
Then I ship you the document with just the base schema reference but say
that I have validated it with the Scripture Reference schema. Works for
you with just the base schema (syntactically valid) but we also have
content validation via a separate schema.
Any thoughts on the last bit? Thanks for raising the issue again Todd! I
like the separate of validation, whether you intended that result or
not! ;-)
Patrick
inReferenceAttributes:
<xs:attribute name="work" type="osisRef" use="optional"/>
<xs:attribute name="cite" type="osisRef" use="optional"/>
<xs:attribute name="grain" type="osisGrain" use="optional"/>
outReferenceAttributes:
<xs:attribute name="outWork" type="osisRef" use="optional"/>
<xs:attribute name="outCite" type="osisRef" use="optional"/>
<xs:attribute name="outGrain" type="osisGrain" use="optional"/>
>
>Todd
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
>>core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Tuesday, May 21, 2002 12:03 AM
>>To: osis-core
>>Subject: [osis-core] Valid Regex!
>>
>>Guys,
>>
>>Version with valid regex attached. (Dumb syntax error in the
>>
>expression
>
>>but then aren't they all?)
>>
>>Patrick
>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>pdurusau@emory.edu
>>
>
--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu
--------------090804090808030309010005
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html>
<head>
</head>
<body>
Todd,<br>
<br>
<br>
Todd Tillinghast wrote:<br>
<blockquote type="cite" cite="mid:003601c200e0$032a3fd0$8900a8c0@flashlight">
<pre wrap="">Patrick,<br><br>I am a little unclear about all of the attributes that are a part of<br>globalAttributes, inReferenceAttributes, outReferenceAttributes?<br><br>I don't want to assume the intended use and distinction between the<br>various options. Can you give a short explanation of the various<br>attributes?<br></pre>
</blockquote>
Sure,<br>
<br>
globalAttributes:<br>
<br>
<xs:attribute name="ews" type="xs:string" use="optional"/><br>
<br>
Electronic writing system: something Eric suggested so we would have a hook
to place a value for a value representing the writing system we are using
to represent a text. Note the same thing as lang since I could be using Western
ASCII to represent Hebrew as a language using CCAT (a transcription system).<br>
<br>
<xs:attribute name="ID" type="xs:ID" use="optional"/><br>
<br>
What you would expect, just an ID.<br>
<br>
<xs:attribute name="lang" type="xs:string" use="optional"/><br>
<br>
The conventional notion of language (as opposed to a writing system). What
most people will use to say, German, French, Greek, etc.<br>
<br>
<xs:attribute name="resp" type="xs:string" use="optional"/><br>
<br>
Responsibility: The discussion was about how people could indicate who authored
a note about a text and since markup is a claim about the text ("I think
the the speaker is ..." in cases where that is unstated is a type of responsibility
situation) I thought it would be simpler to put on all the elements. Doesn't
cost us anything and allows people to record who used what element if that
is important to them. <br>
<br>
<xs:attribute name="type" type="xs:string" use="optional"/><br>
<br>
Holdover from my experience with TEI. Allows the user to declare whatever
typology they care to have for an element and its usage. Note that we give
notes, for example, enumerated types plus the attribute x- plus value. This
actually allows the user to use our noteType or to add some other type if
they are interested.<br>
<br>
<xs:attribute name="n" type="xs:string" use="optional"/><br>
<br>
Holder for values that appear in the text, where we might autogenerate. For
example in a list, the text could have 1, 2, 3 or i, ii, iii, and if that
is important to you, n can record how the text numbered a list for example.
The list might not have the 1, 2, 3 in the actual text since that can be
autogenerated for display purposes.<br>
<br>
Attributes of work, cite and grain vary for "in" and "out" only in terms
of where they are pointing so I will treat them together for purpose, etc.<br>
<br>
work: What we were calling Bible.KJV that sort of thing. Usually would only
appear on the top level element and default down. <br>
<br>
cite: The common verse reference, Matt.1.1. Note that we have changed the
datatype so we can avoid the leading digit problem.<br>
<br>
grain: Steve suggested the first part of the syntax to be XPointer offset
(which I like) but I added the string alternative since there may be other
grain mechanims in the markup of another document that a user wishes to use.<br>
<br>
Note that I have tried to only specify the syntax for references and not
to validate the actual values placed in the syntax. <br>
<br>
My reasoning for that was that our old system seemed (to me) to be problematic
in that it combines two distinct questions: 1. Is this in valid form (the
syntax question) and 2. Is this a valid reference value (the content question)
which both form the answer to 3. Is this a valid reference (in the sense
of yes to #1 and #2)?<br>
<br>
I think we know enough to validate #1 in a schema, but the range of references
is too large and unconstrained to answer #2, at least in terms of the base
schema. We could have a separate schema that we recommend to people that
they use that answers the content question. In other words, have the base
schema, which allows them to author with valid syntax and then (this is partially
a return to the scripture reference model) use a Validate Scripture schema,
to validate all their Scripture references. Actually that might satisfy both
needs and do so rather elegantly since it splits the validation into its
actual components. <br>
<br>
Then I ship you the document with just the base schema reference but say
that I have validated it with the Scripture Reference schema. Works for you
with just the base schema (syntactically valid) but we also have content
validation via a separate schema.<br>
<br>
Any thoughts on the last bit? Thanks for raising the issue again Todd! I
like the separate of validation, whether you intended that result or not!
;-)<br>
<br>
Patrick<br>
<br>
<br>
<br>
inReferenceAttributes:<br>
<br>
<xs:attribute name="work" type="osisRef" use="optional"/><br>
<xs:attribute name="cite" type="osisRef" use="optional"/><br>
<xs:attribute name="grain" type="osisGrain" use="optional"/><br>
<br>
outReferenceAttributes:<br>
<br>
<xs:attribute name="outWork" type="osisRef" use="optional"/><br>
<xs:attribute name="outCite" type="osisRef" use="optional"/><br>
<xs:attribute name="outGrain" type="osisGrain" use="optional"/><br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite" cite="mid:003601c200e0$032a3fd0$8900a8c0@flashlight">
<pre wrap=""><br>Todd<br><br></pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----<br>From: <a class="moz-txt-link-abbreviated" href="mailto:owner-osis-core@bibletechnologieswg.org">owner-osis-core@bibletechnologieswg.org</a> [<a class="moz-txt-link-freetext" href="mailto:owner-osis">mailto:owner-osis</a>-<br><a class="moz-txt-link-abbreviated" href="mailto:core@bibletechnologieswg.org">core@bibletechnologieswg.org</a>] On Behalf Of Patrick Durusau<br>Sent: Tuesday, May 21, 2002 12:03 AM<br>To: osis-core<br>Subject: [osis-core] Valid Regex!<br><br>Guys,<br><br>Version with valid regex attached. (Dumb syntax error in the<br></pre>
</blockquote>
<pre wrap=""><!---->expression<br></pre>
<blockquote type="cite">
<pre wrap="">but then aren't they all?)<br><br>Patrick<br><br>--<br>Patrick Durusau<br>Director of Research and Development<br>Society of Biblical Literature<br><a class="moz-txt-link-abbreviated" href="mailto:pdurusau@emory.edu">pdurusau@emory.edu</a><br></pre>
</blockquote>
<pre wrap=""><!----><br></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
<a class="moz-txt-link-abbreviated" href="mailto:pdurusau@emory.edu">pdurusau@emory.edu</a></pre>
<br>
</body>
</html>
--------------090804090808030309010005--