Hello, congratulations on new recommendations. All efforts by WG members and participants are truly appreciated. I've experimented with video annotations using this model (target type "Video"). Simple media fragments, e.g. xywh=percent:40.2,41.6,21.5,16.2&t=7,16 made it possible to pick up a part of video contents. So far, annotations on HTML5 video element [1] and Youtube iframe [2] are implemented. Hope you'll find them interesting. Looking forward to seeing many Web annot applications. cheers, [1] http://www.kanzaki.com/works/2016/pub/image-annotator?u=/works/2017/annot/carmina-burana-ponnelle.json#t=51,82 [2] http://www.kanzaki.com/works/2016/pub/image-annotator?u=/works/2017/annot/youtube-norrington-eroica-mov2.json -- @prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name "KANZAKI Masahide"; :nick "masaka"; :email "mkanzaki@gmail.com"].
And, fyi, an entry put together by Rob and I (with help from others) has been posted to the W3C Blog elaborating on the significance and potential impact of the publication of these Recommendations: https://www.w3.org/blog/2017/02/making-it-easier-to-share-annotations-on-the-web/ Adding my thanks for the efforts and contributions of the members of the Working Group. Don't forget to join the Open Annotation Community Group! -Tim Cole University of Illinois at Urbana-Champaign Co-Chair, W3C Web Annotation Working Group
I have created an EPUB book containing all the annotation recommendations and notes: https://www.w3.org/dpub/ebooks/web-annotations.epub <https://www.w3.org/dpub/ebooks/web-annotations.epub> Ivan ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Dear all, we did it:-) The documents have just been published, see https://www.w3.org/blog/news/archives/6156 <https://www.w3.org/blog/news/archives/6156> Congratulations and thanks to all who have contributed to this! Cheers Ivan ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/416#issuecomment-281169415 using your GitHub account
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/415#issuecomment-281132644 using your GitHub account
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/414#issuecomment-280932823 using your GitHub account
This note confirms that we are NOT having a Web Annotation Working Group teleconference call on Friday. We remain on schedule to publish 3 Recommendations and 2 Notes next Tuesday, 21 February. And since the Working Group's charter expires in 12 days, this means that there will be no further Web Annotation Working Group meetings or conference calls ever! (Unless of course there is a need at some indefinite point in the future to re-charter a new iteration of the Web Annotation Working Group - never say never.) Thanks again to everyone who contributed to the efforts of the Working Group over the last two and a half years. Considerable progress has been made and I look forward to continuing to work with many of you on the W3C Open Annotation Community Group [1], the incubating Apache Annotator project [2], and elsewhere. The Web Annotation GitHub repository [3] will remain available for new issues and Errata for the Documents Published by the Web Annotation Working Group will be tracked at [4]. -Tim Cole University of Illinois at Urbana-Champaign Co-Chair, W3C Web Annotation Working Group [1] - https://www.w3.org/community/openannotation/ [2] - http://annotator.apache.org/ [3] - https://github.com/w3c/web-annotation/ [4] - https://www.w3.org/annotation/errata/
tcole3 closed this issue. See https://github.com/w3c/web-annotation/issues/147
The use cases were needed to help write the HTML Serialization Note. Completion and ratification of this Note by the WG (final ed. draft: http://w3c.github.io/web-annotation/serialization-html-note/) closes this issue. -- GitHub Notification of comment by tcole3 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/147#issuecomment-280089358 using your GitHub account
Bearing in mind that any normative use of *multiple* named graphs in a given Web Resource will either produce lossy reserializations or not possible to express e.g., in RDFa. -- GitHub Notification of comment by csarven Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/316#issuecomment-280038184 using your GitHub account
iherman closed this issue. See https://github.com/w3c/web-annotation/issues/87
Is this issue solved by the HTML Note? Can we close? -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/87#issuecomment-279955671 using your GitHub account
The meeting minutes are here: https://www.w3.org/2017/02/10-annotation-minutes.html <https://www.w3.org/2017/02/10-annotation-minutes.html> This is probably the last meeting minutes; unless some unexpected happens, the WG does not plan any more formal calls. It was a pleasure working with you guys! So long… Ivan ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Philippe, the Web Annotation WG would like to publish to Working Group Notes. The plan is to publish these alongside the planned publication of the Web Annotation Recommendations; the tentative publication dates has been set to the 21st of February. The two notes are: Document Title: Selectors and States Proposed Short Name: selectors-states Proposed Final URL: https://www.w3.org/TR/2017/NOTE-selectors-states-20170221/ <https://www.w3.org/TR/2017/NOTE-selectors-states-20170221/> Current Editor's draft: http://w3c.github.io/web-annotation/selector-note/ <http://w3c.github.io/web-annotation/selector-note/> Record of the Working Group's Decision (with 5 working days passed since): https://www.w3.org/2017/02/03-annotation-minutes.html#resolution03 <https://www.w3.org/2017/02/03-annotation-minutes.html#resolution03> Abstract: Selecting part of a resource on the Web is an ubiquitous action. Over the years several selection techniques have been developed, usually in conjunction with the media type of the resource. Many of these approaches are also expressed in terms of a fragment identifiers [url], but that is not always the case. This document does not define any new approach to selection. Instead, it relies on existing techniques, providing a common model and syntax to express and possibly combine selections. The formal specification and the semantics originate from a separate Recommendation, namely the Web Annotation Data Model [annotation-model], where it is used to select targets of annotations. The current document only “extracts” Selectors and States from that data model; by doing so, it makes their usage easier for applications developers whose concerns are not related to annotations. ----- Document Title: Embedding Web Annotations in HTML Proposed Short Name: annotation-html Proposed Final URL: https://www.w3.org/TR/2017/NOTE-annotation-html-20170221/ <https://www.w3.org/TR/2017/NOTE-annotation-html-20170221/> Current Editor's draft: http://w3c.github.io/web-annotation/serialization-html-note/ <http://w3c.github.io/web-annotation/serialization-html-note/> Record of the Working Group's Decision (with 5 working days passed since): https://www.w3.org/2017/02/03-annotation-minutes.html#resolution04 <https://www.w3.org/2017/02/03-annotation-minutes.html#resolution04> Abstract: The Web Annotation Working Group has published three Recommendations for expressing annotations on the Web: the Web Annotation Data Model [annotation-model]; the Web Annotation Vocabulary [annotation-vocab]; and the Web Annotation Protocol [annotation-protocol]. These Recommendations define a serialization of the Model in a new, Web annotation-specific profile of JSON-LD [json-ld]. This Note describes and illustrates potential approaches for including annotations within HTML documents. Examples also are included illustrating the use within an HTML document of annotation Selectors as fragment identifiers. (The Working Group's Selectors and States Reference Note [selectors-states] defines the syntax used for Selectors as fragment identifiers.) The approaches described in this document are incomplete and preliminary. They do not exhaust the full range of feasible options. The approaches discussed in this note have emerged from Working Group discussions and should be considered no more than initial starting points for further discussion, experimentation and development. Can we get your approval? Thanks Ivan ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Current status: - there is a tiny dispute on the purules' checker in the protocol document (in the hands of the webmaster) - the final fate of the AS terms, and how this should be reflected in the status section of the vocabulary document, is still pending. Otherwise all documents are ready to be published. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/412#issuecomment-278928054 using your GitHub account
Web Annotation Working Group Teleconference Agenda for Friday 10 February, 2017 (11am Eastern US, 8am Pacific US, 16:00 UTC). Logistics / Call in details: - IRC channel ( irc.w3.org <http://irc.w3.org> ): #annotation. - WebEx via computer: https://mit.webex.com/mit/j.php?MTID=m2c99abd2f8cea21e3e3c33c9c2626eec or direct dial in: +1-617-324-0000 <tel:%2B1-617-324-0000> Meeting Number / Access Code: 645 413 954 Agenda 1. Scribe Selection, Agenda Review, Minutes Approval PROPOSED RESOLUTION: Minutes of the previous call are approved: https://www.w3.org/2017/02/03-annotation-minutes.html 2. General Announcements and Updates (including re Proposed Recommendations and Notes): (Note on) Selectors and States: http://w3c.github.io/web-annotation/selector-note/index-respec.html (Note on) Embedding Web Annotations in HTML: http://w3c.github.io/web-annotation/serialization-html-note/index-respec.html Web Annotation Data Model: http://www.w3.org/TR/2017/PR-annotation-model-20170117/ Web Annotation Vocabulary: http://www.w3.org/TR/2017/PR-annotation-vocab-20170117/ Web Annotation Protocol: http://www.w3.org/TR/2017/PR-annotation-protocol-20170117/ 3. Progress on Blog announcement. 4. Other action items to do before 28 Feb. GitHub Repos Handoff to Community Group 5. AOB Another meeting needed? 6. Adjourn
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/411#issuecomment-277940123 using your GitHub account
@azaroth42, what should happen with this issue? If we want to do it, we should do it soonish, otherwise just close it with no further actions… -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/256#issuecomment-277681145 using your GitHub account
The minutes of the meeting are here: https://www.w3.org/2017/02/03-annotation-minutes.html <https://www.w3.org/2017/02/03-annotation-minutes.html> Note that the group has also taken two resolutions, namely: "The Working Group asks the Director to authorize the publication of the Selector and State note as a Working Group Note, with the short name 'selectors-states'"[1] and "The Working Group asks the Director to authorize the publication of the Embedding Web Annotation in HTML note as a Working Group Note (modulo the editorial changes agreed upon today), with the short name 'annotation-html'"[2] Per charter, these resolutions become final unless a member of the Working Group objects in the coming 5 working days. Nice week-end everyone! Ivan [1] https://www.w3.org/2017/02/03-annotation-minutes.html#resolution03 <https://www.w3.org/2017/02/03-annotation-minutes.html#resolution03> [2] https://www.w3.org/2017/02/03-annotation-minutes.html#resolution04 <https://www.w3.org/2017/02/03-annotation-minutes.html#resolution04> ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Cc: @csarven -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/407#issuecomment-276930085 using your GitHub account
Web Annotation Working Group Teleconference Agenda for Friday 3 February, 2017 (11am Eastern US, 8am Pacific US, 16:00 UTC). Please take a moment before the call to read the Embedding Web Annotations in HTML Note: http://w3c.github.io/web-annotation/serialization-html-note/ Not quite finished, but we are continuing to work this week and hope it will be very close to ready by Friday. We need you to review and comment. Logistics / Call in details: - IRC channel ( irc.w3.org <http://irc.w3.org> ): #annotation. - WebEx via computer: https://mit.webex.com/mit/j.php?MTID=m2c99abd2f8cea21e3e3c33c9c2626eec or direct dial in: +1-617-324-0000 <tel:%2B1-617-324-0000> Meeting Number / Access Code: 645 413 954 Agenda 1. Scribe Selection, Agenda Review, Announcements, Minutes Approval PROPOSED RESOLUTION: Minutes of the previous call are approved: https://www.w3.org/2017/01/20-annotation-minutes.html PROPOSED RESOLUTION: Minutes of the previous call are approved: https://www.w3.org/2017/01/27-annotation-minutes.html 2. Update on Proposed Recommendations Current votes Possible Publication date? Anything else? Web Annotation Data Model: http://www.w3.org/TR/2017/PR-annotation-model-20170117/ Web Annotation Vocabulary: http://www.w3.org/TR/2017/PR-annotation-vocab-20170117/ Web Annotation Protocol: http://www.w3.org/TR/2017/PR-annotation-protocol-20170117/ 3. CFC for Selectors and States Note Plans for Call For Consensus to publish http://w3c.github.io/web-annotation/selector-note/ 4. Discussion of Embedding Web Annotations in HTML Note Issues or concerns that need to be fixed before final editorial cleanup early next week? Readiness for CFC after editorial cleanup complete? http://w3c.github.io/web-annotation/serialization-html-note/index-respec.html 5. Planning for press release for if/when Recommendations are Published Tim and Rob need to draft Testimonials? Schedule? 6. AOB Next meeting: 10 February 7. Adjourn
iherman closed this issue. See https://github.com/w3c/web-annotation/issues/402
👍 Merging for shared sanity us all. 😉 -- GitHub Notification of comment by BigBlueHat Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/403#issuecomment-276690670 using your GitHub account
@BigBlueHat No, I'm talking about Selector Fragment Identifier only. We can "identify" a text on a Web page with both Selector Fragment Identifier with Text Quote Selector (IRI-Alice) and Selector Fragment Identifier with Text Position Selector (IRI-Bob), for example. Then the question was do we need to call the text with its name (Alice, Bob)? If Selector Fragment Identifier is to be used to get to the text, I think it should be called with its location or address which tells us where the text is, rather than its name. It means both Alice's address and Bob's address should be used for that purpose. This is a valid Selector Fragment Identifier. `http://jp.example.org/page1#selector(type=TextQuoteSelector,exact=ペンを,prefix=私は、,suffix=持っています)` Unfortunately, this is invalid as URL. To use this string as URL, we have to encode the Japanese text. Then, the string of IRI and the string of URL are not identical. If these two were identical, I had no concerns. This is why I would like to clarify whether the given sting is "name" (Identifier, IRI) or "address" (Location, URL). I could say the IRI based spec, Selector Fragment Identifier describes how to name fragments on Web. Thanks to the IRI to URL conversion method, we can get to the fragments. It is very capable and I like it. On the other hand, I'm afraid that the original intention of Selector Fragment Identifier might be to provide means to describe location of fragments. If so, I think Selector Fragment Identifier should reform its basement from IRI to URL. Then this note will not need to open pandora's box. What do you think? -- GitHub Notification of comment by tkanai Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/400#issuecomment-276576977 using your GitHub account
BigBlueHat has just created a new issue for https://github.com/w3c/web-annotation: == Citing images in HTML == In the HTML Serialization note, I left a `TODO` for how the image referenced inside the `<blockquote>` might become an actual citation of the image on the remote page (regardless of whether the img's src references a local file or not): https://rawgit.com/w3c/web-annotation/gh-pages/serialization-html-note/index-respec.html#web-annotation-based-citation-urls The surrounding `<blockquote>` and sibling `<q>` tags use the `cite` attribute to reference exact `SpecificResrouce` style selections via the Selector Note's fragment syntax. The `<img>` tag of course lacks the `cite` attribute. So... - is this something "only" possible with RDFa? - is `rel` potentially useful here? Thoughts? 💭 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/402 using your GitHub account
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by tcole3 Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/401#issuecomment-275882202 using your GitHub account
@iherman my respec references likely need help... 😕 -- GitHub Notification of comment by BigBlueHat Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/400#issuecomment-275784582 using your GitHub account
Minutes are here: https://www.w3.org/2017/01/27-annotation-minutes.html <https://www.w3.org/2017/01/27-annotation-minutes.html> Ivan ---- Ivan Herman, W3C Digital Publishing Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
Marked as non-substantive for IPR from ash-nazg. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/pull/399#issuecomment-275694775 using your GitHub account
This week we will dedicate the regular Friday Web Annotation Conference Call slot to discuss and work on the "Embedding Web Annotations in HTML" WG Note. You should only attend if interested in contributing to the development of this Note. The next regular WG call will be next week on 3 Feb. A skeletal first draft version of the Note is now up in GitHub: http://w3c.github.io/web-annotation/serialization-html-note/index-respec.html https://github.com/w3c/web-annotation/blob/gh-pages/serialization-html-note/index-respec.html (Note if you are contributing to this Note and need to make a Pull Request to update it, please do so against the index-respec.html version.) I will be updating the version currently in place again later today. Here are the logistics for this week's call. Web Annotation Working Group Friday January 27, 2016 (11am Eastern US, 8am Pacific US, 16:00 UTC). Logistics / Call in details: - IRC channel ( <http://irc.w3.org> irc.w3.org ): #annotation. - WebEx via computer: <https://mit.webex.com/mit/j.php?MTID=m2c99abd2f8cea21e3e3c33c9c2626eec> https://mit.webex.com/mit/j.php?MTID=m2c99abd2f8cea21e3e3c33c9c2626eec or direct dial in: <tel:%2B1-617-324-0000> +1-617-324-0000 Meeting Number / Access Code: 645 413 954 Agenda - Identify and discuss approaches for serializing Web Annotations in HTML. Thanks, Tim Cole