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-1897) draw:engine defects

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

Dennis Hamilton commented on OFFICE-1897:

7. INTEROPERABILITY.  This is probably a case where the allowance of draw:engine values and their interpretation (according to the namespace used) should be identified as implementation defined.   There may need to be an indication in the specific case of draw:engine that no namespace defined by the ODF specification may be used (e.g., only foreign values are provided for at this time.)

> draw:engine defects
> -------------------
>                 Key: OFFICE-1897
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1897
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.0, ODF 1.0 (second edition), ODF 1.1, ODF 1.2
>            Reporter: Dennis Hamilton
> 1. The draw:engine attribute is described as having a value which is "a token with an XML namespace prefix".  The correct nomenclature should be used (e.g., Prefixed Name as in http://www.w3.org/TR/REC-xml-names/#ns-qualnames).   This applies to all of ODF 1.0/IS 26300/ODF1.1 and ODF 1.2 Part 1 cd02.  
> 2. The definition of namespacedToken in ODF 1.2 is useless and should instead make reference to the XML Namespace specification and the definition of Prefixed Name.   This also applies in section 16.1 of ODF 1.0/IS 26300/ODF 1.1.  (The example in earlier editions should be more definite in showing this type as an element or attribute value, not as an element or attribute name of the XML document.)
> 3. In ODF 1.2 Part 1 cd02, there is no longer any description for the default drawing engine behavior when draw:engine is omitted.
> 4. It is also somewhat ambiguous to say that "The drawing engine may get its data either from the draw:data attribute, or it may evaluate the <draw:enhanced-geometry> child element.  I suspect it is more appropriate to say that "The drawing engine may base the custom-shape on information drawn from the optional  draw:data attribute value as well as other attributes and any <draw:enhanced-geometry> element."
> 5. ODF 1.0/IS 26300/ODF 1.1 section 9.5.1 imply that the <draw:enhanced-geometry> element is meaningful only when draw:engine is omitted.  ODF 1.2 Part 1 cd02 makes the same statement.    This statement should be omitted, or modified to deal with the use of this information when draw:engine is and is not specified.
> 6. CONFORMANCE - If there are any differences in the allowance of draw:engine between extended conforming and only-conforming documents, that needs to be introduced in the section on draw:engine.  

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]