Re: Agenda: Web Annotation Teleconference 2 Sept 2015

Rob,

> On 02 Sep 2015, at 03:16 , Robert Sanderson <azaroth42@gmail.com> wrote:
> 
> 
> Option 1 (Consistent)  is 3.2.1 and 3.2.2, and most of 3.1.*
> Option 2 (Compact) is 3.2.3
> 

Thanks for specifying this, because I was not sure either. And, to be clear, this also means that Option 1 and 2 are not some sort of a deeply mutually incompatible approaches, except that the acceptance of Option 2 may require *some* adjustments, primarily on the model level.

B.t.w., in [1] the text says:

> this also makes the determination of the class of the body more difficult as there are multiple similar options.

this is true, but I do not see that as a huge issue. In the JSON world, the presence of the "text" or the "content" property clearly delineates what type of body that particular one is. In the RDF world, by setting the rdf:domain of 'oa:text' clearly determines the type. In other words, I do not think I agree with your characterization below:

* Increases need for type statements as the structure is irregular

For me, the easy way of adding textual annotations into the structure is a determining factor (I presume that is what you called compactness), which makes be in favour of this one.

Thanks!

Ivan

P.S. This option does raise one issue which is more general: what happens if the user gives an inconsistent structure; in this case, if "content" and "text" appear on the same body. We may have to clearly note those inconsistencies in the spec as errors (and, if we want to be extremely thorough, we may have to add some OWL or SPIN-like statements that makes these inconsistencies trackable for SW environments). But that is a discussion for another day.


[1] http://w3c.github.io/web-annotation/model/wd/roles.html#allow-hasrole-on-new-embeddedtextualbody-class



> Rob
> 
> 
> On Tue, Sep 1, 2015 at 2:27 PM, Doug Schepers <schepers@w3.org> wrote:
> Hi, Rob–
> 
> Can you give code examples for both Option 1 and Option 2?
> 
> That would help me understand how it's being framed in a more concrete way.
> 
> Sorry, but so much has been talked about, with so many orthogonal issues, that's it's hard for me to keep it all in my head. Others may feel the same.
> 
> Thanks–
> –Doug
> 
> 
> On 9/1/15 12:29 PM, Robert Sanderson wrote:
> 
> 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
>    * SpecificResource is required as the object of hasBody and hasTarget
>    * Decreases need for type statements as the structure is regular
>    * 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
>    * Allow any resource as the object of hasBody and hasTarget
>    * Increases need for type statements as the structure is irregular
>    * (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
> 
>     3. Data Model Changes for Roles
> 
>     Section 3.1
>     https://lists.w3.org/Archives/Public/public-annotation/2015Aug/0211.html
> 
>     CfC:
>     https://lists.w3.org/Archives/Public/public-annotation/2015Aug/0211.html
> 
>     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 <http://www.fjhirsch.com>
>     @fjhirsch
>     ==
> 
>     Logistics:
> 
>     IRC #annotation;
> 
>     WebEx via computer:
>     https://mit.webex.com/mit/j.php?MTID=me422bef2c6690852d7d9a2cf39f591b8
>     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
> 
>     ==
> 
> 
> 
> 
> 
> 
> --
> Rob Sanderson
> Information Standards Advocate
> Digital Library Systems and Services
> Stanford, CA 94305
> 
> 
> 
> --
> Rob Sanderson
> Information Standards Advocate
> Digital Library Systems and Services
> Stanford, CA 94305


----
Ivan Herman, W3C
Digital Publishing Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704