On Jul 23, 2012, at 11:29 PM, Kahunapule Michael Johnson
<kahunap...@mpj.cx> wrote:
On 07/23/2012 06:26 PM, Chris Little wrote:
<p/> is bad because it uses a container element to represent a non-container,
and it abuses the semantics of the element for purely typographic purposes.
<milestone type="x-p-indent" /> is bad because it employs a private-use
extension to imply the semantics of a container element, again for purely typographic purposes.
At one point, I remember that OSIS was supposed to be able to represent paragraphs as
containers and verse markers as milestones and vice versa. The "vice versa"
there implies the existence of paragraph markers as containers. I fail to see what the
problem would be with consistently using verses as containers and consistently delimiting
paragraphs as milestones. Theoretically, either way can 100% represent the data. Indeed,
the verse-primary model better represents what many Bible study software packages
actually do. I'm not saying you should or should not do that, but that this is
not obviously a bad thing to do. Indeed, it may be a clever thing to do in some
cases, for typographic or other reasons.
No, it was never the case that <p> was milestoneable and it was never
intended that it become so. I was, in any case, referring to the
specific case of its use in our KJV text, where it is used as an anchor
for hanging pilcrows. Sorry I didn't make myself particularly clear for
those not intimately familiar with the corner-cases and controversies of
OSIS encoding.
--Chris
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
