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] Issue Comment Edited: (OFFICE-2958) 19.388office:version - 2nd item, list of processing for OpenDocument 1.2 - seedescription



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

Michael Brauer edited comment on OFFICE-2958 at 7/27/10 7:28 AM:
-----------------------------------------------------------------

First of all, I think it is inaccurate to talk about incompatible features. There is to the very best of my knowledge no element or attribute where we in ODF 1.1 specified it means "A", and in ODF 1.2 specify that it means something different "B". There are only elements and attributes where we clarified the behavior, that is specify more precisely than in ODF 1.1 what it means. I would not call this an incompatibility between ODF 1.1 and ODF 1.2. 

We further did not remove any features. That is, we are never in the situation where an ODF 1.1/1.1 has to be mapped to an ODF 1.2 features. All ODF 1.0/1.1 features still exist.

However, regardless how we call this situation, we don't need the 2nd bullet item: The first sentence states:

"Any elements and attributes based on earlier versions of OpenDocument for which the same-named OpenDocument 1.2 features are incompatible need not be accepted."

Consumers may anyway ignore any feature. They therefore would be permitted to ignore incompatible features, if we would have them.

"If accepted, an OpenDocument 1.2-incompatible feature should be cast into an equivalent but OpenDocument 1.2-compatible form. See Appendix H, Changes From Previous Specification Versions (Non-Normative), as well as previous specifications and any approved errata for them."

As said above, there are no elements or attributes in ODF 1.0/1.1 that we removed in ODF 1.2. Therefore, we never have to cast anything to an ODF 1.2 feature. Well, we may get incompatible features in the future. But we don't know anything about them now. Therefore, an ODF 1.2 consumer never can cast these into an ODF 1.2 feature. And where we clarified a feature we already mandate that these features have to follow ODF 1.2 in the introduction.

My suggestion therefore is to remove the the full 2nd item. (The other items could also be removed. See OFFICE-2755).

      was (Author: michael.brauer):
    First of all, I think it is inaccurate to talk about incompatible features. There is to the very best of my knowledge no element or attribute where we in ODF 1.1 specified it means "A", and in ODF 1.2 specify that it means something different "B". There are only elements and attributes where we clarified the behavior, that is specify more precisely when in ODF 1.1 what it means. I would not call this an incompatibility between ODF 1.1 and ODF 1.2. We further did not remove any features. That is, we are never in the situation where an ODF 1.1/1.1 has to be mapped to an ODF 1.2 features. All ODF 1.0/1.1 features still exist.

However, regardless how we call this situation, we don't need the 2nd bullet item: The first sentence states:

"Any elements and attributes based on earlier versions of OpenDocument for which the same-named OpenDocument 1.2 features are incompatible need not be accepted."

Consumers may anyway ignore any feature. They therefore would be permitted to ignore incompatible features, if we would have them.

"If accepted, an OpenDocument 1.2-incompatible feature should be cast into an equivalent but OpenDocument 1.2-compatible form. See Appendix H, Changes From Previous Specification Versions (Non-Normative), as well as previous specifications and any approved errata for them."

As said above, there are no elements or attributes in ODF 1.0/1.1 that we removed in ODF 1.2. Therefore, we never have to cast anything to an ODF 1.2 feature. Well, we may get incompatible features in the future. But we don't know anything about them now. Therefore, an ODF 1.2 consumer never can cast these into an ODF 1.2 feature. And there we clarified a feature we already mandate that these features have to follow ODF 1.2 in the introduction.

My suggestion therefore is to remove the the full 2nd item. (The other items could also be removed. See OFFICE-2755).
  
> 19.388 office:version - 2nd item, list of processing for OpenDocument 1.2 - see description
> -------------------------------------------------------------------------------------------
>
>                 Key: OFFICE-2958
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2958
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
>
>
> Now reads:
> "If accepted, an OpenDocument 1.2-incompatible feature should be cast into an equivalent but OpenDocument 1.2-compatible form. See Appendix H, Changes From Previous Specification Versions (Non-Normative), as well as previous specifications and any approved errata for them."
> I don't look forward to correcting this one but that is way too vague. "...cast into an equivalent but OpenDocument 1.2-compatible form." ???
> Without saying what that equivalent form might be?   

-- 
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]