[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-2759) 3.17 Foreign Elementsand Attributes - last two sentences of last paragraph in section - Unclearwhat is meant.
[ http://tools.oasis-open.org/issues/browse/OFFICE-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Durusau updated OFFICE-2759: ------------------------------------ Proposal: 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. BTW, non defined -> non-defined was: 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. I puzzled over this while entering the additional trivial correction. It still seems bizarre to have what I presume to be an ODF defined attribute with an non-ODF defined value, and applying that if it has a default value, but otherwise ignoring the attribute. Either that is simply very poor wording or a hole that an application can drive a truck through as far as interchange with other applications. > 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]