Purpose
The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that define the standard requirements for the semantics of Authentic Chained Data Containers. The semantics of ACDCs include both source provenance and authorization provenance or delegation. The hypothesis is that the W3C Verifiable Credential standard may be expanded to serve as an Authentic Data Container (ADC) with authentic provenance chains (APC) as a super semantic. This may be further expanded to support both a source provenance sub-semantic and a delegated authorization sub-semantic. These are all encapsulated into the semantics with the supporting syntax of an ACDC.
Deliverables
The table below lists all deliverables of the ACDC Task Force:
...
https://trustoverip.github.io/tswg-acdc-specification/
...
...
...
...
...
...
...
...
STTF is to produce a one or more templates for formal specifications and a set of directives for the content and method of authoring of said documents along with the tooling to facilitate document drafting and review. This TF would operate under the purview of the TSWG, but is fully expected to have participation and contributions across all Working Groups in ToIP.
The STTF needs to provide directives for:
Document Format:
- Markdown (we currently require this format for documents going to WG/SC review)
- Kramdown
- something else
Document rendering:
- Spec-up
- Respec
- MKdocs
- something else
Document Structure:
What sections are required? Examples:
- Introduction
- Clauses (ISO) vs sections
- Bibliography
- Appendix vs Annex (ISO)
What sections are required and should be pre-populated? Examples:
- Foreword (ISO)
Status of This Memo (IETF)
- Copyright Notice (IETF)
Document Style:
- How should normative vs informative sections be distinguished?
- Do we require any Internationalization and localization of specifications?
- What format should references and citations have?
- Format and capitalization of terms and definitions
- iso lower cases all term definitions, but their usages can be capitalized, but not other formatting is applied
- IETF capitalizes terms and definitions and their usages... and sometimes italics/bold are applied (cite)
Document versioning:
- method
- publication deliverable / permanent links
Tooling:
- A set of GitHub actions that render publicly accessible:
- Webpages?
- Word documents?
- PDFs?
Documentation for paths to further SDOs:
- IETF
- ISO
- something else
(W3C is intentionally omitted as they have a well established feeder organization through the CCG)
Deliverables
The table below lists all deliverables of the ACDC Task Force:
| Acronym | Full Name of Deliverable | Deliverable Type | Link to Draft Deliverable | Lead Authors | Status/Notes |
|---|---|---|---|---|---|
| ST | Specification Template | Template | https://github.com/trustoverip/specification-template | Draft |
Proposed Chairs
Please add your name to this list if you wish to be a chair:
- Kevin Griffin Kevin Griffin
- ...
- ...
Meeting Schedule
AsynchronousInitial formal meeting then asynchronous, meeting as needed to gain consensus.
Meeting Agendas and Notes
...
- Slack: This TF has its own dedicated Slack channel: #tswg-sttf
- Github: This TF will use GitHub issues for substantive conversations on topics, not Slack. This way the conversation is source controlled.
Specification Generation
Specifications use the IETF draft format but may use the following:
- Markdown: Draft portions spec written in Markdown
- SpecUP: Final version of spec processed with SpecUp
Use Cases
...
- .
...
...
...
...
...