anandbanik / traceability-vocab

A traceability vocabulary for describing relevant Verifiable Credentials and their contents.

Traceability Vocabulary Specification

About

This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to traceability information, such as chemical properties, mechanical properties, country of origin, and other attributes used to determine the status of products and materials in a supply chain.

We encourage contributions meeting the Contribution Guidelines. While we prefer the creation of Issues and Pull Requests in the GitHub repository, discussions often occur on the public-credentials mailing list as well, and at regular public meetings (see below).

Latest Spec

https://w3id.org/traceability

Meetings

Meetings are held

• Tuesdays at 13:30 ET/10:30 PT
• Via Jitsi in browser or standalone app
• using this link: meet.w3c-ccg.org/traceability
• With standing agenda to review open Pull Requests (trace-vocab, trace-interop), then open Issues (trace-vocab, trace-interop), unless otherwise noted on the mailing list

Historical archives for meetings can be found here.

Hosting instructions

Any chair, editor, or other party authorized by CCG to manage recordings and minutes can do the following.

Before the Meeting

• Duplicate the W3C-CCG Traceability Agenda Email Draft in Google Docs
• Update all the items highlighted in yellow, in particular adding new agenda items for week starting with item 6.
• If there are presentation materials, add them to the appropriate dated meeting archives folder before the meeting.
• Send agenda to [e-mail] before each meeting. Use the following format for the subject (modify date accordingly):

  [AGENDA] W3C CCG Traceability Call - 2022-11-22
  

• Confirm in the CCG mail archives that the agenda was sent correctly

During the Meeting

• Be sure to click Start Recording and then Stop Subtitles
• Make sure to link to the agenda at the beginning of the meeting (Agenda: ...)
• Make sure the scribe is identified (Scribe: ... or scribe+ ... identifying someone else, or scribe+ identifying oneself). Scribes, please familiarize yourself with general scribing guidance here and here.
• Make sure topics are labeled when the topic changes (Topic: ...)
• Make sure that action items are listed so that they can be added to issues later ("Action: ...")

After the Meeting

• Kick everyone from the meeting, and click Stop Recording
• Publish the minutes

Development

See DEVELOPMENT.md. The basics are as follow:

npm i
npm run lint
npm run test
npm run build
npm run serve