- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Tue, 1 Sep 2015 18:16:34 -0700
- To: Doug Schepers <schepers@w3.org>
- Cc: Frederick Hirsch <w3c@fjhirsch.com>, W3C Public Annotation List <public-annotation@w3.org>
- Message-ID: <CABevsUGOQhomFUdfwFo6e4pWenfpCgLH_O_s71=q5f6BwnH7QA@mail.gmail.com>
Option 1 (Consistent) is 3.2.1 and 3.2.2, and most of 3.1.* Option 2 (Compact) is 3.2.3 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
Received on Wednesday, 2 September 2015 01:17:05 UTC