[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) [Zip]reference is neither public nor authoritative
I am sure that the link did work in the past. We switched to it in ODF 1.0 2nd edition, because the one we used in ODF 1.0, which did to the very best of my knowledge work when we published ODF 1.0, also failed one day. At least for ODF 1.2, I propose that we switch to Appnote 6.2.0 as proposed by Dennis. This is the version that OOXML uses as well. Best regards Michael On 10/12/09 17:47, robert_weir@us.ibm.com wrote: > Not sure I even caught the bad link on Zip at that point. Maybe the link > was working then? In any case, we should do a comprehensive review of our > all of references, not just whether the reference still exists, but > whether it has been superseded, whether we are citing it correctly (I > found one spelling error in an author's name) whether the citation form is > correct, etc. W > > For the specific case of the Zip reference, the good thing is ISO staff is > supposed to take all non-ISO external references and archive a copy of > them prior to publication. So if anyone needed to verify the Zip format > referenced in the published ISO/IEC 26300 they could. > > It might be a good practice for us as well, to keep an archived copy of > all all non-ISO, non-OASIS, non-W3C, non-IETF referenced specifications. > > -Rob > > > "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 10/12/2009 > 11:20:28 AM: >> Subject: >> >> RE: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) [Zip] >> reference is neither public nor authoritative >> >> I was on the committee at the time. I even discussed the review with > you. >> My search for past material on [Zip] in particular failed to find this >> though. Sorry. >> >> Thanks for the link. I'll check into that. >> >> - Dennis >> >> -----Original Message----- >> From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] >> http://lists.oasis-open.org/archives/office/200910/msg00103.html >> Sent: Monday, October 12, 2009 06:37 >> To: ODF TC List >> Subject: RE: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) > [Zip] >> reference is neither public nor authoritative >> >> This might have been before you joined the TC (it certainly was before > we >> started using JIRA) but I did a complete review of our references and >> posted my recommendations here: >> >> http://markmail.org/message/s7orbvfya2ztq7wv >> >> And details uploaded here: >> >> http://www.oasis-open.org/committees/document.php?document_id=31301 >> >> >> -Rob >> >> "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 10/11/2009 >> 07:21:25 PM: >> >> >>> Subject: >>> >>> RE: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) [Zip] >>> reference is neither public nor authoritative >>> >>> Rob, >>> >>> I only did this because I had this one in my job jar to deal with >>> for Part 3 already and I just hadn't put up the JIRA issue yet. >>> This topic has come up in discussions, just didn't make it into a >>> JIRA issue. It was at the top of my list of pending Part 3 items. >>> >>> I'll watch for any duplicates that arise out of the automated >>> procedure. No worries. >>> >>> - Dennis >>> >>> -----Original Message----- >>> From: OASIS Issues Tracker [ > mailto:workgroup_mailer@lists.oasis-open.org >> ] >>> Sent: Sunday, October 11, 2009 14:28 >>> To: office@lists.oasis-open.org >>> Subject: [office] [OASIS Issue Tracker] Commented: (OFFICE-2082) >>> [Zip] reference is neither public nor authoritative >>> >>> >>> [ http://tools.oasis-open.org/issues/browse/OFFICE-2082? >>> page=com.atlassian.jira.plugin.system.issuetabpanels:comment- >>> tabpanel&focusedCommentId=16257#action_16257 ] >>> >>> Robert Weir commented on OFFICE-2082: >>> -------------------------------------- >>> >>> Dennis, in the future please don't open new JIRA issues >>> corresponding to public comments. I have automation that will >>> automatically do this for all public comments, and I have no easy >>> ability to tell which public comments have had JIRA issues opened by >>> TC members and which ones have not. So when we both do the >>> transfer, we will end up with duplicate issues in JIRA pointing to >>> the same public comment. It also may give the wrong message to the >>> other people who submit public comments and do not see an immediate >>> personal message saying that we've opened a JIRA issue for them. >>> Better to Just wait for the batch transfer of comments to occur like >>> we've done for the other 1500 or so public comments. Nothing gets >>> lost that way. and nothing gets duplicated. Thanks! >>> >>> [ ... ] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- Michael Brauer, Technical Architect Software Engineering StarOffice/OpenOffice.org Sun Microsystems GmbH Nagelsweg 55 D-20097 Hamburg, Germany michael.brauer@sun.com http://sun.com/staroffice +49 40 23646 500 http://blogs.sun.com/GullFOSS Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Haering
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]