Prepare challenge data schema Kickstart meeting

[tschaffter]

Overview

The goal of this meeting is to review past/current Sage efforts to generate a data schema for challenge.

Challenge data schema used by

• New challenge platform developed in collaboration with IBM and XPRIZE
• Other? (@kdaily )

Data schema specifications

• Schema should support ideally the data from past challenges organized on Synapse for the past 13 years

Meeting agenda

Work in progress.

• Why develop a challenge data schema
• What project(s) would use it
• Challenge platform: identify a few specifications
• Timeline
• Identify blocks of the challenge data schema (e.g. actors (organizers, participants, etc.), submissions, results, etc.)
• Scope of the data schema
• Best practices / conventions
  • naming conventions
  • best practices to keep the schema extensible
• Tools to create/convert schemas
  • GitHub
  • Figma?
• Provenance
• Automatic aggregation
• Data governance

[tschaffter]

Meeting with Milen on Feb 18

Notes

• validation rules

  • defined in external file

• inheritance / semantic relationship (JSON schema itself is not good for that)

  • JSON-LD, Schema.org has very generic terms defined by Google+
  • they encode the validation rules using JSON-LD (linked data), then parse out the JSON-LD schema to generate automatically the actual JSON schema, does not include reference to external definition (contains only the validation rules).
  • internal effort: JSON-LD schema, is an extension of schema.org

• JSON schema does not have a good mechanism to separate data and data representation (UI)

• who is funding the challenge data (MIAC and IBM collaboration, ask Justin)

Schema.org: internal/external extension vs inheritance

Agenda

• Presentation on MIAC: who initiated this effort, funded by, goal, current status
  • status of the MIAC grant
• inheritance of MIAC
• context: mix of schema.org and schema.biothings.io

Tool: csv to schema.org (written by Milen) Tool: Schema explorer

1. use cases (+ relevance column)
2. what should be the backend/frontend
3. list different components/modules on a spreadsheet

• before schema, define the features first, related to API
• identify component names

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.