[osis-core] New Schema!

[Troy A. Griffitts]

> Would there be a problem with using <p> rather than <div> to contain the
> "loose" text and milestones when encoding the cases you described?  (In
> this case <p> acting as a "leaf div" and not really taking on the
> meaning of <p>.  Another alternative being an element identical to <p>
> that you could use instead of <div> and not have to overload the meaning
> of <p>.)  

I don't like the idea of using <p> when, in fact it is not marking a 
paragraph.  As far as using an alternative tag, I still don't see the 
benefits of forcing all text under, say, a <div osisID="Matt.1">Text for 
Matthew chapter 1</div> to be under yet another child.


> The benefit in having fewer possible children of <div> is that style
> sheets would have less to consider

I don't see why.  They still have to consider your proposed new element 
that handles all these things.


> and people trying to encode documents
> will not be confused as to how to best use the schema.
 >
> Also it is possible to encode the following:
> 
> <div>
> 	<milestone_start osisID="Matt.1.1"/>text of verse
> 1<milestone_end osisID="Matt.1.1"/>
> 	<div>
> 		<milestone_start osisID="Matt.1.2"/>part 1 of verse
> 2<div>second part of verse 2<milestone_end osisID="Matt.1.2"/><div>
> 	</div>
> </div>

I'm not sure what your example is trying to point out in regard to our 
conversation.  I would say that BECAUSE "text of verse 1" (in your 
example) IS a child of <div>, it needs to be allowed to have things like 
word level annotation.


> 
> This is probably not the best example, but the point is that it seems
> good keep <div> as a pure container of other elements that contain the
> actual "text".  If we don't like the idea of overloading the meaning of
> <p> for the cases you describe, then maybe we should consider an element
> that acts like <p> but has a different name.
> 
> 
> Todd