See also: IRC log
<TimCole> Correct minutes url:
<TimCole> https://www.w3.org/2017/01/06-annotation-minutes.html
PROPOSED RESOLUTION: Minutes of the previous call are approved: https://www.w3.org/2017/01/06-annotation-minutes.html
RESOLUTION: Minutes of the previous call are approved: https://www.w3.org/2017/01/06-annotation-minutes.html
<ivan> +1
<ivan> shane, spec ops should vote for the PR! :-)
<ShaneM> ivan: oh - sure.
TimCole: We're now in PR status, until Feb 14th
ivan: Everything went very smoothly, thanks
to everyone
... for PR we need to get some votes. We have 4 positive votes, plus one
abstention
... Need to get votes from the participants of the group
... esp Illinois, Getty, etc
TimCole: Should we contact Los Alamos
ivan: LANL has already voted :)
... Rob can ask Stanford, Ben can you ask your AC Rep?
... Takeshi, how complicated to get to your AC rep?
takeshi: I have a meeting next week
ivan: Also we have hypothes.is vote in already. Who else was in the group and active?
Rob: Library of Congress -- I can email Ray
ivan: Paolo isn't there any more, but could ask Tim from Harvard
Rob: Will do
Ivan: I've asked my institute in Amsterdam
TimCole: Oxford and Edinburgh in the UK
ivan: Benjamin, do you still have the
contact for MS?
... any member can vote, and they were interested in Berlin
bigbluehat: Also talked to someone at Lisbon, so will get in touch with them
ivan: Want to raise at publication IG, will
take care of those folks
... So with those, we have 10 or more which is fine. No problem unless
someone objects, of course
... something we discussed on the call was preparing for a larger blog
announcement. One or both of the chairs should do it.
... a one pager about what the specs do, why, and so on
TimCole: Are there any recent examples?
ivan: hmm ... I will have a look. I think
CSV did something similar
... everything for post TR has been set up
TimCole: How to handle the blog?
Rob: Come up with some bullets first between us, and then one of us drafts the text?
TimCole: OK
... any other comments or questions about PR?
See: http://w3c.github.io/web-annotation/selector-note/
TimCole: Already had three comments from Rob
<TimCole> http://lists.w3.org/Archives/Public/public-annotation/2017Jan/0015.html
<TimCole> https://github.com/w3c/web-annotation/pull/397
Rob: (summarises the three comments in the email above)
<ivan> Tim, Rob: https://www.w3.org/blog/2015/12/wai-aria-graphics-module-published/
Ivan: Agreed with the three suggestions, I edited the text and have a PR in which needs review
Rob: Will review after the call
<TimCole> http://w3c.github.io/web-annotation/selector-note/
TimCole: Most recent version of the note
doesn't have the fixes in, but are there any other concerns with the
note?
... Paolo, are you in a position to ask MGH to vote?
Paolo: Yes, I'll do that
TimCole: If there's no comments or questions, what's the publication process for the note?
ivan: We should publish when we publish the recs, but it's good to have the decision so we can get the short name approved and so on
TimCole: An email call for consensus?
ivan: Yes, and recorded in 2 weeks. I can
get everything ready by then. It's a simple document, so there shouldn't
be any major issue
... we can agree that pub date is with the recs
TimCole: Rob, why don't you do that after
looking at the pull request?
... we don't know publication date for the recs?
Ivan: The deadline is the 14th, but if
there's no issues then it's very short. We then set a date that's okay
with the webmaster.
... there's no changes on the doc, so should be no problem with the
checkers
TimCole: The recs don't reference the note, so still won't at TR. We'll need to update the references between them, and for the note
PaoloCiccarese: Short question ... wondering
if any of the big players manifested any interest? Google, Apple?
... in the work in general, the specs in particular
ivan: Had some interesting discussions with
MS, but that was all.
... they didn't join the group, but it was late in the process at that
stage
... publishers are interested, a different crowd. Wiley is using it
internally. Other EPub reader companies are interested
... Bluefire, readium consortium is planning to implement it.
... Rob, you're in the best position to get a vote from Europeana
Rob: I can do that
TimCole: Hasn't been a post of the PR status to the CG. Might be players there that have AC reps that could vote
Rob: Sounds good to me
Paolo: Can we use the message for the members?
Ivan: Lets not forward it directly
Paolo: I'll write something and have Rob and Tim double check it
TimCole: That seems like a good set. Is anyone involved in Dan's AAK group?
ivan: Yes, and Rob as well. There's a
meeting on the 10th of Feb
... I think most of the members there we will have already caught
TimCole: What else in terms of other work?
ivan: The HTML note?
TimCole: Not sure we have time to go through
it?
... I could put something up next week.
TimCole: As epub is based on HTML, could be something to think about?
ivan: A bit unclear as IDPF and W3C are
considering merging ... lots of discussions still
... idea is that there will be a separate group to maintain the Epub 3
documents, not official w3c docs
... no idea where the annotation part would fit into that
TimCole: Was thinking from a technical sense, don't want to say something that contradicts what was learnt in the process
ivan: Lets see what there is, and we can finesse if there's enough by the time we need it
TimCole: Talked about HTML serialization -- RDFA implementation, embedding the JSON-LD, and use cases that we looked at along the lines of wanting the annotation to travel with the HTML that it annotates
ivan: So in this case epub is a good example
indeed
... I don't know how it was used in practice if at all
TimCole: it was at least talked about. That was the use case to talk about in the note, rather than more exotic ones
ivan: does wiley have any use cases in scholarly publishing?
bigbluehat: our focus now is about editorial
workflows
... would want the option to publish the editorial annotations with the
document, but not necessarily mixed into the document structure or an
island of JSON-LD at the top
... just dump the annotations into the document. A layer to turn off or
on, RDFA is kind of always there
... the more likely case for RDFA or similar would be at publication
time ... non editorial annos, such as footnotes
... not sure if we'd switch to that over <cite>
... maybe for transclusion across documents
ivan: there's a use case there, which is all we're looking for
<csarven> editorial time: https://dokie.li/#figure-dokieli-citation (screencast 42seconds)
ivan: question is if we can refer to Wiley or not
bigbluehat: I think you can
... Wiley Information Model is based on web annotations, amongst others.
As we move towards web first process, these things take shape in
augmenting content
... would want the option to embed
TimCole: the purpose of the note to me is a
marker for experimentation and future work
... points out the options and says that there needs to be more work
bigbluehat: Would want to see it pursued
... JSON-LD doesn't have a dom level marker, which is useful
TimCole: Anything else about the
serialization note?
... github and wiki transitioning to the CG ... will be maintained by
us?
ivan: the w3c wiki will be frozen, but we didn't use it much
TimCole: Does the CG have a wiki?
Rob, Paolo: Yes ... but we didn't use it much
TimCole: And remind me of the errata set up?
ivan: It's up, and automatically bound by an
API and a small script to the issue list
... it's tied to the github, used the mechanism in another WG so quick
to adapt it
TimCole: We do need to move the annotation
tests over to the main GH
... to simplify management. Need to verify with shane that it doesn't
need to still be tied to his site
<ivan> Errata page: https://www.w3.org/annotation/errata/
Ivan: there's a description at the page of what has to be done
<ivan> example in working: https://www.w3.org/2013/csvw/errata/
Ivan: as an example, ^^
... there are a few errata already. That's how it will evolve for our
documents as well
TimCole: Next question when we meet next? Could meet next friday if there's progress on the html note, otherwise 3rd of Feb
ivan: If you think there's enough to discuss next week, happy to do that
TimCole: Okay lets hold next week for the
HTML note
... any other business?
PaoloCiccarese: Sent an email to Tim, and a draft for the CG
Tim, Rob: Thanks Paolo!
bigbluehat: Apache annotator is officially
incubating
... it's mostly tilgovi and I or people that worked on annotator.js
... if there's any interest, would be good to have people sign up
Rob: just client, or also server code?
<TimCole> http://annotator.apache.org/
bigbluehat: Wide open, it's up to the people
who show up
... currently looking at tilgovi's code to produce good web annotation
docs
... highly collaborative
ivan: One thing on that, I have an early
skeleton for the server side to look at the protocol based on mongo
... a way to understand what's happening
... in python, not JS
... haven't touched it for several months, but if interested can give
the code. Not great quality.
... just ping me and I can send it
bigbluehat: the apache repos are git based, so happy to take a look at it
ivan: Don't have the time to do anything
with it in the future
... for that crowd maybe it should be in node.js?
bigbluehat: Apache is agnostic, up to us. My
hope is we have a few implementations that have similar internal APIs
... don't need to declare that JS is the only way to do it
TimCole: Actions ... Rob will do review and
merge PR, then CFC, contact lots of people
... I'll check with Stephen about the UK contacts
... Adjourn