RE: Agenda: Web Annotation Teleconference 2 Sept 2015

Rob-

 

I like this way of framing our objectives for Agenda item #4 tomorrow.

 

I'll wait to vote until after our discussion tomorrow, but a very few notes embedded now in the hopes of saving myself (and everyone else) a few cycles during the call tomorrow since much of this is probably obvious to everyone already. Feel free to point out any obvious, irrefutable errors in my thinking to save even more time tomorrow.

 

-Tim Cole

 

From: Robert Sanderson [mailto:azaroth42@gmail.com] 
Sent: Tuesday, September 01, 2015 11:29 AM
To: Frederick Hirsch <w3c@fjhirsch.com>
Cc: W3C Public Annotation List <public-annotation@w3.org>
Subject: Re: Agenda: Web Annotation Teleconference 2 Sept 2015

 

 

All,


Regarding Agenda point 4, I'd like to frame it as the following design tradeoff:
  * Option 1:  Verbose, Structured and Consistent
  * Option 2:  Compact, Flexible and Inconsistent

Following this trade-off, the decision seems to be between:

## Option 1:
  * motivatedBy is only allowed on SpecificResource 

Whether this leads to consistency depends on whether we want to allow motivated by on a SpecificResource used within Multiplicity classes. Probably won't get to this question tomorrow, but something to keep in mind. 


  * SpecificResource is required as the object of hasBody and hasTarget

But we would still allow Literal Body (Simple Text Body) annotations having no need for role/motivatedBy, right? Still a common use case, I feel. 


  * Decreases need for type statements as the structure is regular

Yes, but see below.

 

  * Improves client performance as there are fewer tests that need to be made in the code


## Option 2:
  * Allow motivatedBy on EmbeddedContent, SpecificResource, Multiplicity and the Annotation 

I would like this option better if Annotation were excluded from this list (for reasons that have come up elsewhere). 


  * Allow any resource as the object of hasBody and hasTarget


  * Increases need for type statements as the structure is irregular

Magnitude of benefit may be small, I feel, since the unique required properties/keys of SpecificResource, Composite and EmbeddedContent are sufficient to recognize type, e.g., hasSource (now hasContent), item, and rdf:value (now oa:text, I think), respectively. JSON-LD framing @default can be used to do this (for example). Choice and List (both have members) always require explicit typing.


  * (Arguably) Improves network performance as fewer bytes are transferred [1]

This leaves aside all of the naming issues and subClassing questions, which may be easier to decide (or non-issues) after the above decision has been made.

Many thanks,

 

Rob

 

[1] I include arguably, as with on-the-fly / over-the-wire compression, we (Stanford, IIIF) have found the difference is so minimal at this level that all other network performance issues will make this gain undetectable.

 

 

On Mon, Aug 31, 2015 at 5:01 PM, Frederick Hirsch <w3c@fjhirsch.com <mailto:w3c@fjhirsch.com> > wrote:

Agenda - Web Annotation WG teleconference 2 Sept 2015

(logistics below)

Regrets: Paolo, Doug

1. Agenda Review, Scribe Selection, Announcements

2 Minutes Approval

proposed RESOLUTION: Minutes from 19 August approved, https://lists.w3.org/Archives/Public/public-annotation/2015Aug/att-0302/minutes-2015-08-19.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_public-2Dannotation_2015Aug_att-2D0302_minutes-2D2015-2D08-2D19.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=MHTmEbd2PwDYWnD8EC4SbjC5EHPuC5wU8VcSpnYi2fE&e=> 

3. Data Model Changes for Roles

Section 3.1 https://lists.w3.org/Archives/Public/public-annotation/2015Aug/0211.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_public-2Dannotation_2015Aug_0211.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=oI4u1nbWR3McR_sxUwMnWniGFZlfjsugN1PEHIy0EQE&e=> 

CfC: https://lists.w3.org/Archives/Public/public-annotation/2015Aug/0211.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_public-2Dannotation_2015Aug_0211.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=oI4u1nbWR3McR_sxUwMnWniGFZlfjsugN1PEHIy0EQE&e=> 

4 Data Model Further Considerations (section 3.2)

5  Other Business

6  Adjourn

regards, Frederick & Rob

Frederick Hirsch
Co-Chair, W3C Web Annotation WG

www.fjhirsch.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fjhirsch.com&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=PcP0UgWU5IpY_f1zWjHxL3BygqLP9g1H8h1i4-Y_Lks&e=> 
@fjhirsch
==

Logistics:

IRC #annotation;

WebEx via computer: https://mit.webex.com/mit/j.php?MTID=me422bef2c6690852d7d9a2cf39f591b8 <https://urldefense.proofpoint.com/v2/url?u=https-3A__mit.webex.com_mit_j.php-3FMTID-3Dme422bef2c6690852d7d9a2cf39f591b8&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=FNIP2nEZaTuGnkgtlC1H7Yc3RvDY0Rd1tf6gTsAXwWw&e=> 
or direct dial in: +1-617-324-0000 <tel:%2B1-617-324-0000> , Access code: 645 413 954

We will continue to use zakim to manage the queue, see notes in the wiki:  https://www.w3.org/annotation/wiki/WebEx <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_annotation_wiki_WebEx&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=zjI0r-H6xRs5fYf2_jJkju6US9ijk0nLw4ns2nuwU2k&m=wM3naOT9LbisvwPddknd7uf90goXREV1hLDD6FD_bbc&s=7ERr3MjBZsj1Ds5CnZ0qV7Pw6dUlZwi7-phvDWNaJK8&e=> 

==








 

-- 

Rob Sanderson

Information Standards Advocate

Digital Library Systems and Services

Stanford, CA 94305