OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Foreign Element question - first question for Monday


Greetings!

Francis Cave spotted a possible issue with foreign elements under 3.17, which reads in part:

*****

If a foreign element has a <text:h> or <text:p> ancestor element, and is a child element of an element for which the OpenDocument schema permits the inclusion of character data, and if the OpenDocument schema permits the inclusion of character data for all *its* ancestors up to the <text:p> or <text:h> element ancestor element, or a <text:ruby-base> ancestor element,

*****

Francis asks:

*****

I don't understand the condition "...and if the OpenDocument schema permits the inclusion of character data for all its ancestors up to...". What does "its" refer to in this context? I presume it refers to "of an element" earlier in the sentence. If that is the case, surely it is sufficient that the parent element of the foreign element permits the inclusion of character data.

*****


I see two different cases and don't know which one is correct.


First case:


<text:p> / other ancestors / <parent:element> (allows character data) / <foreign:element> (content) </foreign:element>


If Francis is correct, then the <parent:element> allowing character data is sufficient.


Second case, which I include because we used "for all of its ancestors":


<text:p> / other ancestors *all of which must allow character data / <parent:element> (allows character data) / <foreign:element> (content) </foreign:element>


Those are two very distinct cases and I lean towards the second based on the current text but:


1) Was that intentional?


2) Does it make any difference in how implementations manage foreign elements?


Since Francis and I are trying to push out the next drafts, I will be asking the TC to take up this question first at our Monday meeting.


Hope everyone is having a great weekend!


Patrick



-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau 

Attachment: signature.asc
Description: OpenPGP digital signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]