Add DOS objects to Beacon response metadata

[mfiume]

It would be useful to have a pointer to the URL of relevant whole datasets, if available. For example, pointers to reads, alignments, variants. Suggest using the Data Object Service Schema being developed by the Cloud Work Stream.

Propose adding:

files : [
   reads : <dos object>
   alignments : <dos object>
   variants : <dos object>
]

[mbaudis]

@mfiume
I am against files as part of the Beacon response, but in support of a generic mechanism, announcing / linking to a DOS response.
It could be an object like:

handover: [
  {
    schema: "DOS",
    access_key: "30822e80-8ef8-4ac9-af5d-304aa7f8c1dd"
  }
],

... which would be a general wrapper for open supported schemas.

Beaconinfo then could announce the support of DOS responses for a given Beacon.

[mbaudis]

... which would be based on the general concept to keep data delivery outside of the Beacon schema itself, but allow co-opting of other standards to fulfil the same purpose (here: using a delivery system through a "handover" mechanism, with authentication / security aspects of non-aggregated response not being part of beacon itself).

[mfiume]

Big +1

[jrambla]

In general, I'm cautious on using specifications (DOS) that are not standard yet.
This doesn't mean that we should plan for them, but not adding them in our specs.

[mbaudis]

We now provide an example of how this could look like on the backend in the GA4GH Schema Building Blocks, e.g. in callsets, biosamples ...

'data_use_conditions' : {
  'id' : 'DUO:0000004',
  'label' : 'no restriction'
}

But we'll need a proper object model for Beacon to make real use of those. This is an area where I really encourage some discussions & contributions!