1. Brief WG/IG reporting Tobias Weigel on behalf of co-chairs
- @resdatall
CC BY-SA 4.0

2. https://rd-alliance.org/ - https://twitter.com/resdatall
IG Data Fabric
Status – working on:
Delivering harmonized recommendation doc (GDOC + virtual layer paper) as supporting output
editing, discussion, heading for submission after P10 -

3. Data Fabric components
Consensus on essential consensus – but detail questions remain:
Is the scope of each component well-defined?
How do the components interact?
What combinations of components make sense? What is typical use?
 Systematic study on components and their networked sets
scope, role, interfaces, status of interface specs, status of implementation, relation with layers, governance issues
also: what does layering mean for implementations scenarios and disciplines? -

4. Specific configuration: Climate data components
Agent
Search component
Type registry
Broker
Schema registry
Processing executor
Collection builder
PID registry
Identifier Infrastructure Usage for Global Climate Reporting

5. https://rd-alliance.org/ - https://twitter.com/resdatall
RPID Testbed
1 year effort, started 04/2017, NSF sponsored
IU, Tufts, CNRI
RPID project establishing a test bed across groups
PIT, DTR, Kernel Info
URN-Handle transition
AWS, Dockerization, config management via Puppet -

6. https://rd-alliance.org/ - https://twitter.com/resdatall
Further WGs
WG Research Data Collections:
Editing comprehensive recommendation document
API feature freeze
Collections API at DH 2017 in August
WG Kernel Information:
DANS: Social science RDA-EU collaboration project (PITSS)
Feedback on profile strawman, possible extension
Also relates to PIT, DTR, Data Fabric
WG Data Type Registries:
Workshop planned at DKRZ (pre P10) on types and typing scenarios -

7. WG Research Data Collections
(Research) data management beyond single objects
Not just describe collections, but enable actions on them
Create, Read, Update, Delete, List plus some others
Machine agents as primary users
Contribute an essential component to the Data Fabric
Provide a cornerstone API specification against which tools and services can be built across community boundaries

8. Design considerations
Key requirements:
Favor limited functionality over support for use case details
Offer extension points
Use by machine agents primarily
No constraints on particular back-ends
No mandatory use of PIDs (supported, but optional)

9. API: Structure

10. Current implementations and use cases
REPTOR: data repository, also covering DTR and DFT recommendations
Tufts: Python/Flask implementation for Perseids Project
backends for file system, RDF/LDP, MongoDB
iDigBio: Python and redis-based
Use cases:
Perseids, iDigBio, GEOFON, DKRZ/CMIP6, CAU Kiel/IGSN – more are welcome!
Full recommendation document in editing over summer! -