Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)

I know in the original version of ODF they had their own, but I thought they had moved to OPC since it’s pretty much the same thing (as you said, mostly minor details).

At the end of the day, we could probably pick any one of them (except OCF) and be happy with it – assuming the desire for a ZIP-based package.

Leonard

From: Benjamin Young <byoung@bigbluehat.com>
Date: Tuesday, December 11, 2018 at 10:37 AM
To: Leonard Rosenthol <lrosenth@adobe.com>, Ivan Herman <ivan@w3.org>, Avneesh Singh <avneesh.sg@gmail.com>, Brady Duga <duga@google.com>
Cc: Garth Conboy <garth@google.com>, Wendy Reid <wendy.reid@rakuten.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)

Hey Leonard,

I think Apache OpenOffice and LibreOffice use OASIS OpenDocument Format--which differs from OPC...but is still a zip file with an XML file + "stuff":
https://en.wikipedia.org/wiki/OpenDocument#Software<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FOpenDocument%23Software&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=4g%2BUf%2FQodTZ1x1%2BxF843jVcW150E1hkB%2BFVxB5TDA5E%3D&reserved=0>

OpenDocument is also an ISO standard: ISO/IEC 26300

While OPC is ECMA-376 and ISO/IEC 29500-2:2012

However, all of these .zip formats are mostly about moving the "collection" of content to it's destination where it's mostly extracted (often "internally") and then consumed vs. a media format like MPEG4 or M4B (MPEG4 4 Books) which are deliberately media focused.

So far, though, none of these seem to provide an obvious incentive for browser use/consumption. Perhaps we should take a step back and define the expectations for the packaging format?

Cheers,
Benjamin


--

http://bigbluehat.com/<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbigbluehat.com%2F&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=5M06hDq3ZQ1WLcE60hWJsGMt%2B79qk9FaYhn9TCMSNlY%3D&reserved=0>

http://linkedin.com/in/benjaminyoung<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flinkedin.com%2Fin%2Fbenjaminyoung&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=HcvJXaxoDN%2B0lrW41tOoU9pRQ2xmYUncJvkIl6xbUBA%3D&reserved=0>

________________________________
From: Leonard Rosenthol <lrosenth@adobe.com>
Sent: Tuesday, December 11, 2018 10:10 AM
To: Ivan Herman; Avneesh Singh; Brady Duga
Cc: Garth Conboy; Wendy Reid; W3C Publishing Working Group
Subject: Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)


OH, I wasn’t aware of that – but it does make sense (just as EPUB itself is under a CG).



So then to use OCF, we’d need to (just as we are talking about with EPUB 3.2) move it to a WG and REC track along with the changes.  And yes, as @Brady<mailto:duga@google.com> points out, that’s work!!



IF we wanted a ZIP-based container, which doesn’t have the problems of OCF, and is an open standard that we can refer to, then I would recommend OPC (<https://en.wikipedia.org/wiki/Open_Packaging_Conventions >), as I did in the github issue thread…OPC is used by OOXML/OpenOffice as well as ODF (MSOffice) and others.  While being an ISO standard (and thus having Ivan’s paywall concerns), it also exists as an ECMA specification which is freely available.



Leonard



From: Ivan Herman <ivan@w3.org>
Date: Tuesday, December 11, 2018 at 6:52 AM
To: Avneesh Singh <avneesh.sg@gmail.com>
Cc: Brady Duga <duga@google.com>, Leonard Rosenthol <lrosenth@adobe.com>, Garth Conboy <garth@google.com>, Wendy Reid <wendy.reid@rakuten.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)







On 11 Dec 2018, at 05:23, Avneesh Singh <avneesh.sg@gmail.com<mailto:avneesh.sg@gmail.com>> wrote:



The IDPF submissions to W3C are CG reports and do not have status of Standard.

So, if IDPF’s OCF (now under W3C) is developed in CG, would there be some way to refer it in audio WP?



Per process this would be fairly difficult I'm afraid



Ivan







With regards

Avneesh

From: Brady Duga

Sent: Tuesday, December 11, 2018 9:25

To: Leonard Rosenthol

Cc: Garth Conboy ; Reid, Wendy ; W3C Publishing Working Group

Subject: Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)



OCF *is* an ISO spec: https://www.iso.org/standard/63569.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fstandard%2F63569.html&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=JZY1TwQzXtvzhd4pubIh9pQBFxu3l0dhHcuhe%2F8QgxA%3D&reserved=0> (does ISO call them specs?)



It is also an IDPF spec. It is not a W3C recommendation. Normatively referencing an ISO spec, or a W3C recommendation should be pretty easy - just point at them. So if we want to use OCF as is, we are fine - we can point at the ISO version. If we want to make changes this becomes harder. Sure, we can make the changes (after finding editors for the document), hammer OCF into a workable W3C draft, get our two implementations, test suite, vote, etc., assuming we can get buy-in for a new ZIP based rec. None of this is impossible (well, buy in for ZIP might be), but it is not simple. There had been some comments around referencing the ISO version, but I don't see how that will be possible since we need at least one change.



On Mon, Dec 10, 2018 at 6:32 PM Leonard Rosenthol <lrosenth@adobe.com> wrote:

I agree Brady…



But OCF is *NOT* an ISO spec, it’s an IDPF spec (see my link).  And I would assume that IDPF specs are owned nowadays by the W3C – so it’s changing a W3C spec.



Leonard



From: Brady Duga <duga@google.com>
Date: Monday, December 10, 2018 at 5:31 PM
To: Leonard Rosenthol <lrosenth@adobe.com>
Cc: Garth Conboy <garth@google.com>, "Reid, Wendy" <wendy.reid@rakuten.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: OCF for Packaging (was Re: [AudioTF] Agenda 2018-12-14)



