add meeting minutes and some minor fixes

website/docs/about/Meetings.md

@@ -17,12 +17,13 @@ A group mailing list is maintained and can be used by any list member to post me
 
 UNTP development team meetings are held fortnightly at alternating times to accomodate participants from different timezones. Use the links below to add the calendar entries to your diary or add the meeting links.
 
-* **Thursday 8pm UTC meetings**.  Every 4 weeks. Next meeeting 6th Feb 2025. 
-	* [ICS Calendar File](../../meetings/UNTP-8pm-UTC-4weekly.ics).  Download and double click to add the meetings to your calendar.
-	* [Join the meeting](https://us02web.zoom.us/j/82338035316?pwd=kscabBvSB9hTukagOJCN4shxSt6ZWT.1). Click to join the meeting without a calendar entry.
 * **Thursday 8am UTC Meetings**. Every 4 weeks. Next meeting 20th Feb 2025.  
 	* [ICS Calendar File](../../meetings/UNTP-8am-UTC-4weekly.ics). Download and double click to add the meetings to your calendar
 	* [Zoom meeting link](https://us02web.zoom.us/j/82338035316?pwd=kscabBvSB9hTukagOJCN4shxSt6ZWT.1). Click to join the meeting without a calendar entry.
+* **Thursday 8pm UTC meetings**.  Every 4 weeks. Next meeeting 6th Mar 2025. 
+	* [ICS Calendar File](../../meetings/UNTP-8pm-UTC-4weekly.ics).  Download and double click to add the meetings to your calendar.
+	* [Join the meeting](https://us02web.zoom.us/j/82338035316?pwd=kscabBvSB9hTukagOJCN4shxSt6ZWT.1). Click to join the meeting without a calendar entry.
+
 
 Each meeting will generally work through open [issues](https://github.com/uncefact/spec-untp/issues) and [pull requests](https://github.com/uncefact/spec-untp/pulls). 
 
@@ -32,6 +33,7 @@ Previous meeting dates, recordings, transcripts, and minutes are summarised belo
 
 |Meeting|Summary|Recording|Transcription|
 |---|---|---|---|
+|2025-02-06| [The UNTP meeting focused on reviewing change requests, refining the identity resolver framework, approving the verifiable credentials update, discussing implementation guidance, exploring certification and governance models, and addressing open issues for future development.](#2025-02-06-meeting-summary)|[video](https://us02web.zoom.us/rec/share/ayxfoRJH0z9FXI25UWNuZ4KQ0LQ7N3GoLHTxbz-wTW4fjjOfMjQ3_zr-uNp6jUhk.dwHfJ3YszOvW9aLb)|[transcript](../../meetings/2025-02-06-Recording.txt)|
 |2025-01-23| [The meeting focused on enhancing UNTP governance, fostering community engagement through CAP, refining chain of custody models, and exploring tools for effective collaboration, setting the stage for further iterations and sector-specific applications.](#2025-01-23-meeting-summary)|[video](https://us02web.zoom.us/rec/share/kQt_d4JsLMrfy3iCGf1hoD04b-7Rg5ksuGML-Sj8wSMZL7l3uWqhkO4HEPpr8nBG.eHleGSxocBLfQumY)|[transcript](../../meetings/2025-01-23-Recording.txt)|
 |2025-01-08| [The meeting addressed progress on UNTP implementations, focusing on decentralized access control, sustainable mining, and selective disclosure, while initiating discussions on managing mixed commodities and advancing public review of specifications.](#2025-01-08-meeting-summary)| [video](https://us02web.zoom.us/rec/share/u7PDvJjbvgcJui79hqIYoh-CAzgoKVZtt5fieXWZkenCMkMCpbnmA4XKrEJjBJsT.eIZrcLXd5eSP72e2)|[transcript](../../meetings/2025-01-08-Recording.txt)|
 |2024-12-12| [The meeting discussed progress on UNTP collaborations, technical updates, and pilot projects, with participants emphasizing interoperability, schema flexibility, and industry-specific implementations for 2025 goals.](#2024-12-12-meeting-summary)| [video](https://us02web.zoom.us/rec/share/XLYqWl-SuqhWB8BvudCHewjB-ds60wD6AyDAafxVB0SSKdm4PBbCKm0bTiY_xYRy.4SVCRR3yzrsJ2w4c)|[transcript](../../meetings/2024-12-12-Recording.txt)|
@@ -73,6 +75,94 @@ Previous meeting dates, recordings, transcripts, and minutes are summarised belo
 |2023-12-14|[The meeting focused on revising the structure of Recommendation 49, enhancing communication strategies, inviting contributions, and planning technical content development for implementation, with follow-up actions and scheduling outlined.](#2023-12-14-meeting-summary)| [video](https://us02web.zoom.us/rec/share/gh8BWTuMrZL0TOka76YVHwbZ_ZTIPhCJTn4LJv7YbxhlK4ZOudb24I3J9t9m9zCE.v6Di5lRXOLHSLQMy)|[transcript](../../meetings/2023-12-14-Recording.txt)|
 |2023-11-30| [The meeting focused on refining communication strategies and restructuring Recommendation 49 to align with previous UN recommendations, emphasizing flexibility, implementability, and stakeholder engagement.](#2023-11-30-meeting-summary)|[video](https://us02web.zoom.us/rec/share/3QJpW_xq7ljVf5UTWKtz_gCYrTO6cP5ZlsNZKhNccA0bY9iSfPcaFP6crO7jlFg.uotFEZa-l-bUgyI9)|[transcript](../../meetings/2023-11-30-Recording.txt)|
 
+## 2025-02-06 Meeting Summary
+
+**Chair:** Steve (Speaker 1)  
+**Participants:** David (Speaker 6), Nancy (Speaker 7), Zach (Speaker 4), Virginia (Speaker 2), Clary (Speaker 7), Marcus (Speaker 5), and others  
+
+---
+
+#### **Key Topics Discussed:**  
+
+**1. Opening Remarks**  
+- **Steve** welcomed participants, reminding them that this is a **UNTP meeting** and that contributions are **UN intellectual property (IP)**.  
+- **Meeting was recorded**, with no objections raised.  
+
+---
+
+#### **2. Change Requests & Technical Updates**  
+
+**Identity Resolver Page Updates**  
+- **Steve** walked through the process of how identifiers (product, facility, business) are resolved to find additional data (e.g., digital product passports).  
+- The page was reviewed to ensure it supports **existing identifier schemes** while accommodating **decentralized identifiers**.  
+- **Key Discussion Points:**
+  - **David** raised concerns about persistence of product identifiers for **circularity** (e.g., for recycled materials).  
+  - **Steve** clarified that the document **focuses on resolving identifiers rather than defining data carriers** but acknowledged that **traceability extensions** address linkage between raw materials and finished products.  
+  - **Nancy** questioned the inclusion of **glyph identifiers**, and **Steve** clarified that examples were provided **without preference**.  
+  - **Virginia** suggested improving the diagram wording to **clearly show that different identifier schemes are supported**.  
+  - **Zach** proposed creating a **ticket to further discuss identifier persistence** in future updates.  
+
+**Verifiable Credentials Specification Update**  
+- **Ashley** proposed a change requiring **version 2.0** of the verifiable credentials specification instead of allowing both versions 1.1 and 2.0.  
+- **Technical team (Patrick, Nis)** had reviewed and approved the change, with no strong objections from others.  
+- **Decision:** **PR approved** to enforce the use of **Verifiable Credentials version 2.0**.  
+
+**New Implementation Commitment**  
+- **K4 Security (Korea)** expressed commitment to implementing UNTP.  
+- **Steve** verified their legitimacy and **no objections were raised** to adding them to the implementation list.  
+
+---
+
+#### **3. Implementation Guidance Page**  
+- **Steve** introduced a new draft page to help organizations navigate the implementation of **UNTP**.  
+- **Five-Step Implementation Framework** was proposed:
+  1. Assess the **business case** for implementation.  
+  2. Identify **relevant pages** and register **intent to implement**.  
+  3. Choose **software solutions** or ask vendors for support.  
+  4. Run **pilot tests** and refine implementation.  
+  5. Scale up.  
+
+**Key Discussion Points:**  
+- **Clary** suggested adding a section for **consulting and implementation services** to assist companies.  
+- **John** proposed including a section on **long-term governance** for managing UNTP extensions.  
+- **Virginia** recommended promoting **awareness of UNTP among SMEs**, encouraging them to request **UNTP-compatible software**.  
+- **Marcus** raised the question of whether software vendors should have **branding or certification** for implementing UNTP.  
+- **Steve, Virginia, and Zach** discussed the feasibility of an **accreditation or certification** program but agreed it would likely be managed by external certifiers, not the UN.  
+
+**Decision:**  
+- PR for **Implementation Guidance Page to be reviewed and merged**.  
+- A **ticket will be created** for future discussions on **certification and branding** for software vendors.  
+
+---
+
+#### **4. Certification and Standards Governance**  
+- Discussion on **who should maintain long-term governance of industry extensions** (e.g., Australian Agriculture Traceability Protocol - AATP).  
+- **Steve** proposed that **National Standards Bodies (NSBs)** (e.g., **Standards Australia, Canadian Standards Authority**) could be a good home for maintaining **industry-specific extensions**.  
+- **Virginia** and **Zach** agreed that **commercial certification bodies (e.g., SGS)** could handle **third-party accreditation** instead of the UN.  
+- **Zach** suggested forming a **working group** to explore governance models.  
+
+**Decision:**  
+- **A ticket will be created** to explore a **UNTP Certification & Accreditation Framework**.  
+
+---
+
+###% **5. Closing Remarks**  
+- **Steve** noted that **open issues had increased** from **50 to 81**, urging participants to **discuss issues between meetings** rather than waiting for calls.  
+- **Final call for comments**, with **Marcus** expressing interest in joining discussions on **Australian standards**.  
+- **Meeting adjourned**, and **minutes to be shared shortly**.  
+
+---
+
+#### **Next Steps & Action Items:**  
+✔ **Merge** approved PRs (Verifiable Credentials update, Implementation Guidance).  
+✔ **Create tickets** for:  
+   - **Persistence of identifiers discussion**.  
+   - **UNTP Certification & Accreditation Framework**.  
+   - **Improving implementation guidance** for SMEs.  
+✔ **Continue governance discussions** with **National Standards Bodies**.  
+✔ **Review open issues** and prioritize for resolution before the next meeting.  
+
+
 ## 2025-01-23 Meeting Summary
 
 **Date**: January 23, 2025  

website/docs/business-case/CommunityActivationProgram.md

@@ -7,7 +7,9 @@ import Disclaimer from '../\_disclaimer.mdx';
 
 <Disclaimer />
 
-# Introduction
+# Community Activation Program
+
+## Introduction
 
 The Community Activation Program (CAP) serves as a comprehensive framework and collaborative community designed to support industries in developing and implementing their own UNTP extension projects. Communities, supported by UNECE, continue to thrive long after the project is complete, aiding industries in adopting extensions and associated tools.
 
@@ -25,7 +27,7 @@ Starting a UNTP project requires careful consideration of specific foundational
 
 * **Funding mechanism**: Robust and sustainable funding is crucial for supporting the project’s initial phases, covering development, outreach, and pilot testing. This ensures that the project gains traction and delivers early successes to build momentum.
 
-# CAP delivers value to industries and creates a flywheel of adoption
+## CAP delivers value to industries and creates a flywheel of adoption
 
 Industry associations engaging with CAP to develop UNTP extensions benefit from:
 
@@ -41,7 +43,7 @@ As extension projects mature, they generate a self-sustaining flywheel effect. T
 
 ![](costbenefit.png)
 
-# CAP supports a structured approach to extension development and adoption
+## CAP supports a structured approach to extension development and adoption
 
 The CAP toolkit offers a proven, six-phase methodology:
 
@@ -57,7 +59,7 @@ The CAP toolkit offers a proven, six-phase methodology:
 
 [More on the methodology here.](https://uncefact.github.io/spec-untp/docs/tools-and-support/ImplementationPlans)
 
-# A successful UNTP extension project is a team effort
+## A successful UNTP extension project is a team effort
 
 UNTP extension projects thrive through collaboration with a wide range of stakeholders.
 ![Activation Flywheel](CommunityActivationFlywheel.png)
@@ -78,7 +80,7 @@ CAP member stakeholders bring unique needs and derive tailored benefits:
 
 * **UNECE**: Act as a global steward, offering governance frameworks that ensure alignment and interoperability across projects. Their involvement fosters cooperation, providing guidance that strengthens the foundation for sustainable and globally consistent practices.
 
-# A UNTP extension team requires specialist skills
+## A UNTP extension team requires specialist skills
 
 To deliver a successful extension project, teams require a range of specialist skills. In addition to deep industry knowledge brought by the industry association and its members, a project should have:
 
@@ -94,7 +96,7 @@ To deliver a successful extension project, teams require a range of specialist s
 
 * **UNTP extension knowledge**: Deep understanding of the UNTP framework is indispensable for designing and implementing extensions that meet global standards. Teams must navigate trade protocols, ensure data governance, and address technical interoperability challenges to deliver scalable and impactful solutions.
 
-# CAP membership provides access to valuable resources
+## CAP membership provides access to valuable resources
 
 As a member of the Community Activation Program, members can access a wide range of resources:
 
@@ -104,7 +106,7 @@ As a member of the Community Activation Program, members can access a wide range
 * **Collaboration networks**: Engaging with established UNTP extension programs offers valuable opportunities for shared learning and innovation. These networks allow new participants to benefit from the experiences of others, adapt proven methodologies, and align their projects with broader industry goals. Collaboration also strengthens the ecosystem, making it easier for new extensions to integrate seamlessly.  
 * **Software tools**: A suite of software solutions is available to support UNTP extension projects. These tools facilitate rigorous testing, ensure conformance with established standards, and simplify supply chain management processes. By automating critical workflows and enabling data interoperability, these tools reduce the complexity of project implementation and drive efficiency.
 
-# Starting a community is simple
+## Starting a community is simple
 
 * **Join the community**: Join the [UNTP chat channel](https://uncefact.slack.com/ssb/redirect) to connect with a UNTP leader and discuss your community needs. By joining the community, participants gain access to ongoing support, exclusive updates, and a global network of peers dedicated to advancing UNTP standards.
 

website/docs/specification/SustainabilityVocabularyCatalog.md

@@ -37,10 +37,26 @@ History of releases is available from the **[Version history](https://test.uncef
 
 ## Overview
 
-Web **vocabularies** are a means to bring consistent understanding of **meaning** to ESG claims and assessments throughout transparent value chains based on UNTP. There are hundreds of ESG standards and regulations around the world, each with dozens or hundreds of specific conformity **criteria**. Any given value chain from raw materials to finished product is likely to include dozens of passports and conformity credentials issued against any of thousands of ESG criteria. Without a consistent means to make sense of this data, UNTP would provide a means to discover a lot of data but no easy way to make sense of it. The UNTP defines a standard and extensible topic map (taxonomy) of ESG criteria and provides a mechanism for any standards authority, or national regulator, or industry association to map their specific terminology to the UNTP vocabulary.
+Web **vocabularies** are a means to bring consistent understanding of **meaning** to ESG claims and assessments throughout transparent value chains based on UNTP. There are hundreds of ESG standards and regulations around the world, each with dozens or hundreds of specific conformity **criteria**. Any given value chain from raw materials to finished product is likely to include dozens of passports and conformity credentials issued against any of thousands of ESG criteria. Without a consistent means to make sense of this data, UNTP would provide a means to discover a lot of data but no easy way to make sense of it. This specification describes a consistent way to structure sustainability claims (in product passports and facility records) as well as sustainability assessments (in conformity credentials). It also provides guidance to scheme owners about how to make their sustainability standards compatible with linked data digitalisation. 
 
+## Conceptual Model
 
-## UNTP Core Vocabulary
+The diagram shows how the sustainability vocabulary catalog works with UNTP credentials such as product passports, facility records, and conformity credentials to bring unambiguous meaning to sustainability claims and assessments. 
+
+* Schemes (Grey): There are thousands of national regulations and industry standards that address sustainability of products, facilities, and organisations. Each one typically contains multiple auditable criteria. These are governed by the the government or industry authorities that define them.  UNTP does not seek to create any new schemes or regulations but rather to provide a means to ensure that these standards and regulations can be unambiguously referenced by digital credentials. This requires each individual criteria to have a globally unique identifier (a URI). 
+* DPP / DFR (green): The UNTP digital product passport (DPP) provides a means for a manufacturer or brand owner to list multiple sustainability claims for a given identified product. Similarly a UNTP digital facility record (DFR) provides the same capability but for facilities such as farms, mine-sites, processing plants, or manufacturing sites. Each claim may reference a sustainability criteria defined by a regulator or an industry standard.  
+* DCC (brown): The UNTP digital conformity credential (DCC) provides a means for a second or third party to list independent assessments of specific products or facilities against the same conformity criteria. For a DCC to verifiably support a claim in a DPP, the identifier of the criteria and supporting regulation / standard must match. Therefore it is important that both the manufacturer issuing the DPP and the auditor issuing the DCC use the same identifier for the sustainability criteria.  
+
+![Sustainability Vocabulary Catalog](SustainabilityVocabularyCatalog.png)
+
+The purpose of the sustainability vocabulary catalog (SVC) is to reduce the risk of misalignment between claims in DPPs and assessments in DCCs and also to provide a way to group similar criteria across different schemes. The SVC has three components
+
+* A catalog of schemes with relevant metadata including geographic coverage, industry sector, and governance type.
+* A recommended naming convention for criteria URIs that may be used by scheme owners to define their criteria identifiers (URIs).
+* A sustainability typology that can be used to classify criteria from different schemes. 
+
+
+## Claims and Assessments
 
 The UNTP core vocabulary defines the uniquely identified linked data entities such as Product, Location, Facility, Party, Standard, Regulation, Criteria, Declaration, Attestation, Endorsement. These entities provide the building blocks for construction of Digital Product Passports and Digital Conformity Credentials.
 
@@ -180,8 +196,8 @@ The conformity Information structure in the DPP is an array of UNTP `Declaration
 
 ## Sustainability Vocabulary Catalog
 
-The sustainability vocabulary catalog is designed to provide a reference-able digital library of sustainability conformity standards, regulations, and criteria that can be used as an allowed set of terms to use in conformity declarations. The library also aims to provide a mechanism for mutual recognition of conformity criteria between different regulations and standards. 
+The sustainability vocabulary catalog is designed to provide a reference-able digital library of sustainability conformity standards, regulations, and criteria that can be used as an allowed set of terms to use in conformity declarations. 
 
-TBA
+TBD