[osis-core] OSIS Candidate Release! - Duplicate mention of <note> and <reference> as children of <div>

[Patrick Durusau]

Todd,

Not really ambituity (at least as traditionally understood in markup) 
just sloppy coding. ;-) Will remove.

Thanks for the catch!

Patrick

Todd Tillinghast wrote:

><note> and <reference> are listed directly as children of <div> and then
>ALSO now children as a part of annotationGroup.  This can cause ambiguity as
>to which instance in intended.  The now extra ones should be removed.
>
>Todd
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org
>>[mailto:owner-osis-core@bibletechnologieswg.org]On Behalf Of Patrick
>>Durusau
>>Sent: Sunday, April 21, 2002 6:08 AM
>>To: osis-core
>>Subject: [osis-core] OSIS Candidate Release!
>>
>>
>>Guys,
>>
>>Attached is the candidate release for OSIS_1.0. I really need to have
>>everyone sign off on this one as we all need time to synch our remarks
>>(and demos) to the final version. (Not to mention that I think I have
>>offended all the volunteers to translate it by not responding while
>>waiting for the schema to settle. I will try to mend fences after we get
>>a wrap to give them.)
>>
>>Note that I have added more Bible names (as per Chris), fixed the
>>content model to allow phrase level markup without a <p> element in
>><div> and gave Troy a synching mechanism that is a list of
>>referenceTypes. Got Troy's note this morning hours before any of the
>>rest of the team would be awake so just entered it. Differs from a gloss
>>in that you could list several other works that you had marked at the
>>word level for the creation of parallel texts. Not how I would do it but
>>it is probably a way to do it with poorly structured text.
>>
>>In any event, I need to start working on some other stuff for Rome so
>>please read and respond, but don't look for a response from me until
>>probably mid-afternoon.
>>
>>I have learned a lot from this effort, one of which is despite being a
>>known anarchist(!) that we need to get better procedures for comments
>>and wider circulation and longer lead times for the next modules.
>>Suggestions, particularly from those of you with a lot of experience in
>>doing this would be greatly appreciated! (I don't think we need a lot of
>>debate on the guidelines, just write something up, we will all look at
>>it for a week or so and then simply choose the best options.)
>>
>>I think this beginning module is something that does not do all that any
>>of us would like, but it is a firm foundation for building an entire
>>array of modules that meet the needs of bible scholars, publishers,
>>readers, and of course, bible programmers!
>>
>>Congratulations on a job well done!
>>
>>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