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: [OASIS Issue Tracker] Commented: (OFFICE-2759) 3.17 ForeignElements and Attributes - last two sentences of last paragraph in section -Unclear what is meant.

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

Dennis Hamilton commented on OFFICE-2759:

I keep wondering what this provision means in the case that the attribute is required for the element that contains it and ignoring it doesn't work.  And of course there is the problem when the default value is the wrong thing.

Although this statement does not extend to Part 3 (I trust), if one of the optional attributes around encryption is not understood and the default is used, I doubt that there will be a successful result, for example.  I am sure there are counterparts of this situation in Part 1.

> 3.17 Foreign Elements and Attributes - last two sentences of last paragraph in section - Unclear what is meant.
> ---------------------------------------------------------------------------------------------------------------
>                 Key: OFFICE-2759
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2759
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>            Reporter: Patrick Durusau
> The entire paragraph reads:
> "OpenDocument consumers should be able to parse and interpret documents that contain attribute values not defined by the OpenDocument schema. If an attribute which has such a non defined value has a default value, then a conforming consumer should assume that the attribute has this value. Otherwise, a conforming consumer should ignore the attribute."
> OK, fix non defined -> non-defined. 
> But, how does "parse and interpret documents that contain attributes values not defined by the OpenDocument schema" square with:
> 1) If attribute has a non-defined value, but has a default, use the default value, or
> 2) Ignore the attribute altogether. 
> Shouldn't this read:
> A conforming consumer that encounters an OpenDocument defined attribute that has a value that is not defined by OpenDocument, then it should:
> 1) If the attribute has a specified default value, use its default value, or
> 2) If the attribute does not have a specified default value, ignore the attribute.

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


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