W3C

– DRAFT –
Publishing Community Group

14 September 2022

Attendees

Present
gpellegrino, JF, John Roque, liisamk, Naomi, p_belfanti, rickj, wendyreid, wolfgang, zheng_xu
Regrets
-
Chair
-
Scribe
wolfgang, zheng_xu

Meeting minutes

<zheng_xu> list agenda

<zheng_xu> hahaha

<zheng_xu> just playing around with Zakim :)

<zheng_xu> looks like this is still working https://www.w3.org/2001/12/zakim-irc-bot.html

<zheng_xu> and https://www.w3.org/2002/03/RRSAgent

<zheng_xu> please save agenda

zheng: update for TF - announcement for starting Education TF - started to tal about counterfeiting issue which we will continue today

No update this time due to TPAC

Update of Ed TF work

p_belfanti: kicked off ED a few weeks ago
… started to gather use cases
… also creating form of use case template and will send to generic public
… good start

wolfgang: yes, we also need to category for Ed TF - younger learning, high ed and so on

zheng_xu: next meeting for Ed TF will be hold on next week

<JF> zakin, next item

Discuss about digital publishing counterfeiting https://github.com/w3c/publishingcg/issues/39

<wendyreid> https://twitter.com/shershovitz/status/1567538503621251073

Good job Zakim :)

<JF> this has come around before: https://www.w3.org/2012/08/electronic-books/submissions/webooks2013_submission_41.html

<JF> https://www.ala.org/ala/washoff/contactwo/oitp/emailtutorials/accessibilitya/10.htm

wendyreid: explaining about https://github.com/w3c/publishingcg/issues/39
… some way to explore might be content signature? Share secret between publisher and retailer?

<JF> AND accessibility experts too

<JF> ;-)

wendyreid: still need to explore idea and we need to learn methods and what we can standize

Lars: maybe can think about potential of blockchain. maybe worth of exploring

liisamk: we worked title by title to make sure counterfeit title to be taken down
… but still see this happens in self publishing platform
… this happens a lot after a new book released especially getting into library and epub are exposed to hackers

<Lars> help

<Lars> Never mind ;)

liisamk: sometimes content is modified and maybe even injected a few words at end of last page which is used for marketing purpose

<Lars> How do I put myself on the queue? I forgot :p

use "q+"
… sometimes they add certain character to part of metadata
… retailers are willing to take down counterfeits but no one has good idea about how to prevent it or slow it down yet.
… it's bad for consumer as well since the quality is bad. sometimes image are wrong, css are ripped off so the layout can be terrible.

<Lars> Thanks!

<rickj> * I have to leave to get to the AC meeting at TPAC. Thanks for the good conversations

JF: it's also happened for music. There are multiple problems. Most DRM can not be used since it is bundle to certain distributors
… some DRM are not good for a11y
… recognizing the problem but to find a solution can be tricky

<JF> https://www.w3.org/2012/08/electronic-books/submissions/webooks2013_submission_41.html

<JF> https://www.ala.org/ala/washoff/contactwo/oitp/emailtutorials/accessibilitya/10.htm

<JF> another relevant link: https://www.wired.com/story/ebooks-drm-blind-accessibility-dmca/

Zheng: problem that DRM will be cracked, is not our issue here - which behaviour is more damaging to the industry?

<JF> me +1 to Wendy

<gpellegrino> https://content-blockchain.org/building-blocks/what-is-the-iscc/

<gpellegrino> https://isccdemo.content-blockchain.org/

gpellegrino: comparing two code there is possibility to compare book

<Lars> Thanks Gregorio! I was looking for this. Highly recommended solution

p_belfanti: the issue is probably more about re-distribute the book - counterfeit

<Lars> Reach out to Sebastian Posth (@posth )

<wendyreid> https://www.scenarex.ca/

Lars: There is a company in Canada ^ for blockchain tech on digital books

liisamk: we are not trying to address DRM.

<JF> +1 Liisa

liisamk: the counterfeiting is the real issue
… what we are trying to find is to build some guide to help people maybe in suplychain to understand to recognize counterfeit

Zheng: who could provide a copyright check - publisher or distributor (Amazon, etc.) - tool for similarity check on products handed in
… maybe rough mechanism could help
… would it make sense to have a TF for this issue?

<liisamk> +1 to an anti-counterfeit TF

JF: we need to properly scope the issue, problem and solution

<wendyreid> https://github.com/w3c/publishingcg/issues/39

wendyreid: can we have more detailed info in above github issue
… lightweight platform / solution is recommended
… maybe some signature could help (signature.xml)
… we can explore this way

<JF> +1 to "True and Verified"

liisamk: recommend further discussion in a separate TF
… I can lead the taskforce

Zheng: we can set up a different TF for counterfeiting issue

<johnr> present John Roque

<Zakim> JF, you wanted to remind about Verified Credentials as a possibility

<JF> https://www.w3.org/TR/vc-data-model/

JF: there is some spec ^ in W3C and shared in the github issue. That might help

wendyreid: can check with Ivan about the vc data model
… recommend to reach out more retailer, publisher and other group as well as BISG

Zheng: we can kick off - try to shout out to people outside of PCG - to expand the network makes sense - has not to be a member of PCG - reach out to distirbutors

wolfgang: have a good day and see you next meeting

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

Diagnostics

Succeeded: s/done/down/

Maybe present: Lars, zheng