But changing one thing in an ISO spec is largely as difficult as changing N things. I think the difficulty is going from N == 0 to N > 0 when it comes to changes.



On Mon, Dec 10, 2018 at 2:27 PM Leonard Rosenthol <lrosenth@adobe.com> wrote:

Sorry I missed the meeting today, but I just reviewed the minutes (where I came up a few times 😊).



As I have previously stated, I also would support a revision to OCF (call it whatever you want) that addresses the primary issue with it today – the removal of the mandatory mimetype file.  That file and it’s requirement to be the first file in the package/archive (<http://www.idpf.org/epub/31/spec/epub-ocf.html#sec-zip-container-mime<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.idpf.org%2Fepub%2F31%2Fspec%2Fepub-ocf.html%23sec-zip-container-mime&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=Gf7ij0vAwgHTeJF31g1zaegPPCNWBG8S76sY9P%2FE0tg%3D&reserved=0>>) is the only thing that you need to change with OCF to make it usable going forward.   And just changing the MUST to a MAY is all you need to do to make it happen – it’s that simple!



Leonard



From: Garth Conboy <garth@google.com>
Date: Monday, December 10, 2018 at 2:42 PM
To: "Reid, Wendy" <wendy.reid@rakuten.com>
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: [AudioTF] Agenda 2018-12-14
Resent-From: <public-publ-wg@w3.org>
Resent-Date: Monday, December 10, 2018 at 2:41 PM



Regrets.  In the air.



But, to paraphrase Trump (without yet have seen minutes for todays call [also in the air]), "I'm a zip/ocf man" (for this initial application).



Best,

   Garth





On Mon, Dec 10, 2018 at 11:18 AM Reid, Wendy <wendy.reid@rakuten.com> wrote:

Correction:

Time and Date Link: https://www.timeanddate.com/worldclock/fixedtime.html?msg=AudioTF&iso=20181214T10&p1=250&ah=1<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timeanddate.com%2Fworldclock%2Ffixedtime.html%3Fmsg%3DAudioTF%26iso%3D20181214T10%26p1%3D250%26ah%3D1&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=Hmsguvb5AYkJQ38Cwa1xkGbrcIIVXyfNC61puhxyeiI%3D&reserved=0>



From: "Reid, Wendy" <wendy.reid@rakuten.com>
Date: Monday, December 10, 2018 at 1:42 PM
To: W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: [AudioTF] Agenda 2018-12-14
Resent-From: <public-publ-wg@w3.org>
Resent-Date: Monday, December 10, 2018 at 1:41 PM



Hello everyone,



The Audiobooks Taskforce (AudioTF) will be meeting Friday, December 14th at 10AM EST [0]. Call details are at the bottom of the email.



Agenda:

  1.  Approve Minutes from last session [1]
  2.  Packaging re: PWG discussion of Dec 10 [2]
  3.  AOB

[0] https://www.timeanddate.com/worldclock/fixedtime.html?msg=AudioTF&iso=20181116T10&p1=250&ah=1<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timeanddate.com%2Fworldclock%2Ffixedtime.html%3Fmsg%3DAudioTF%26iso%3D20181116T10%26p1%3D250%26ah%3D1&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=%2FlS%2Bm%2FXUh4dtPG7Je8RtvvodsfA5%2BG8t7Z%2Fj6T1TPk8%3D&reserved=0>

[1] https://www.w3.org/2018/11/16-pwg-audio-minutes.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F11%2F16-pwg-audio-minutes.html&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552531099&sdata=nST%2BRCWaO3MQ1udE0u3AMXPYhgkoHE8bYFfnyBXB0OU%3D&reserved=0>

[2] https://www.w3.org/2018/12/10-pwg-minutes.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F12%2F10-pwg-minutes.html&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552687347&sdata=A93GbLfu6LK93rr0viuMqmH3Jm6O9Rzdv%2Bv5zejMkBc%3D&reserved=0>



Join from PC, Mac, Linux, iOS or Android: https://rakuten.zoom.us/j/411076785<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frakuten.zoom.us%2Fj%2F411076785&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552687347&sdata=yETbhK409SZMEF1VYzM2ZkT47vUDX35zfnx6yrim6BI%3D&reserved=0>

Telephone:
Dial(a number based on your current location):
US: +1 669 900 6833 or +1 646 876 9923 or +1 877 853 5257 (Toll Free) or +1 855 880 1246 (Toll Free)
Japan: +81 (0) 524 564 439 or +81 (0) 3 4578 1488 or +81 (0) 800 100 5040 (Toll Free)
Meeting ID: 411 076 785
International numbers available: https://zoom.us/u/aejYsJsyQT<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fu%2FaejYsJsyQT&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552687347&sdata=qmuob1m3%2Fwos5cRQk6Ro%2FrBgnvdXiYKDIaq3RYBsafQ%3D&reserved=0>

Cheers,

Wendy





----
Ivan Herman, W3C
Publishing@W3C Technical Lead

Home: http://www.w3.org/People/Ivan/<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FPeople%2FIvan%2F&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552687347&sdata=xivVaE0rny8YxGTWO5eVGQZSpsTe0XESi8xXOELjfOA%3D&reserved=0>
mobile: +31-641044153

ORCID ID: https://orcid.org/0000-0003-0782-2704<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Forcid.org%2F0000-0003-0782-2704&data=02%7C01%7Clrosenth%40adobe.com%7C3c07dcf395734c3828a708d65f7e9127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636801394552687347&sdata=XQbAh2ltNufWWmznsuOqktQf9nwWFtdCCSe26mq3TPc%3D&reserved=0>