[osis-core] whitespace (again)

[Patrick Durusau]

Todd,

I am going to do this in 1.9.3 (coming later today) and see if it works 
(does here) for those who want to preserve space.

Hope you are having a great day!

Patrick


Todd Tillinghast wrote:
> Patrick,
> 
> I did see the error post.
> 
> Just to be clear let try to repeat what I think you are saying.
> 
> 1) On a single element within the schema we specify a default value of
> "default" for xml:space.  This is likely <osisText>.
> 
> 2) On all other elements there is no default value specified.
> 
> Todd
> 
> 
>>Todd,
>>
>>Did you see my followup post correcting my error on this topic?
>>
>>I now agree that we should say "default" and allow the user to declare
>>it at the appropriate place in their document.
>>
>>Does that work for you?
>>
>>Hope you are having a great day!
>>
>>Patrick
>>
>>Todd Tillinghast wrote:
>>
>>>Patrick,
>>>
>>>I can't imagine any cases where you would want to say <osisText
>>>xml:space="preserve">, because all of the text between <osisText
>>>xml:space="preserve"> and </osisText> would need to be on a single
>>
> line
> 
>>>in the XML document unless you intended to the line break as a part
>>
> of
> 
>>>the text.
>>>
>>>Based on the OSIS 1.9, BCV encoding of the KJV that I created from
>>>Troy's OSIS 1.1 version of the text I found that the
>>>xml:space="preserve" is best placed on the <verse> element.  That
>>
> way
> 
>>>you can have a <chapter> element with each <verse> element on its
>>
> own
> 
>>>line without preserving the line breaks that make the document more
>>>readable.
>>>
>>>Another alternative is to not have a default value of either
>>>xml:space="preserve" or xml:space="default" expressed on any element
>>
> in
> 
>>>our schema and just go with the default of xml:space="default"
>>
> declared
> 
>>>by the XML specification.
>>>
>>>Todd
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>>>Sent: Saturday, October 11, 2003 7:46 PM
>>>>To: osis-core@bibletechnologieswg.org
>>>>Subject: [osis-core] whitespace (again)
>>>>
>>>>Guys,
>>>>
>>>>Hate to even go here but Todd suggested making the value of
>>>
> xml:space
> 
>>>as
>>>
>>>
>>>> "default" on osisTextCT.
>>>>
>>>>Did not consult the spec (mis-read a book I paid for instead) and
>>>
> said
> 
>>>>it would have to be preserve.
>>>>
>>>>Spec reports:
>>>>
>>>>
>>>>
>>>>>The value "default" signals that applications' default white-space
>>>>
>>>>processing modes are acceptable for this element; the value
>>>
> "preserve"
> 
>>>>indicates the intent that applications preserve all the white space.
>>>
>>>This
>>>
>>>
>>>>declared intent is considered to apply to all elements within the
>>>
>>>content
>>>
>>>
>>>>of the element where it is specified, unless overriden with another
>>>>instance of the xml:space attribute.
>>>>
>>>>
>>>>>The root element of any document is considered to have signaled no
>>>>
>>>>intentions as regards application space handling, unless it provides
>>>
> a
> 
>>>>value for this attribute or the attribute is declared with a default
>>>
>>>value.
>>>
>>>
>>>>So, we can go with:
>>>>
>>>><attribute xml:space value="default"> in the schema, and that means
>>>
>>>that
>>>
>>>
>>>>if you don't say anything at osisTextCT, the application can do what
>>>
>>>it
>>>
>>>
>>>>likes.
>>>>
>>>>On the other hand, if you put in the document,
>>>>
>>>><attribute xml:space value="preserve"> in osisTextCT, then any
>>>>application should honor that request (Todd's probably won't ;-) but
>>>>that is another story).
>>>>
>>>>Is there a need to vary preservation of whitespace at the element
>>>
>>>level?
>>>
>>>
>>>>I don't see it as costing us anything and some people will probably
>>>
>>>want
>>>
>>>
>>>>it.
>>>>
>>>>How says anyone interested in the issue? (We need to wait for Todd
>>>
> to
> 
>>>>get back online sometime Monday to have a say as well.)
>>>>
>>>>Hope everyone is having a great day!
>>>>
>>>>Patrick
>>>>
>>>>
>>>>--
>>>>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-core mailing list
>>>>osis-core@bibletechnologieswg.org
>>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>
>>>
>>>_______________________________________________
>>>osis-core mailing list
>>>osis-core@bibletechnologieswg.org
>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>
>>
>>
>>--
>>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-core mailing list
>>osis-core@bibletechnologieswg.org
>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 


-- 
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!