Web Annotation Working Group Teleconference

<scribe> scribe: azaroth

Doug: Work for W3c, based on the east coast, active on an annotation projection with hypothesis and w3c for specs. Staff contact for the group

Ivan Herman: from w3c, in Europe, staff contact and on Digital publishing group

Frederick Hirsch: Co chair for this group

<shepazu> I'm Doug Schepers, shepazu on IRC

<dwhly> shepazu: we could go through irc a > z

aron: WOrking at hypothes.is Contributed to annotator. Based in Berlin

bigbluehat: Ben Young, for hypothesis as developer advocate

Bill Kasdorf: Work for apex, scholarly publishing space, books and magazine. All have annotation has a high priority. Representing BISG with Julie

bjdmeest: Ben De Meester, Belgium Europe

Dave Cramer: Hachette, MA. Involved in CSS and DPIG, adding book like design features to OWP

dinesh?

<dinesh> can you hearme?

<dinesh> ok

Dan Whaley: San francisco, founder of hypothes.is

dinesh: Bangalore India, looking at annotations for handling accessibility

gerben?

Jake Hartnell: Hypothes.is, happy to be here

Jeff Young: OCLC, linked data projects

I think Kevin is a ghost

Kyrce Swanson: Pearson Education, NYC. Internal markup and edupub, annotations keeps coming up.

<Luc> http://lists.w3.org/Archives/Public/public-annotation/2014Sep/0034.html

Luc Moreau: Southampton, UK. Part of SociaM social machines, provenance and annotation. Co-chair of PROV WG

MarkS?

Matt Haas Pearson Education, background in IDPF and EPUB to 3

Paolo: Co chair of the OACG, in Boston, annotopia and domeo, plus harvard MOOC

Ray Denenberg: Library of Congress, annotation in the bibframe model for library metadata

Tim Clark: Mass General, with Paolo. Scientific communication focused on bio-medical research

<stain> am I next?

<stain> stain: Stian Soiland-Reyes working for myGrid, University of Manchester in UK. We make software and social web apps for scientists, using Linked Data and web services. My focus has been on provenance and attribution, semantically annotating research artifacts published as Research Objects, recently joined the Open PHACTS project for drug discovery using Linked Data.

Stian Soiland-Reyes: Work ... that :)

Randall Leeds: Hypothes.is Working on the spec annotation project. Interested in indyweb.

<gerben> Gerben: work with Hypothes.is, interest in semantic web & artificial intelligence, currently studying machine learning in Helsinki (sorry I did not get around to an introduction email)

Tim Cole: UIUC, veteran of OAC and OACG, working on annotation in the context of digital library projects

Bailer: JOANNEUM Research, Austria. Publishing cultural heritage, museum and audio-visual

<wbailer> wbailer: Werner Bailer

<ivan> Werner Bailer

Thanks!

Jem Rayfield: Financial Times, linked data projects, work with the BBC

Not going to go through agenda, will move on to W3C process and work mode

fjh: Not going to go through agenda, will move on to W3C process and work mode
... Probably won't make it through everything, though would like to go through the charter

shepazu: Public working group, so anyone can participate in the public mailing list

<fjh> did quick review of agenda

shepazu: if there's anything confidential, then you should say so so it isn't scribed
... or if it should be truly confidential, eg IP problems, then you can contact Ivan and Doug to try and sort things out
... for the most part all the technical conversation will happen on the public list

<fjh> i suggest you assume everything is public that you say in the group

shepazu: we may have invited experts in the group. Public can't join telcons of f2f meetings. There may be exceptions to that too.
... one of the reasons we want people to join is to get IP commitments. When you join the WG you explicitly say that specifications with consensus, you're giving royalty free grant to any IP
... it applies to everyone, not just members of the WG
... We have a large group, will be looking at different specifications
... We have chairs, Frederick and Rob, Staff contacts, myself and Ivan, and Editors of specifications
... it's a high profile and critical role. Need an editor to have a specification
... usually also the author of a specification
... Two current decisions -- editors can edit the spec and come back to the WG for okay, rather than vice versa
... Can be slow, so editors will edit and WG can raise issues about the changes
... If you don't agree, there's a formal objection process, if there's no consensus. Ultimately it would go to Tim BL.
... They need to be technical. Not on process or other aspect of the WG. If you have an objection to the process.
... [music]
... The chairs are here to make sure that the WG moves forward
... Ivan and Doug are here to help the chairs and make sure W3C process is followed
... There's a huge process document to help avoid conflict and build consensus
... We'll be asking for editors for the specs
... Scribe is another role that we all share
... From week to week we'll have a different scribe
... If you're comfortable scribing, or enjoy it, or otherwise, you're welcome to scribe as much as you like
... Another role is test lead. Test lead will be per spec, and writes tests, but main role is to make sure that every testable asssertion in the spec is known and has a test
... testable assertion is something that a conforming implementation must support

(MUST) ?

scribe: Interoperability is the goal of the testing. Need to run the tests against the user agents, including browsers, servers, tools etc. that conforms to the spec
... if we have a test, we need two passing interoperable implementations
... can't just have to installations of annotator, for example
... In order for it to progress, according to process.
... So test lead has important job of wrangling the tests
... Typically done by a person who can be systematic in going through the spec
... They can delegate to others

