[OASIS Issue Tracker] Commented: (OFFICE-3850) Clause 1.6 of ISO/IEC 26300

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35478#action_35478 ] 

Patrick Durusau commented on OFFICE-3850:
-----------------------------------------

This was added in our second DCOR for ISO/IEC 26300:

*****
ODF processing of whitespace characters is in conformance with the provisions of [XML 1.0].

In addition, ODF processors shall ignore all element children ([RNG] section 5, Data  Model) of ODF-defined elements that are strings consisting entirely of whitespace  characters and which do not satisfy a pattern of the ODF schema definition for the  element.

Any special treatment of additional occurrences of whitespace characters depends on the specific definitions of individual ODF elements, attributes, and their datatypes. See, in particular, section 5.1.1."
*****

The point about "ODF Processing" should be accepted. Replace "In addition, ODF processors" with "ODF processing". A non-material change as it doesn't change any previous requirement. Suggest we do this as errata.

If the term "element children" is unclear then so is RNG section 5, Data Model, which says in part:

*****
an ordered sequence of zero or more children; each child is either an element or a non-empty string; the sequence never contains two consecutive strings
*****

The phrase : "do not satisfy a pattern" cannot be read in isolation from the rest of the clause. 

The relevant part reads: "...do not satisfy a pattern of the ODF schema definition for the  element." 

We have element children *of* defined ODF elements that are 1) strings consisting entirely of whitespace  characters *and* ...do not satisfy a pattern of the ODF schema definition for the  element." 

That is to say some schema definition may define a string of entirely whitespace characters and in such cases, follow the schema definition.

I fail to see what is unclear about this clause. 

BTW, on the general point of "it is not the job of ISO/IEC 26300 to change whitespace handling behaviour of XML processors", ISO/IEC 26300 does not. 

What ISO/IEC 26300 does do is prescribe the processing of the XML which it itself defines. XML in the context of ISO/IEC 26300 is an interchange format, not a processing model. Applications are free to use any processing model they choose, so long as they obey the rules for processing the format defined by ISO/IEC 26300.

I suggest we accept the change of: Replace "In addition, ODF processors" with "ODF processing". (purely editorial, not a substantive change) and decline the invitation to make further changes.



> Clause 1.6 of ISO/IEC 26300
> ---------------------------
>
>                 Key: OFFICE-3850
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3850
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema)
>    Affects Versions: ODF 1.0 (second edition)
>            Reporter: Patrick Durusau
>            Priority: Minor
>
> There are three problems. First, "ODF processor" is used but never defined. Second, "element children" is unclear. Third, "do not satisfy a pattern" is undefined. The last one cannot be addressed by a simple editorial change.
> Submitted as part of SC34N1979 by Japan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira