<wolfgang> hi, to all of you :)

<wolfgang> * gotomeeting tells me that the organizer is not yet present. Is this OK?

laurent will scribe

<cmaden2> lol

<dauwhe> scribenick: laurentlemeur

<tzviya> http://www.w3.org/2017/07/10-pwg-minutes.html

<scribe> agenda: no comments, approved

tasks distributed during the F2F

<garth> (Lurking from a plane — you all behave! :-)

<tzviya> https://docs.google.com/document/d/1sXM51YzrfahFmkJBL-rt69Jvo0LGbOesleuEgwRWvP0/edit?usp=sharing

early to draft, but draft to be ready in October

Matt has seen no feed back, doesn't need assistance, if people see something, they can add an issue.

tzviya: identifier section - really important matter

@dauwhe, thanks for the tip

<rkwright> and when the person says several lines worth, skip the name and use an ellipses i.e ...

Tzviya: about locators

.Benjamin Young: I'll be happy to help

Yuri: are these locators the same thing as the "old" CFI spec?

Benjamin: the extended concept will be extended.

Yuri: then we'll help, with annotations and Readium in mind

<tzviya> evidentpoint volunteers to contribute to locators and ids

Leonard: we werer thinking about locators in a different way.
... how do you talk about individual resources?
... we didn't came upon sub-resources

Tim: it will go into the github repo, let's discuss there

Tzviya: keep in mind we are separate from DPUB. We don't want to create a new fragment identifier.
... Content model, core media types, nobody assigned. Anybody volunteers? leave for now.
... Document level annotations: isn't it about Web Annotations?

Leonard: it should be much further down.

<bigbluehat> "Document (or Publication) level annotation" == identifier, doesn't it?

BillK: is it at the publication level or document level?

<bigbluehat> Web Annotation covers everything that can be identified.

Leonard: publication

<leonardr> @bigbluehat - maybe :)

<bigbluehat> Just need specs for identification (and location)

<timCole> Web Anno covers how to describe the annotation, not what is done with it...

<leonardr> agreed that once we know what the identifier is, that it may be automatic

Tzviya: metadata

Luc: I can deal with that. Serialization is to be decided; first it is needed to list the necessary metadata

Tzviya: and the minimum set of metadata a publication must support

Hugh McGuire: I volunteer

<hughmcguire> yes we are working on open textbooks / open monographs on the web. boris can work on metadata.

Tzviya: Manifest. There has been extensive discussion already
... Navigation is assigned to Avneesh & George

George: we'll check all aspects of navigation

Tzviya: Sync media, in the a11y taskforce?

Avneesh: join work btw DAniel, Marisa and a11y taskforce

Tzviya: Implementation issues; maybe we'll deal with it as it comes up

Leonard: let's keep it as a placeholder

Tzviya: Personnalization, Mateus

Mateus: I'm planning at starting a call for participation this week. Especially User to reading environment. Less clear on the Authoring aspect. -> Mostly from a publisher perspective.

Leonard: one of the first thing we should discuss is understanding where we drow the line btw the author and user's needs.

Mateus: that makes sense.

<wolfgang> *+1 to @leonard on personalization

<mateus-teixeira> +1

Laurent: Jiminy is working on the Readium baseline CSS, which includes questions like how to get a night mode and GUI personalization working in front of complex CSS in ebooks. This will be usable as input for this taskforce.

Leonard: at Adobe we has an initiative along the same lines

Tzviya: for each section, do you have what you need?

<leonardr> we've been focusing on typographic areas most recently (font size, font choice, colors, etc)

<hughmcguire> how do i get in speaker queue?

<wolfgang> *@hughmcguire: type q+

<hughmcguire> great! thank you.

Tzviya: tools are calls for participation, write a paragraph and send it for review, open a github issue and wait for people to yield at you.

<Murata> +q

<wolfgang> * you're welcome!

Tzviya: you can write in a Google doc if you like

<mattg> draft doc: https://github.com/w3c/wpub/blob/master/index.html

Makoto: what will be the status of the working draft: an agreed paper or a collection of sections not totally agreed?

Tzviya: the published WD should be agreed by consensus.

Avneesh: the a11y TF: we want to come on with a plan

Tzviya: Ivan will be back in August

<tzviya> https://github.com/w3c/wpub/issues/6#issuecomment-314486416

tzviya: last week we went through the issues is github. We have a lot of repetition and some confusion on what we have to accomplish.
... issue 6 is maybe the most important; it is about the abstract model, not the serialization.

<Murata> I hear lots of noise.

<laudrain> Sorry we cannot follow Dave, too much noise

Dave: a WP is a collection of Web resources (very difficult to follow, white noise)

<tzviya> Identifier of WP.

<tzviya> Identification as a WP

<tzviya> List of publication resources.

<tzviya> Reading order.

<tzviya> Metadata.

<tzviya> Nav doc.

<dauwhe> dauwhe: manifest is just information about the publication as a whole

<Murata> Looks sensible.

<hughmcguire> looks sensible to me!

Dave: made some experimenting this morning.

<laudrain> Please Caller 02, mute, too much noise

<Murata> FYI: OOXML allows embedded OOXML via OLE.

<leonardr> @murata - yes and it's hideous!

Luc: seems that some info like metadata may be optional in WP and mandatory in EPUB4. E.g a title. Is it a decision?

Tzviya: decision to be taken in the metadata TF

<leonardr> @dauwhe - IIRC it does not

<leonardr> isrelatedto?

<hughmcguire> isBasedOn

<wolfgang> isVersion/RenditionOf?

Avneesh: navigation, before making it optional, are we sure that we can infer it from the content?

Tzviya: mostly because a single page publication does not need it. But all docs I've seen have a navigation.

<Murata> I don't think that we have to reach consensus about that yet.

BillK: basic question; could the identifier of the WP be the URL or URI or IRI of the manifest?

Tzviya: no answer at the moment

<hughmcguire> 3 mins

<bigbluehat> don't make it anything that has a file extension in it...whatever else you do. Not .html and not .json. The web doesn't have file extensions.

<leonardr> @hadrien - yes, because sniffing is such a good idea :(

Tzviya: we need a decision on this subject. Some people spent time on it already. But we need more manageable github issues

<Hadrien> @leonardr we have media types for that

<leonardr> @hadrien we *should* have them, but the HTML spec doesnt actually care about those either.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/durung/during/
Succeeded: s/publisdher/publisher/
Succeeded: s/Garth/Ivan/
Succeeded: s/URL of the first item in the spine/URL or URI or IRI of the manifest/
Present: tzviya wolfgang Avneesh Luc Ric mattg laurentlemeur dauwhe Vlad Chris_Maden rdeltour Bill_Kasdorf Tim_Cole Deborah_Kaplan Leonard Garth clapierre1 Hadrien mateus-teixeira duga George Benjamin_Young
Found ScribeNick: laurentlemeur
Inferring Scribes: laurentlemeur

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2017Jul/0022.html
Got date from IRC log name: 17 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/17-pwg-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report