fjh: That's basically it.

shepazu: If you're interested in a particular deliverable, we have 5. Unusually different from one another
... Most groups focus on one part of the stack, but we have client and server
... Robust anchoring. We'll try to work with other groups
... Hope we can work with other groups for HTTP API, such as the social web WG
... that'll let clients post generic messages to servers
... Shouldn't invent our own stuff, but instead use other groups' work. Then we don't need to worry about implementations
... Stands a much better chance of being implemented, developers need to learn less, can work with existing tools
... Will be looking for people to step up as editors.
... Rob and Paolo are both experienced editors. Frederick too.
... Dave is editing CSS modules

<stain> Stian as well know it well

shepazu: Lots of liasons that can be done by different people
... Luc also an editor for Provenance

Ivan: A number of people around who know how this works

shepazu: In the wiki we should put together a list of people who have done these roles before
... General procedure for work. Telcos aren't binding, things can be revisited but do need to move forwards
... telcos every week more or less and we'll have periodic face to face meetings
... first f2f is at TPAC, W3C's big meeting in late october
... Please register
... If you're able to come, that would be awesome
... We try to work towards consensus, politeness is crucial, in all venues
... A friendly organization :)
... If something happens, then we'll move to correct it
... Technical arguments are great

<dwhly> shepazu: we'll deal w/ you separately.

shepazu: But have respect
... We'll take people aside and go through expectations for participation

<matt> Is this the F2F meeting? http://www.w3.org/2014/11/TPAC/

shepazu: We are trying to get an annotation system working on W3.org ; hope that the group will experiment with using it for feedback

<dwhly> matt: yes, on tuesday the 28th

<rayd> What time?

<fjh> matt, yes, see Tuesday Web Annotations WG entry

shepazu: Already have one spec that's a good input -- the OACG data model
... Any questions

fjh: We'll use 2014 process
... which we don't need to belabour

shepazu: This is a matter of the workflow of the documents

<dwhly> rayd matt: it's all day on the 28th

shepazu: First Public Working Draft, then subsequent refine

<dwhly> room opens at 08:00

shepazu: then last call
... We can explain more as we go on

fjh: Not going to get through the agenda, so thanks Doug for covering all that

<rayd> FTF all day?

fjh: Would like to schedule next calls
... I suggest that we use the same time slot that we have now until TPAC
... on a weekly basis
... We'll make sure we have a better brdige, does that make sense

+1

<paoloC> +1

<jyoung4> +1

shepazu: Is this time okay for people?

<stain> +1

<rayd> +1

<matt> +1

<Kyrce> +1

<ivan> +1

<Bill_Kasdorf> +1

<fjh> +1 to this slot

+1

<bjdmeest> +1

<Jacob> +1

<aron_> +1

<TimCole> +1

<tilgovi> +1

<Luc> +1

<dinesh> +1

<dwhly> +1

<shepazu> +1

<JakeHart> +1

scribe: bad give -1, if you don't care give 0

fjh: Suggest we don't meet on Oct 22nd, won't be there
... can meet without me if that works

<bigbluehat> +1

<fjh> lets meet weekly at this time, including next week, 1 Oct, 8, 15 oct

<fjh> also can meet 15,22 but I cannot attend

okay for 15th

ivan: Out next week
... fine to go through charter with out team contact

fjh: Need to go through the charter
... if there's questions or concerns with the charter we can go through that then
... Tuesday at TPAC, link in the chat

<dwhly> 1

<TimCole> +1

shepazu: Straw poll of who's coming to the meeting? +1s?

<Luc> -1

<stain> -1

<bigbluehat> +1

<jyoung4> -1

<bjdmeest> +1

<ivan> 0

+1

<fjh> yes to F2F _+1

<JakeHart> +1

<Bill_Kasdorf> -1

<paoloC> 0

<aron_> +1

<wbailer> -1

<Jacob> -1

<rayd> +1 except during AC

<matt> 0

<Kyrce> 0

<dwhly> zz_nickstenn +1 (I think)

shepazu: If it turns out there's more people we have observer seats for space

<rayd> is it all day?

<shepazu> +1

<shepazu> rayd, yes

<ivan> https://www.w3.org/2002/09/wbs/35125/TPAC2014/registrants#WebAnn

ivan: looking at list of people who have registered,

<rayd> I'm coming but haven't registered yet

ivan: a number of people have said they might, hotel will be full, so please take care of it this week
... last chance is October 8th or so

fjh: Suggest we defer the rest of the agenda until next week

ivan: one more thing, certain things on the agenda like tools
... make a list of the questions and hopefully decide by email
... don't need to wait for calls to make decisions
... lets try and get it done

fjh: The more we get done on the list the better

+1

Nothing from me

<Luc> bye

fjh: Anything pressing? No, really appreciate it
... happy to see you all, and talk again next week at this time on the original call number

shepazu: Would be good to introduce yourself on the list so everyone knows who everyone is

fjh: Thanks to Rob for scribing

:)

<dwhly> thanks guys! well done.

Thanks all from me!

I'll be more noisy when not scribing :D

<JakeHart> I can record.

<JakeHart> : )