GEOSS AIP-5 Data Sharing Working Group

1. GEOSS AIP-5 Data Sharing Working Group Prepared by Steven F. Browdy GEO IX Plenary AIP-5 Results Side Event

2. Introduction • Thanks to all working group members for their participation and contributions • Guided by the work done in the Data Sharing Working Group (previously the Data Sharing Task Force) • Three areas of focus: • User authentication and single sign-on • GEOSS Data-CORE compatible licenses • Use metrics GEO IX Plenary AIP-5 Results Side Event

3. Authentication and Single Sign-On • Quick history • First raised in AIP-3 based upon DSTF guidelines • Considered research and secondary focus • Not addressed in AIP-4 effort due to other AIP focus • Re-addressed in AIP-5 • May – December, 2012 • Considered a priority by the GEO Infrastructure Implementation Board GEO IX Plenary AIP-5 Results Side Event

4. Authentication and Single Sign-On • Requirements • Avoid GEOSS Common Infrastructure (GCI) impact as much as possible • Avoid heavy impact on data providers • Focus on open standards • Researched OpenID • Researched SAML-2 • Needs to work in a programmatic way, as well as interactively with a user • Strategies considered • Federated solution between data providers • Centralized solution using a GCI component GEO IX Plenary AIP-5 Results Side Event

5. Authentication and Single Sign-On • Goals • Operationalize authentication and SSO in 2013 • AIP-6 collaboration planned • EC FP7 Citizen Observatory Web (COBWEB) project • Test recommendations during AIP-6 • Engage data providers for a federated solution • Disseminate process for the greater GEOSS architecture GEO IX Plenary AIP-5 Results Side Event

6. Authentication and Single Sign-On • AIP-5 research • OpenID and SAML-2 to be used for authentication and SSO • The idea of a “GEOSS User” is being considered to support data use metrics within GEOSS • Use cases developed GEO IX Plenary AIP-5 Results Side Event

7. Authentication and Single Sign-On • Use cases • Registration for Authentication via OpenID • Registration as OpenID user for Authentication via SAML2 • Organizational user for Authentication via SAML2 • Identification as "GEOSS User" During Registration • OpenID-Protected Data Access via OpenID Authentication • SAML2-Protected Data Access via OpenID Authentication • OpenID-Protected Data Access via SAML2 Authentication • SAML2-Protected Data Access via SAML2 Authentication • Registering and Modifying a New Identity or Service Provider GEO IX Plenary AIP-5 Results Side Event

8. Authentication and Single Sign-On • Recommendations • Federated solution (lightest impact on GCI) • OpenID and SAML-2 to be used • Data provider support for a set of “trusted” OpenID identity servers to be used with SAML2 user management systems • USA has such a list • Discussions planned for INSPIRE list • Authentication is the current primary goal • Access control is a future interest • User interaction is the current primary goal • Programmatic authentication is a future interest GEO IX Plenary AIP-5 Results Side Event

9. GEOSS Data-CORE Licenses • Quick history • First raised in AIP-3 based upon DSTF guidelines • Considered research • Not addressed in AIP-4 effort due to other AIP focus • Re-addressed in AIP-5 • May – December, 2012 • Considered a priority by the GEO Infrastructure Implementation Board GEO IX Plenary AIP-5 Results Side Event

10. GEOSS Data-CORE Licenses • Requirements • Reflect the results of the Legal Interoperability Subgroup of the Data Sharing Working Group • Recommend the placement of license metadata in as many metadata standards as possible. • ISO 19115 family of standards (including ISO 19139) • Dublin Core • OpenSearch (RSS/Atom) • WCS, WFS, WMS, WPS, SOS • GBIF (Global Biodiversity Information Facility) • THREDDS • NetCDF, HDF5 • GCMD DIF • Implementation • Modifications to CSR • Modifications to data provider metadata GEO IX Plenary AIP-5 Results Side Event

11. GEOSS Data-CORE Licenses • Goals • Draft of guidelines document in AIP-5 • Engage data providers for testing the license discovery in AIP-6 • Disseminate official guidelines document to GEOSS data providers • Publish guidelines for data providers and data users on the Best Practices Wiki GEO IX Plenary AIP-5 Results Side Event

12. GEOSS Data-CORE Licenses • AIP-5 research • Determine the license fields needed • License/waiver name - this will be a text field conatining the common name of the license or waiver (CC0, CC-BY, etc.) • License pointer - this will be a URL field that links to the actual license or waiver • License logo - this will be a URL field that links to a graphical logo for the license or waiver • Attribution text - this will be a text field that contains the actual words to be used by users/applications for attribution • Determine placement • ISO, Dublin Core, OpenSearch handled • Others still being worked on GEO IX Plenary AIP-5 Results Side Event

13. Use Metrics • Quick history • First raised in AIP-3 based upon DSTF guidelines • Considered research and secondary focus • For the benefit of monitoring GEOSS usage • Under no circumstances, can individual information about a user's access to GEOSS-available data be gathered, tracked, monitored, or analyzed • Not addressed in AIP-4 effort due to other AIP focus • Re-addressed in AIP-5 • May – December, 2012 • Considered a priority by the GEO Infrastructure Implementation Board GEO IX Plenary AIP-5 Results Side Event

14. Use Metrics • Requirements • Minimize impact on the GEOSS Common Infrastructure (GCI) • Avoid heavy impact on data providers • Strategies considered • Data providers will report data usage to GCI • Acquire information about accessed data • Acquire information about discovered data, which can allow data providers to understand the value of GEOSS • No user identification (person or organization) reported • Reporting should be based upon “GEOSS Users” only GEO IX Plenary AIP-5 Results Side Event

15. Use Metrics • Goals • Operationalize use metrics in 2013 • Generate recommendation document as a basis for AIP-6 CFP • Recommend the various information items to be gathered and provided to the GCI. • Recommend the implementation details of how to gather and report user metrics. • Test implementation during AIP-6 • Engage data providers to supply the desired metrics • Generate tutorial documentation regarding use metrics for placement in the Best Practices Wiki and distribution to data providers. GEO IX Plenary AIP-5 Results Side Event

16. Use Metrics • AIP-5 research • Use metrics information to be provided • provider name • dataset accessed • date/time of access • specify which "tags" were associated with the data (geossDataCore, geossAttribution, etc.) • was a license used and which one • was cost involved and how much • optional additional information (up to the discretion of the data provider) • Use cases developed GEO IX Plenary AIP-5 Results Side Event

17. Use Metrics • Use cases • Data Provider or GEOSec Accesses and Uses Metrics • Data Provider Submits Metrics to the GCI • Data Provider Resubmits Metrics to the GCI • Analyze GEOSS Data-CORE Use from the Metrics • Analyze SBA Use from the Metrics GEO IX Plenary AIP-5 Results Side Event

18. Use Metrics • Recommendations • Guidelines for data providers to submit use metrics • there may need to be a registration step to allow data providers to verify their submissions, and to resubmit if necessary • regularity of metrics submission will vary by data provider (real-time or periodic) • reporting periods (daily, monthly, quarterly, etc.) • Use metrics should be open to the public GEO IX Plenary AIP-5 Results Side Event

19. ? ? ? GEO IX Plenary AIP-5 Results Side Event