Data Provenance (DPS) TC

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

yes

yes

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina

First, thanks Duncan for prompting this important discussion and for his thoughtful guidance on process - much appreciated as always.

To move forward and set up the official DPS TC repository by OASIS procedures, we need to establish a quorum. To help us do so, please respond to this message-yes or no-as soon as possible. Your response, either way, is helpful.

Motion for Consideration:
I move to approve the TC chair(s) working with OASIS to set up the DPS TC GitHub repository, which will serve as the official repository for the source files for the written DPS TC specification.

Bryan Botnick, Lisa Bobbitt, Fotis Psallidas, and I (Kristina Podnar) are proposed maintainers of this repository.

If we reach a quorum, we can proceed with repository setup before our April 22 meeting.

In the meantime, nothing prevents anyone from reviewing what has already been developed by D&TA. Here are the relevant links for your reference:

·    Executive Briefing (https://assets.ctfassets.net/b9fqy5fsj3oi/5SIIAFf0wpurPhjDiSC7Ju/ba6ab6a25aeeba81ec62904486cb215f/Data_Provenance_Standards_Executive_Overview_July_2024.pdf)

·    GitHub repository with technical specifications of the standards (https://github.com/Data-and-Trust-Alliance/DPS)

·    Use cases (https://downloads.ctfassets.net/b9fqy5fsj3oi/37mIPyZhfzofPl8InQKUME/7cdd1cbdaa82e8083fba5fc13c0cd128/D_TA_Data_Provenance_Standards_Use_Case_Scenarios_v01td_-_Reduced.pdf)

· Metadata Generator (we can make the source code available in the repository, per the question raised in the chat during the first meeting) (https://data-and-trust-alliance-data-provenance-standards.northeurope.cloudapp.azure.com/)

As Duncan rightly pointed out, we'll need to carefully consider which pieces we move forward with from a project perspective. I suggest we reserve that discussion for the April 22 meeting, though I defer to our co-chairs and all of you for thoughts and input.

Thanks in advance for your quick replies and continued engagement!

Kristina