[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Ownership of the xml:space issue?
I think we said you would take over ownership of the xml:space issue once it became an editorial issue? Not trying to dodge work, so if this is not true I can make the updates.
I think four things need to be done based on our ballot, and on the CFDs for 127 and 150 (where the CFD ends and the ballot begins is a little foggy – so I think we should just reference the meeting minutes and ballot results in the tracker – up to you).
1. Remove xml:space from the attribute list of <source> (184.108.40.206) and <target> (220.127.116.11). Also notice there is a constraint on <target> that will need to be edited.
2. Add OPTIONAL xml:space to <xliff> (18.104.22.168), <file> (22.214.171.124), <group>(126.96.36.199), and unit (188.8.131.52).
3. Change the Default value in 184.108.40.206 to (https://lists.oasis-open.org/archives/xliff/201401/msg00016.html):
'preserve'. Note also that the 'default' value is to be interpreted as 'preserve' for the data content (See section
4.7.5 White Spaces).
The default value is inherited from the closest ancestor defining xml:space. If no ancestor specify xml:space the default is 'default'.
And (https://lists.oasis-open.org/archives/xliff/201401/msg00019.html) change the Used in from <source>, <target> to <xliff>, <file>, <group>, <unit>
4. Change 4.7.5
- from “For the elements <sc>, <ec>, <ph> and <data>: The white spaces of their content MUST be preserved in all cases, even if the value for xml:space is set or inherited as default.”
- to “For the element <data>: The white spaces of its content MUST be preserved in all cases, even if the value for xml:space is set or inherited as default.”
Please let me know if you want to make the changes, or if you want me to.