[Meta] Welcome – Repository Ready, Let's Begin the Work

[amir-hameed-mir]

Welcome to the Verifiable Supply Chain Community Group

I am pleased to announce that the Verifiable Supply Chain Community Group is now officially underway. The repository structure is in place, and we are ready to begin collaborative work on advancing verifiable data standards in global supply chains.

Repository: https://github.com/w3c/vsc-cg

---

What We Have Established

The repository is organized to support our charter and align with the UORA CG liaison. The initial structure includes:

Directory	Purpose
profiles/	Industry-specific VC/UORA profiles (pharmaceuticals, critical minerals, food & beverage, luxury goods, electronics, automotive)
interoperability/	Mappings to legacy standards: GS1 EPCIS, ISO 28000, and regulatory frameworks (DSCSA, EUDR, CBAM)
trust-framework/	Governance models, accreditation criteria, and liability frameworks
use-cases/	ROI calculators, implementation guides, and case study templates
tools/	Reference implementations, SDKs, and conformance test suites
specs/	Formal JSON-LD schemas, API definitions, and context files
.github/	CI/CD workflows and issue templates

This structure is intentionally modular, allowing us to develop in parallel across industry verticals while maintaining a cohesive core.

---

Call for Contributors

This is a community effort, and I invite all members to participate. There are several ways to get involved.

Immediate Opportunities

Role	Description
Editors	Lead drafting of profiles and specifications
Co-Chair	Help coordinate meetings, agenda, and community engagement
Profile Leads	Drive industry-specific profiles (pharma, minerals, food, luxury, electronics, automotive)
Technical Contributors	Develop reference implementations, test suites, and tooling
Use Case Contributors	Document real-world implementations and ROI models

If you are interested in any of these roles, please comment on this issue or contact me directly.

---

Proposed Initial Workstreams

Based on our charter, I propose we focus on the following initial workstreams.

Workstream	Priority	Description
Pharmaceuticals Profile	High	DSCSA-aligned verifiable credentials, batch-level traceability, serialization requirements
Critical Minerals Profile	High	Conflict minerals traceability, ethical sourcing attestations
EPCIS Mapping Specification	High	Translate GS1 EPCIS events to Verifiable Credentials
Trust Framework Template	Medium	Governance models, trust anchor accreditation criteria
ROI Calculator & Case Study Template	Medium	Quantifiable business value documentation

---

Meeting Structure & Cadence

I would like your input on how we structure our meetings to best accommodate participants across time zones.

Proposed Options:

Option	Day/Time	Format
A	Wednesdays 10:00 EST	60-minute working session
B	Tuesdays 15:00 UTC	60-minute working session
C	Alternating weeks	90-minute deep-dive
D	Bi-weekly	60-minute coordination + async work

Please share your preference, or suggest alternatives that work better for your schedule.

Agenda for First Meeting (Tentative):

1. Welcome and introductions
2. Overview of repository structure
3. Prioritization of initial workstreams
4. Assign leads for profiles
5. Set meeting cadence
6. Next steps

---

Discussion Topics for the First Weeks

To get us moving, I propose we discuss the following in the coming weeks.

Topic	Lead
Pharmaceuticals Profile: What are the core data elements required for DSCSA compliance?	Open
EPCIS Mapping: How do we map existing EPCIS event data to VC models?	Open
Trust Framework: What governance models already exist in supply chain consortia?	Open
UORA Liaison: How do we ensure synchronized development with the UORA CG?	Amir

---

Next Steps

1. Review the repository – Familiarize yourself with the structure
2. Express interest – Comment below with areas you would like to contribute to
3. Suggest meeting time – Let me know your availability
4. Share use cases – If you have real-world supply chain implementations, please document them

---

Let’s Begin

The work ahead is significant, but the opportunity is equally substantial. Verifiable supply chains can transform how we track provenance, ensure compliance, and build trust across global industrial networks. I am excited to work alongside all of you to make this a reality.

Please comment with your thoughts, availability, and areas of interest.

Looking forward to building this together,

Amir Hameed Mir
Chair, Verifiable Supply Chain Community Group
W3C

[Manilvc]

Hi Amir and the community,
I'm Manil Jayswal, a Product Engineer from Ahmedabad, India with 3 years of hands-on experience in Backend Development, Self-Sovereign Identity (SSI), Verifiable Credentials (VC), and Blockchain integrations.
I have practical experience building W3C-compliant Verifiable Credentials and Verifiable Presentations workflows, implementing DID Comm protocols for secure peer-to-peer identity communication, and working with DIF specifications for cross-ecosystem interoperability. This makes the goals of the Verifiable Supply Chain CG directly aligned with my professional background.
I'd like to contribute in the following areas:

