Page Comparison

10

Admin

IPR Review

25

Admin

• Name Change

  • Cleaning up web pages, please help out.

    • Review (before) and discuss home page for content, also roadmap https://kantara.atlassian.net/wiki/spaces/WA/overview?homepageId=2916356

  • Suggest a brief blog on name change.

    • This overview from Mark can do that, just put this out on Kantara’s blog and point to it?

      • Edit if you like, at least take a look at the overview

      • ANCR Notice Credentials for Digital Transparency & Privacy

• IPR Review

  • Updated home page wiki links

  • Option Patent and Copyright Reciprocal Royalty Free with Opt-Out to (RAND) This also covers the steps for the differenent levels and stages of Kantara publications. Right now we are at Draft Technical Specification, and shortly to Initial Draft Technical Specification, and Final Draft Technical Specification. Interestingly and importantly it includes the opportunity to implement a fully compliant implementation. This is where the code of conduct can be included and well as the requirement for conformance measurement.

• Name Change

  • Cleaning up web pages, please help out.

  • Suggest a brief blog on name change.

2025

TPI - Roadmap

Specification -

Aug 2 - Outline of TPI - Conformance specification, references relationship to code of conduct.

Aug 16 -Internal Final Draft Specification

Aug 23 - Initial Draft Technical Specification by WG released to LC and wider community.

10

TPi - Code of Conduct

• Developed via GItHub

• DTL-ANCR GitHub

  • Template

• "Fully Compliant Implementation" shall mean: (a) an implementation of a Corporation Recommendation Technical Specification which supports or implements all of the portions of that Corporation Recommendation Technical Specification defined by that Corporation Recommendation Technical Specification as being "Required"; or (b) an implementation of an optional portion of a Corporation Recommendation Technical Specification or optional Corporation Recommendation Technical Specification which supports all portions defined by that optional portion of the Corporation Recommendation Technical Specification or that optional Corporation Recommendation Technical Specification as being "Required"; and, in each instance, (c) an implementation of all portions of a Corporation Recommendation Technical Specification required for a specific type of product or component thereof.

• Consensus protocolGit Hub Repo

• Overview (Mark)

• Language in license requirement calls for fully compliant implementation in order to be able to use the TPIs.

• The Code of Conduct can provide this as a Consensus Protocol.