Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review approaches to locating objects of interest #22

Open
ianfore opened this issue Oct 15, 2020 · 2 comments
Open

Review approaches to locating objects of interest #22

ianfore opened this issue Oct 15, 2020 · 2 comments

Comments

@ianfore
Copy link

ianfore commented Oct 15, 2020

Suggest that TASC review of relative roles of Search and DRS bundling is needed. Current bundling use cases in the examples given below may be better addressed through the ability to identify objects of interest through queries against defined schema. Bundling as a bag of objects provides insufficient information to users.

Illustrative examples are provided in this issue

Some key questions for consideration:

  • Should the question of how a complex object is unpacked and handled be left to tools that are specific to those complex objects? In this situation DRS should confine itself to indicating the type of the object. Use of those objects is then handled by calling upon tools that know how to work with that type. AKA - separation of concerns.
  • If we support complex objects what schema mechanism could be used for representing the content of a bundle? Could SchemaBlocks or other existing standards be used?
  • Is Research Objects a suitable standard for this which GA4GH could adopt?
@uniqueg
Copy link

uniqueg commented Jun 18, 2024

If I understand the problem correctly, indeed it sounds like something that RO-Crate addresses, at least with respect to linking data models to entities. In any case I think that DRS should only (optionally) reference schemas, not "unpack" entities themselves (i.e., +1 for separation of concerns, we probably don't want to overload DRS too much).

That being said, this issue is probably more fitting for DaMaSC at this point?

@ianfore
Copy link
Author

ianfore commented Jun 18, 2024

Suggesting we should close this. There are two routes by which the issue can be handled:

  • Schemas in Discovery mechanisms (Data Connect, Beacon) allow identification of individual files according to their attributes
  • DRS has deprecated bundling and recommended that objects consisting of multiple files are represented in some standard format which includes a manifest describing the structure. DRS deliberately didn't address what manifest format would be used.

Yes DaMaSC can potentially address the first of these. RO-Crate is a candidate in the second case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants