[osis-editors] Change for 2.0.1 Requested

[Jim Schaad]

Patrick,

Yes,  you now have the sense of the issue.  My suggestion would be to
keep <transChanges> as non-milestone able, but to allow for a <q>
milestone (and relatives) to be placed inside of it.  I would be leery
of the suggestion of breakin g up the <transChange> as you make it much
harder to determine where to place the brackets (using my scheme to mark
these items) and generally any notes on the <transChange> want to apply
to the entire item.

jim

> -----Original Message-----
> From: Patrick Durusau [mailto:Patrick.Durusau@sbl-site.org] 
> Sent: Tuesday, January 20, 2004 6:07 AM
> To: jimsch@nwlink.com
> Cc: osis-editors@bibletechnologieswg.org
> Subject: Re: [osis-editors] Change for 2.0.1 Requested
> 
> 
> Jim,
> 
> Jim Schaad wrote:
> > Patrick,
> > 
> > I am sorry, but you have missed the point.  Even if I 
> replace <q> with 
> > <speech> I have the same issue.  I cannot milestone a 
> transChange, and 
> > I cannot start a speech (or a quote) inside of a transChange.
> > 
> > Does that make it clear what I am talking about?
> > 
> Maybe. The reason why I suggested using the <q> element was 
> to allow the 
> use of <transChange>.
> 
> What I now understand is that my solution depended upon reading a 
> different structure from the one you are reading in the text 
> to adapt to 
> the markup (rather than the other way around).
> 
> When you say:
> 
>  > I cannot milestone a transChange, and I
>  > cannot start a speech (or a quote) inside of a transChange.
> 
> You do not mean that the <speech> or <q> should be contained 
> inside the 
> <transChange>? Correct?
> 
> In other words, what you are really looking for is for 
> <transChange> to 
> become milestoneable such that you can start a <q> or 
> <speech> inside a 
> <transChange>?
> 
> Taking your earlier example:
> 
> "Some <say, 'He is> John the Baptist,'
> 
> You want:
> 
> <q>Some <transChange sID="0101" type="added"/>say <q>He 
> is<transChange 
> eID="0101"> John the Baptist,</q></q>
> 
> So it is <transChange> being able to cross element boundaries (along 
> with the appropriate content models) that is the issue?
> 
> Sorry, you're right, I missed that from the original post.
> 
> The other question will be, what advantages/disadvantages are 
> there to 
> the following:
> 
> <q>Some <transChange type="added">say</transChange><q><transChange 
> type="added">He is</transChange> John the Baptist</q></q>
> 
> Captures the <transChange> without crossing the boundaries.
> 
> May need to look at where transChange can occur, presently:
> 
> catchWord
> cell
> chapter
> closer
> div
> item
> label
> l
> mentioned
> p
> q
> rdg
> salute
> seg
> speech
> verse
> 
> Children of <transChange>
> 
> a
> abbr
> date
> divineName
> foreign
> hi
> index
> lb
> milestone
> milestoneEnd
> milestoneStart
> name
> note
> reference
> seg
> w
> 
> Apologies for the length of this response. This is something we will 
> need to look at during our next meeting and I wanted to 
> capture as much 
> information as possible on the issue.
> 
> Hope you are having a great day!
> 
> Patrick
> 
> 
> 
> 
> > 
> > jim
> > 
> > 
> >>-----Original Message-----
> >>From: Patrick Durusau [mailto:Patrick.Durusau@sbl-site.org]
> >>Sent: Friday, January 16, 2004 8:39 AM
> >>To: jimsch@nwlink.com
> >>Cc: osis-editors@bibletechnologieswg.org
> >>Subject: Re: [osis-editors] Change for 2.0.1 Requested
> >>
> >>
> >>Jim,
> >>
> >>Jim Schaad wrote:
> >>
> >>>Gentlemen,
> >>>
> >>>I am trying to encode the following text (Matt 16:14):
> >>>
> >>>14They said, "Some <say, 'He is> John the Baptist,' but others,
> >>>'Elijah,' and others, 'Jeremiah or one of the prophets.'"
> >>>
> >>>In this text,  <..> should translate to <transChange type="added">
> >>>This means that I get
> >>>
> >>><verse osisID="Matt.16.14>
> >>>They said, <q>Some <transChange type="added"> say, <q
> >>>sID="Matt.16.14.q.1"/>He is</transChange> <name 
> >>
> >>type="human">John the
> >>
> >>>Baptist</name>,<q eID="Matt.16.14.q.1"/> but others, <q><name
> >>>type="human">Elijah</name>,</q> and others, <q><name 
> >>>type="human">Jeremiah</name> or one of the 
> prophets.</q></q></verse>
> >>>
> >>Based on the NIV, which is what is closer at the moment, I am
> >>not sure 
> >>about your division into quotes. Rather than quotes the 
> portions John 
> >>the Baptist, Elijah, etc. are reports of speech and not 
> >>quotations. The 
> >>overall content of the verse following "They said" is a quotation.
> >>
> >>Thus,
> >>
> >><verse osisID="Matt.16.14>
> >>They said, <q>Some say, <q
> >>sID="Matt.16.14.q.1"/><transChange>He is</transChange> <name 
> >>type="human">John the
> >>Baptist</name>, but others, <name
> >>type="human">Elijah</name>, and others, <name 
> >>type="human">Jeremiah</name> or one of the prophets.</q></verse>
> >>
> >>Quote always allows <transChange> to be a child element.
> >>
> >>Does that help or have I missed the mark?
> >>
> >>Hope you are having a great day!
> >>
> >>Patrick
> >>
> >>
> >>
> >>
> >>
> >>>The problem with this is that <transChange> does not allow a <q>
> >>>element to appear in it.
> >>>
> >>>Jim
> >>>
> >>>
> >>>_______________________________________________
> >>>osis-editors mailing list osis-editors@bibletechnologieswg.org
> >>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-editors
> >>>
> >>
> >>
> >>--
> >>Patrick Durusau
> >>Director of Research and Development
> >>Society of Biblical Literature
> >>Patrick.Durusau@sbl-site.org
> >>Chair, V1 - Text Processing: Office and Publishing Systems 
> >>Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model
> >>
> >>Topic Maps: Human, not artificial, intelligence at work!
> >>
> >>
> > 
> > 
> > _______________________________________________
> > osis-editors mailing list osis-editors@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-editors
> > 
> 
> 
> -- 
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems 
> Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
>