[![W3C][1]][2] # Web Annotation Working Group Teleconference ## 08 Oct 2014 [Agenda][3] See also: [IRC log][4] ## Attendees Present Benjamin_Young, Dan_Whaley, Dave_Cramer, Frederick_Hirsch, Kyrce, Kyrce_Swenson, Matt_Haas, Paolo_Ciccarese, Ray_Denenberg, Rob_Sanderson, TimCole, Tim_Cole, [IPcaller], azaroth, bigbluehat, chillag, dauwhe, dwhly, fjh, raphael, rayd, tilgovi, unknown, Jacob_Jett, Randall_Leeds, Jake_Hartnell, Raphael_Troncy Regrets Ivan_Herman, Doug_Schepers, Bill_Kasdorf, Ben_De_Meester, Luc_Moreau, Antonio_Olmo_Titos(tripu), Nick_Stenning, Markus_Gylling Chair Frederick_Hirsch, Rob_Sanderson Scribe rayd ## Contents * [Topics][5] 1. [Scribe Selection, Announcements, Minutes Approval][6] 2. [Extended Data Model Introduction][7] 3. [Other business][8] 4. [Adjourn][9] * [Summary of Action Items][10] * * * Date: 08 October 2014 ### Scribe Selection, Announcements, Minutes Approval can I map my name to bigbluehat? you can map your number to a name using this tool, it can help [https://www.w3.org/1998/12/bridge/info/name.php3][11] awesome. I'll try Randall Leeds ScribeNick: rayd no announcements proposed RESOLUTION: 1 October 2014 minutes approved with Rob added as chair: [http://www.w3.org/2014/10/01-annotation-minutes.html][12] minutes accepted with addition that rob is chair **RESOLUTION: 1 October 2014 minutes approved with Rob added as chair: [http://www.w3.org/2014/10/01-annotation-minutes.html][12]** ### Extended Data Model Introduction Paolo walk through second half data model [http://www.slideshare.net/paolociccarese/open-annotation-specifiers- and-specific-resources-tutorial][13] paolo: used to think about core extensions but now single namespace … specifiers and specific resources slide 2 slide 2 scribe: slide 3 basic anno model. can annotate one or more targets and have one or more bodies ... body and target can be URI ... but most of time want to annotate a fragment of a resource ... uri fragments have limitations so we need to get beyond that ... ... slide 5 fragment of an image ... same for body ... called specific resouce not specific body or target ... slide 7 ... tool to specify selectors slide 8 notes types of specifiers, including styles scribe: highlight with different colors to indicate different things ... URI one way to indicate a fragment, but they don't cover all the use cases ... (URI fragment) Raphael: The Media Fragment URI specification, [http://www.w3.org/TR/media-frags/][14], specifies how to specify simple temporal fragments (using two time codes) and simple spatial fragments (reduced to rectangle bounding box using a top,left position + width and height, aka xywh) scribe: some selectors built in but you can make up your own paolo: spec has a number of selectors that have been generally agreed, could define additional selectors but need interoperability scribe: 10 ... 12 list of builtin selectors ... range, etc. paolo: fragment URIs had some disagreement but other representations had URI issues, but so far seems the best choice scribe: 13 ... 15 fragment selector slide 14, source + fragment, e.g source1#namedSection scribe: 16 breaks URI into source and selector, conforms to media fragment spec ... 17 SVG selector to identify fragment of image ... ... can define squares, circles, ovals fjh, you wanted to ask degree of concern about use of fragment URIs raphael: ok with fragment URIs but also need to be able to create structured data raphael: concerned about validation raphael need to make sure that what you're breaking down is consistent with URI and not clear how ISSUE: How to validate fragment selectors Created ISSUE-7 - How to validate fragment selectors. Please complete additional details at <[http://www.w3.org/annotation/track/issues/7/edit>.][15] raphael: media spec allows simple fragment, rectangles etc. ... need use cases for more complex cases rob: some were offered at CG summary so far: we are ok with media fragment URIs for simple cases of time and box region selection, need use cases to justify more complicated cases yet paolo notes for biology there are more precise annotation selection cases, also for maps paolo: there are plenty of cases ... with SVG seletor can do many of these things Raphael: the question is then whether complex regions (e.g. arbitrary complex polygons) should actually be defined in the hash part of a URI or not paolo: but there are other ways to do it ... maphub uses svg as well as text selector ... they think text selector easier to encode Raphael: maphub uses svg and WKT fjh: is there an issue to record paolo: no, extensibility takes care of it paolo: selectors are important but take care to avoid proliferation tcole: potential for fallbacks in selectors [http://maphub.github.io/][16] paolo: some selectors only specific applications understand but others can fallback paolo: should keep this in mind, can have complicated selector and also simpler one for fallback (eg shaped region or rectangle) rob: sequence of fallbacks rather than random choice azaroth: IDPF had ePub need for this rob: issue 2 in github paolo: 19 text selectors. Issues, copyright for example, counting characters ... text quote v. text position ... 21 a paragraph is annotated and there is text before and after Or if the change is big blocks of text being moved around And the prefix + exact + suffix moves together paolo: 22 text position selector, probably simplest. ... 23 start and end paolo: need to be clear text quote and position depend on document stability. csillag: have implemented both of these, sometimes you might want to use multiple methods at once paolo ... 24 state scribe: keep track of when page was annotated ... time and http request state are recorded ... 25 time state paolo: state was discussed as “setup”, e.g. rotate 3D model so it is same view as when annotated scribe: 27 http request state ... selectors can be used together with state to properly identify target ... 29 style specifiers ... can say annotation is styled by css style ... 31 scope specifier. Might annotate an image w/in a web page paolo: issue raised of whether annotation is for image in context of page, or independent of page. My experience is that context generally matters. scribe: e.g. scope is web page and source is image in the web page paolo: pragmatically annotate the image and then note the scope scribe: 32 annotated telescop image tim: selector state straightforward but how to implement use cases. tcole: concerned about use cases supporting style, scope and maybe should revisit tim: style and scope specifiers need more work rob: hope we don't need to revisit whether there is a requirement for them, but discuss how to implement paolo: tim right, we never reached agreement rob: will generate two issues. **ACTION:** azaroth to generate "status quo" proposal issues for Style and Scope [recorded in [http://www.w3.org/2014/10/08-annotation- minutes.html#action01][17]] Created ACTION-1 - Generate "status quo" proposal issues for style and scope [on Robert Sanderson - due 2014-10-15]. azaroth: please review issues in github and discuss on list ### Other business none ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** azaroth to generate "status quo" proposal issues for Style and Scope [recorded in [http://www.w3.org/2014/10/08-annotation- minutes.html#action01][17]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][18] version 1.135 ([CVS log][19]) $Date: 2009-03-02 03:52:20 $ [1]: http://www.w3.org/Icons/w3c_home [2]: http://www.w3.org/ [3]: http://lists.w3.org/Archives/Public/public- annotation/2014Oct/0016.html [4]: http://www.w3.org/2014/10/08-annotation-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #ActionSummary [11]: https://www.w3.org/1998/12/bridge/info/name.php3 [12]: http://www.w3.org/2014/10/01-annotation-minutes.html [13]: http://www.slideshare.net/paolociccarese/open-annotation-specifiers- and-specific-resources-tutorial [14]: http://www.w3.org/TR/media-frags/ [15]: http://www.w3.org/annotation/track/issues/7/edit>. [16]: http://maphub.github.io/ [17]: http://www.w3.org/2014/10/08-annotation-minutes.html#action01 [18]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [19]: http://dev.w3.org/cvsweb/2002/scribe/