Hi folks – we have our next committee meeting on Thursday at 11a Eastern.
Here are the notes from previous meetings. Matt and I have drafted a proposed agenda (also pasted below) – please review and reach out in advance with any questions or suggestions!
~greg
Agenda:
Upcoming HSDS walkthrough webinar Nov 18th
Provenance:
OpenLineage report – what it does do, what it doesn’t do (sourcing, but not stewardship?)
How else might we address the needs for provenance (and stewardship) that aren’t addressed by OpenLineage?
Does this leave us thinking that OpenLineage is worth using on its own terms? Or do we need to craft our own approach holistically?
Hi folks – thanks to those who joined us today. Notes are here.
In brief, we primarily discussed the issue of Provenance. We affirmed that OpenLineage seems to do too much of blockchain-style tracing bits of data as they go through complex systems but not enough of specifying stewardship responsibilities. We reiterated some basic needs for provenance in our field, and asked to what extent these needs can already be met by the metadata table (and proposed data guides).
Seems like “a field specifying who has responsibility at the record level for every top-level object” may be one of the minimally necessary steps. A few others were discussed. Let’s see if we can recap here and in a synthesized summary and get a proposal together.
Hi folks – thanks for joining today, notes are here.
Seems like we’ve got provisional agreements on most of the technical issues that emerged, and we’ll expect to see proposals and next steps shaped up accordingly.
We only briefly discussed a big question: what kind of additional documentation materials – especially tutorials and how-to’s – should we develop?
Documentation: tutorials and how-to’s – what do we need?
For instance:
Generating profiles.
Flattening HSDS into a spreadsheet.
Expanding HSDS from a spreadsheet
Producing data guides
What kind of documentation do you think would help you, your partners, and the community with adoption, adaptation, implementation, etc?
Hi folks – happy new year! I hope you had restful holidays. We’re scheduled for a monthly committee meeting on thursday.
Here’s the initial draft of a proposed agenda, rolling items forward from the previous month. Several technical issues for which we either have or are developing proposals, and then the open topic of How-To + Tutorial documentation, which could take up as much time as we want it to.
I checked in with @mrshll who has been out for most of a month, to see if we might need more time – he seems to think he’ll make enough progress by Thursday to warrant the checkin.
@TechnicalCommittee please let me know if you’ll be able to attend Thusday, or if you’d like more time to prepare. And, do you have any suggestions or questions for the agenda.
schema-level $ids – questions remain on how important these $id fields are in the short-term, and the best method to address issues highlighted around these fields in compiled schemas and in Profiles tooling.
the schema discrepancy RE: the relationship between organizations and services – It was determined that properly addressing this would entail a major change, but because it’s not currently considered urgent, changes will instead be implemented within current documentation and tooling ahead of an upgrade to 4.0.
documentation priorities – in which we dedicated some time to generating a list of potential tutorials we could produce this year, including how to: generate a profile, design data partnerships, and reference HSDS in database design.
