Changes between Version 2 and Version 3 of Taskforces/FCS/VidConf20140304


Ignore:
Timestamp:
03/04/14 15:22:18 (10 years ago)
Author:
Oliver Schonefeld
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Taskforces/FCS/VidConf20140304

    v2 v3  
    11= FCS Taskforce Video Conference 2014-03-04 =
    2 
    3 * What?
    4  * FCS specification draft
    5 * Who?
    6  * Members of the [[Taskforces/FCS|FCS taskforce]]
    7 * When?
    8  * 4 March 2014: 14.00 - 16.00 CET
    9 * Where?
    10  * !FlashMeeting: [http://fm.ea-tel.eu/fm/29d4d5-36470]
     2 * What?
     3  * FCS specification draft
     4 * Who?
     5  * Members of the [[Taskforces/FCS|FCS taskforce]]
     6 * When?
     7  * 4 March 2014: 14.00 - 16.00 CET
     8 * Where?
     9  * !FlashMeeting: [http://fm.ea-tel.eu/fm/29d4d5-36470]
    1110
    1211== Agenda ==
     12 * Welcome
     13 * Introduction round
     14 * Discussion of the [[FCS-Specification-ScrapBook|FCS specification draft]]
     15 * Planning on time-frame for finishing the draft
    1316
    14 * Welcome
    15 * Introduction round
    16 * Discussion of the [[FCS-Specification-ScrapBook|FCS specification draft]]
    17 * Planning on time-frame for finishing the draft
     17== Outcome: Decisions and Actions ==
     18 * '''Action''': add default recommendation for hits granularity: change wording in section to make clear that, Endpoint shall provide one hit within one `<sru:record>`. If multiple hits occur within one resource, and endpoint must serialize each hit as an individual record. Endpoints are expected to do this on best effort basis.
     19 * '''Action''': separate Data Views from Core-Spec; add them in an appendix, if a "one document" spec is compiled. Generic Hits however will also stay in Core-Spec, because it's the lowest common denominator.
     20 * '''Action''': change wording to indicate, that `<Hits>` element is optional, but make clear that Endpoint should use it
     21 * '''Action''': change wording to indicate,that an Endpoint MUST support Endpoint Description in ''explain''
     22 * '''Action''': change element names `<Collection*>` to `<Resource*>`; that's more coherent with the other parts of the spec.
     23 * '''Decision''': drop recursive `<Resource>`; Endpoint Description (and/or CMDI Data Views) can be used to exploit Resource hierarchy
     24 * '''Decision''': submit new FCS spec to SCCTC for their April meeting; we need to be done with out work by end of March.
     25 * '''Decision''': incorporate discussed changes ASAP and start new (mail) discussion round
     26 * '''Decision''': Transition to new spec: build second Aggregator, that supports new spec; set deadline for centers with "old Endpoints" to adopt to the spec until 2014-10-31; the old Aggregator will be disabled in November; Tübingen will ensure, that they have a person to work on the Aggegator after May 2014.
     27
     28
    1829
    1930== Documents ==
    20 
    21 * [[FCS-Specification-ScrapBook|FCS specification draft]]
     31 * [[FCS-Specification-ScrapBook|FCS specification draft]]