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-1820) ISO/IEC JTC 1/SC 34N 1078 : DEFECT REPORT NUMBER JP2-29



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

Dennis Hamilton commented on OFFICE-1820:
-----------------------------------------

DISCUSSION REQUIRED

I agree with Andreas, I don't understand what it is we are rejecting.

In conjunction with OFFICE-1818, and related comments there, it seems pretty clear that the undefined interactions and nomenclature identified in these two issues is significant and it isn't possible for the defect report to tell us what the fix should be.  

ALTERNATIVE A:

1. Report these as deferred to future work in the defect-report response.

ALTERNATIVE B:

2. Alternative A supplemented by a decision whether or not we will put in a remedy for ODF 1.2 and then see how to correct across ODF 1.0/IS 26300/ODF 1.1.

3. Find a definitive source on the matter and see how to adapt it in a way that it abstracts for ODF in a way that is consistent with what any implementations actually provide already.  

ALTERNATIVE C:

4. Alternative A, and If there are no implementations, make explicitly implementation-defined in ODF 1.2, and bring in something understandable for ODF-next that deprecates the implementation-defined provisions..  

> ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER 	JP2-29
> ---------------------------------------------------------
>
>                 Key: OFFICE-1820
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1820
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.0 (second edition)
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.0 Errata 02
>
>
> Transcribed from http://www.itscj.ipsj.or.jp/sc34/open/1078.htm
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
> DEFECT REPORT NUMBER 	JP2-29
> QUALIFIER 	clarification required
> REFERENCES IN DOCUMENT 	Clause 15.20
> NATURE OF DEFECT 	This subclause is understandable only if the reader uses OpenOffice and examines the output. Such descriptions are very inappropriate as ISO/IEC standards.
> SOLUTION PROPOSED BY THE SUBMITTER 	Add diagrams and explain "reference points", "measure line", "guides", and so forth.

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