[osis-core] Re: USFM to OSIS mapping: Next Steps (last steps)

[Patrick Durusau]

Ed,

Latest beta attached.

Marker attribute has been added to milestone, q and speech.

Hope you are having a great day!

Patrick

Ed_Abrahamson at sil.org wrote:
> 
> How do I obtain a pre-release copy of OSIS 2.1 schema?  We have 
> assumptions about what has been modified and would like to confirm or 
> clear up any misconceptions to insure that we are all going in the same 
> direction.
> 
> Ed Abrahamson
> Publishing R&D
> SIL International
> 
> 
> 
> 
> *"Steven J. DeRose" <sderose at acm.org>*
> 
> 03/24/2005 11:22 AM
> 
> 	
> To
> 	Todd Tillinghast <todd at snowfallsoftware.com>
> cc
> 	Nathan Miles <nmiles at ubs-icap.org>, Alan_Conner at sil.org, 
> kdeblois at biblesocieties.org, patrick.durusau at sbl-site.org, 
> Jeff_Gayle at sil.org, Jim_Albright at wycliffe.org, "'Bob Chaney'" 
> <bob_chaney at sil.org>, Ed_Abrahamson at sil.org, Jonathan Kew 
> <jonathan_kew at sil.org>, Marie_Titus at sil.org, Michael_Cochran at sil.org
> Subject
> 	Re: USFM to OSIS mapping: Next Steps (last steps)
> 
> 
> 	
> 
> 
> 
> 
> 
>  >Summary of where we are:
>  >A) The mapping between USFM and OSIS is complete with the exception
>  >of the open issue related to \m and \mi.
>  >B) The pre-release OSIS 2.1 schema is complete and includes the
>  >necessary additions to support the current mapping between USFM and
>  >OSIS.
>  >
>  >Patrick and I spoke late last week following a conversation between
>  >Patrick and Steve.  Conclusions from the conversation with Patrick:
>  >
>  >1) Structure to represent continuation of of text is better left out
>  >of OSIS documents because it is already represented with the current
>  >structure and would be contrary to standard XML practice for marking
>  >up textual content.
>  >
>  >2a) From the Ultra XML users guide there seems to be sufficient
>  >support to handle continuation text.  Jonathan Kew attempted to use
>  >Ultra XML but found the documented syntax to not work as expected.
>  >2b) Our suggestion would be to work with Ultra XML regarding how
>  >they would suggest you use their tool to render text that is
>  >interrupted by an element where the interrupting element causes a
>  >block to be generated (perhaps they will: provide suggestions on how
>  >to work around any bugs, fix the bugs, and/or suggest alternative
>  >solutions).
>  >2c) After either finding success with Ultra XML or having exhausted
>  >that avenue come back to the mapping issue at hand.
> 
> There is also the already-available workaround of marking the
> continuations as type="x-continued" or some such, which correctly
> expresses the meaning, and should enable working around UltraXML's
> apparent bug. I'm reluctant to add a value for this to the spec
> directly, unless there is a case for it independent of the UltraXML
> problem. To me, that is because it seems to be a workaround for a
> software bug, rather than an additional phenomenon to account for. I
> remember that Jim would prefer it were added to the spec; might it
> help to add something to the OSIS doc like this (along with a tagging
> example to show how it works):
> 
>  >Some current XML software is known to have difficulty formatting
>  >continued paragraphs correctly. Users of such software are
>  >encouraged to tag continued paragraph portions with
>  >type="x-continued" as a temporary workaround until such bugs are
>  >fixed. The "x-" prefix indicates that this value is not a part of
>  >the OSIS specification, and we hope that as software improves, the
>  >need for it will entirely disappear.
> 
> *Has* anyone talked to UltraXML yet about this issue? If we don't
> make them aware of it, and aware of how important it is, we can't
> expect they'll ever fix it. On the other hand, continued paragraphs
> are not that exotic -- perhaps they have already got a workaround, as
> Todd points out above.
> 
> Does anyone know who the right contact person is at UltraXML? Send me
> their contact info and I will try to get them to escalate the
> problem. If someone (Jonathan, Todd?) can send me the reference to
> their manual where it says this should work, that would sure help,
> too. Having tried that, if I don't see some motion I can try to find
> some additional XML strings to pull to get in at a higher level and
> encourage something to happen.
> 
> Thanks, all! I think we're nearly there!
> 
> steve
> -- 
> 
> Steve DeRose -- http://www.derose.net
> Chair, Bible Technologies Group -- http://www.bibletechnologies.net
> Email: sderose at acm.org  or  steve at derose.net
> 

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau at 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!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osisCore.2.0.9_almost7.xsd
Type: text/xml
Size: 89849 bytes
Desc: not available
Url : http://www.bibletechnologieswg.org/pipermail/osis-core/attachments/20050331/1feecb71/osisCore.2.0.9_almost7-0001.xml