• Technical Contributor — Reference implementations, SDKs, and conformance test suites (/tools directory)
• EPCIS Mapping Workstream — Help translate GS1 EPCIS events into Verifiable Credential models
• Specifications — JSON-LD schemas and API definitions (/specs directory)
• Pharmaceuticals Profile — Happy to support DSCSA-aligned credential workflows

My relevant tech stack:

• Python (FastAPI/Flask)
• W3C VC & VP
• DIDs & DID Comm
• DIF Standards
• Blockchain Anchoring
• Docker
• Azure
• MySQL
  Looking forward to contributing and collaborating with this community!

Manil Jayswal
Product Engineer — Backend • Blockchain • SSI / Verifiable Credentials
LinkedIn Profile: Manil Jayswal
Github Profile: jayswal433
Location: Visnagar, Gujarat, India

[amir-hameed-mir]

@Manilvc

Hi Manil, welcome — glad to have you here.

Your experience with SSI, VCs, DIDComm, and DIF lines up really well with what we’re doing, especially around EPCIS mapping and VC-driven supply chain flows.

To get started, I’d suggest:

Take a look at the open issues and pick something that interests you. If you have a new idea, feel free to open an issue first.

For anything substantial, it’s best to discuss briefly on the issue before jumping into implementation so we stay aligned.

When you’re ready, submit a PR linked to the issue — smaller, focused contributions are easier to review.

For specs work (JSON-LD / VC), examples and clear context definitions are very helpful.

For DIDComm / DIF-related pieces, please call out any interoperability assumptions you’re making.

One small but important point — if you use AI tools anywhere in your contribution (code, specs, docs), just mention it in the PR or issue. It helps keep things transparent for reviewers.

A good starting point for you could be EPCIS → VC mapping or contributing to the reference implementations under /tools.

Looking forward to seeing your contributions.

[jayswal433]

Hi @amir-hameed-mir,

Thank you for the warm welcome and the clear guidance — really appreciate it!
Just to mention — I'll be contributing from this account (@jayswal433) going forward.
I'll start by going through the open issues and pick something around EPCIS → VC mapping or reference implementations under tools as you suggested. I'll make sure to discuss on the issue before jumping into implementation.

Noted on the AI transparency point — I'll always mention it if I use any AI assistance in my contributions.
Looking forward to getting started!

Manil Jayswal

[amir-hameed-mir]

@jayswal433

Welcome to the Verifiable Supply Chain Community Group. We are pleased to have you with us.

To ensure you are fully integrated into our technical workflow, I encourage you to subscribe to our mailing list at public-vsc@w3.org Once you have subscribed, please take a moment to introduce yourself to the community. It is a standard practice that allows other members to learn about your background, your areas of interest, and how you plan to contribute to our work.

We look forward to your contributions.

Best regards,

Amir Hameed Mir
Chair, Verifiable Supply Chain CG

[jayswal433]

Hi Amir and the community,
I'm Manil Jayswal, a Product Engineer from Gujarat, India with 3 years of hands-on experience in Backend Development, Self-Sovereign Identity (SSI), Verifiable Credentials (VC), and Blockchain integrations.
I have practical experience building W3C-compliant Verifiable Credentials and Verifiable Presentations workflows, implementing DID Comm protocols for secure peer-to-peer identity communication, and working with DIF specifications for cross-ecosystem interoperability. This makes the goals of the Verifiable Supply Chain CG directly aligned with my professional background.
I'd like to contribute in the following areas:

Technical Contributor — Reference implementations, SDKs, and conformance test suites (/tools directory)
EPCIS Mapping Workstream — Help translate GS1 EPCIS events into Verifiable Credential models
Specifications — JSON-LD schemas and API definitions (/specs directory)
Pharmaceuticals Profile — Happy to support DSCSA-aligned credential workflows

My relevant tech stack:

• Python (FastAPI/Flask)
• W3C VC & VP
• DIDs & DID Comm
• DIF Standards
• Blockchain Anchoring
• Docker
• Azure
• MySQL

Looking forward to contributing and collaborating with this community!
Manil Jayswal

Product Engineer — Backend • Blockchain • SSI / Verifiable Credentials
LinkedIn: Manil Jayswal
GitHub: @jayswal433
Location: Gujarat, India

[amir-hameed-mir]

@jayswal433 Thank you, you can draft an email introduction from your email through which you joined, subject can be Introduction and your above intro is detailed already and send it to public-vsc@w3.org , you will find all meeting links, minutes and other communication there, beside our GitHub you can also start discussions in the mailing list itself if there is anything you would be interested to share and present