Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2024-10-01 01:05:54 -04:00
Code Issues Packages Projects Releases Wiki Activity

connect from identosphere

Browse Source
This commit is contained in:
⧉ infominer 2023-08-13 00:45:53 -04:00
parent fae0e0ff2d
commit cc7883c25a
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
_data/standards.csv
View File

@ -616,6 +616,9 @@ OpenID Connect,OpenID,ABConnectWG,,,,,,,,​​First Implementer’s Drafts of O
OpenID Connect,OpenID,ABConnectWG,,Rodriguez Fernandez,,,,,,OpenID Connect Client-Initiated Backchannel Authentication Flow – Core 1.0,"OpenID Connect Client Initiated Backchannel Authentication Flow is an authentication flow like OpenID Connect. However, unlike OpenID Connect, there is direct Relying Party to OpenID Provider communication without redirects through the user's browser. This specification has the concept of a Consumption Device (on which the user interacts with the Relying Party) and an Authentication Device (on which the user authenticates with the OpenID Provider and grants consent). This specification allows a Relying Party that has an identifier for a user to obtain tokens from the OpenID Provider. The user starts the flow with the Relying Party at the Consumption Device, but authenticates and grants consent on the Authentication Device",,https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html,,Specification,,,Working Group,,,,,,,,2021-08-01,,,,,,,,,,,,,
OpenID Connect,OpenID,ABConnectWG,,Oliver Terbu,,,,,,OpenID Connect for Verifiable Presentations,This specification defines an extension of OpenID Connect to allow presentation of claims in the form of W3C Verifiable Credentials as part of the protocol flow in addition to claims provided in the id_token and/or via UserInfo responses.,,https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-08.html,,Specification,,,Working Group,,,,,,,,2022-01-28,,,,,,,,,,,,,
OpenID Connect,OpenID,ABConnectWG,,Kristina Yasuda,,,,,,Self-Issued OpenID Provider v2,"This specification extends OpenID Connect with the concept of a Self-Issued OpenID Provider (Self-Issued OP), an OP which is within the End-User's local control. End-Users can leverage Self-Issued OPs to authenticate themselves and present claims directly to the RPs. This allows users to interact with RPs directly, without relying on third-party providers or requiring the End-User to operate their own hosted OP infrastructure.",,https://openid.net/specs/openid-connect-self-issued-v2-1_0-07.html,,Specification,,,Working Group,,,,,,,,2022-01-28,,,,,,,,,,,,,
OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect for Identity Assurance 1.0,"This specification defines an extension to OpenID Connect [OpenID] for providing Relying Parties with identity information, i.e., Verified Claims, along with an explicit statement about the verification status of these Claims (what, how, when, according to what rules, using what evidence). This specification is aimed at enabling use cases requiring strong assurance, for example, to comply with regulatory requirements such as Anti-Money Laundering laws or access to health data, risk mitigation, or fraud prevention.",,https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html,,Specification,,,Working Group,,,,,,,,2022-08-19,,,,,,,,,,,,,
OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect for Identity Assurance – Overview & Call to Action,"OpenID Connect for Identity Assurance is primarily focussed on addressing use-cases where the details of the assurance process used to verify and validate the end-users identity need to be explicitly communicated.<br><br>The working group believes it’s a good fit for account opening, staff on-boarding, account recovery and access to restricted services where communication of how the underlying identity was established is needed.",,https://openid.net/oidc4ida-overview-call-to-action/,,Post,,,Working Group,,,,,,,,2022-08-25,,,,,,,,,,,,,
OpenID Connect,OpenID,ABConnectWG,,,,,,,,OpenID Connect Extended Authentication Profile (EAP) ACR Values 1.0,"This specification enables OpenID Connect Relying Parties to request that specific authentication context classes be applied to authentications performed and for OpenID Providers to inform Relying Parties whether these requests were satisfied. Specifically, an authentication context class reference value is defined that requests that phishing-resistant authentication be performed and another is defined that requests that phishing-resistant authentication with a hardware-protected key be performed. These policies can be satisfied, for instance, by using W3C scoped credentials or FIDO authenticators. ",,https://openid.net/specs/openid-connect-eap-acr-values-1_0-01.html,,Specification,,,Working Group,,,,,,,,2021-10-03,,,,,,,,,,,,,
OpenID Connect,Self Issued,,,Mike Jones,,,,,,The OpenID Connect Logout specifications are now Final Specifications,The OpenID Connect Logout specifications are now Final Specifications<br>Thanks to all who helped us reach this important milestone! This was originally [announced on the OpenID blog](https://openid.net/2022/09/12/the-openid-connect-logout-specifications-are-now-final-specifications/).,,https://self-issued.info/?p=2298,,Post,,,Working Group,,,,,,,,2022-09-27,,,,,,,,,,,,,
OpenID Connect,IDCommons,,,"Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker",,,,,IIW,Use-cases: OIDC for Verifiable Credentials - How do you want to use Identity Provider you control?,"We talk about users controlling their own identities, but what does it really mean in “real-life”?<br><br>For example, in OpenID Connect, what are the real-life use-cases and concrete needs to move from Identity Providers offered by Identity Companies to users controlling their own Identity Provider",,https://iiw.idcommons.net/12G/_Use-cases:_OIDC_for_Verifiable_Credentials_-_How_do_you_want_to_use_Identity_Provider_you_control%3F,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-07,,,,,,,,,,,,,
OpenID Connect,IDCommons,,https://www.slideshare.net/TorstenLodderstedt/openid-connect-for-w3c-verifiable-credential-objects,"Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker",,,,,IIW,OpenID Connect for W3C Verifiable Credential Objects,Have been incubated in OpenID Foundation and DIF’s joint Self-Issued OpenID Provider WG - contact Kristina ([kristina.yasuda@microsoft.com](mailto:kristina.yasuda@microsoft.com) for participation details),,https://iiw.idcommons.net/2F/_OpenID_Connect_for_W3C_Verifiable_Credential_Objects,,Session Notes,,,Verifiable Credentials,,,,,,,,2021-05-06,,,,,,,,,,,,,
@ -644,8 +647,8 @@ KERI,Harvard,,,Doc Searls,,,,,,On KERI: a way not to reveal more personal info t
KERI,Jolocom,,,,Jolocom,,,,,How KERI tackles the problem of trust,"In contrast to blockchain or central registry-based trust systems, KERI is based on a hash-chain data structure called a ‘key event receipt log’ (KERL). Conceptually, it’s similar in some ways to the Peer DID Method specification, except that its data model is a KERL rather than a DID document. And while KERI can be used as a DID method, it is fundamentally not reliant on any of the DID specifications and can be used in many other contexts as well. In particular, it is also useful for Internet of Things (IoT) networks and other security-conscious, low-resource use cases.",,https://jolocom.io/blog/how-keri-tackles-the-problem-of-trust/,,Post,,,About,,,,,,,,2020-10-15,,,,,,,,,,,,,
KERI,Definitely Identity,,,,Samuel Smith,,,,,"Tim talks with Sam Smith, creator of KERI","In this episode, we explore the Key Event Receipt Infrastructure (KERI)and how it relates to decentralized identity. We also touch topics in the white paper: trust domains, self-certifying identifiers, architectural implications, and more.",,https://podcasts.apple.com/ca/podcast/definitely-identity-episode-14-with-sam-smith/id1496565155?i=1000494102345,,episode,,,About,,,,,,,,2020-10-08,,,,,,,,,,,,,
KERI,Human Colossus Foundation,,,,,,,,,Thinking of DID? KERI On,"The current generation of DIDs has introduced an innovative approach to digital identifiers, which has triggered the SSI movement. However, the inclusion of the method space in the DID syntax has led to fragmentation and weak security properties of the identifier type. These known method-space issues give the community impetus to redress them. In light of these innovative developments, now is the time to embrace KERI as an improved interoperable and secure solution for digital identity.","In this blog post, we address DIDs security from the viewpoint of KERI (Key Event Receipt Infrastructure), a novel, simple, and improved DKMS (Decentralized Key Management System) solution for digital identifiers. KERI provides a unifying solution to DID document authentication and resolution that will prove invaluable to use cases where security and interoperability are essential (e.g., for global supply chains and humanitarian applications).",https://humancolossus.foundation/blog/thinking-of-did-keri-on,,Post,,,About,,,,,,,,2021-01-27,,,,,,,,,,,,,
KERI,Gleif,,https://www.gleif.org/lei-solutions/gleifs-digital-strategy-for-the-lei/2022-06-28_lei-digital-strategy-current_version-focus-vlei_v0.17_work.pdf,,,,,,,LEI Digital Strategy,"The Global LEI System (GLEIS) has a unique opportunity to solve the problem of trust for legal entities on a global scale. It can enable digital transformation in a way that is interoperable, independent and autonomous. As a regulatory endorsed system overseen by the Regulatory Oversight Committee (ROC), the GLEIS is the only system that establishes a recognized, monitored and standardized global identity for legal entities that, whenever possible, is linked to the national ID system in that jurisdiction. The system is underpinned by open data, meaning any person or company can access the LEI and its associated reference data. The GLEIS also bridges traditional and online processes by serving as a tool to identify the counterparty in any transaction and can aggregate data on legal entities held in repositories.<br><br>GLEIF’s digital strategy for the LEI centers on two methods for cryptographically binding the LEI to its organization – digital certificates and Verifiable Credentials.","From banking to production and supply chain management, industries worldwide are adjusting to the digitization of processes and transactions. ",https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei,,Post,,,Organization,,,,,,,,2022-06-08,,,,,,,,,,,,,
KERI,IDCommons,,,,,,,,IIW,GLEIF vLEI with KERI,"The Global Legal Entity Identifier Foundation (GLEIF) proposes that the Legal Enitity Identifier (LEI) can be used to establish a chain of trust for organizational identity.<br><br>In this session, GLEIF shares plans and progress regarding its development program to create an ecosystem and credential governance framework, together with a technical supporting infrastructure, for a verifiable LEI (vLEI), a digitally verifiable credential containing the LEI.",,https://iiw.idcommons.net/20K/_GLEIF_vLEI_with_KERI,,Session Notes,,,Organization,,,,,,,,2021-05-07,,,,,,,,,,,,,
KERI,GLEIF,,https://www.gleif.org/lei-solutions/gleifs-digital-strategy-for-the-lei/2022-06-28_lei-digital-strategy-current_version-focus-vlei_v0.17_work.pdf,,,,,,,LEI Digital Strategy,"The Global LEI System (GLEIS) has a unique opportunity to solve the problem of trust for legal entities on a global scale. It can enable digital transformation in a way that is interoperable, independent and autonomous. As a regulatory endorsed system overseen by the Regulatory Oversight Committee (ROC), the GLEIS is the only system that establishes a recognized, monitored and standardized global identity for legal entities that, whenever possible, is linked to the national ID system in that jurisdiction. The system is underpinned by open data, meaning any person or company can access the LEI and its associated reference data. The GLEIS also bridges traditional and online processes by serving as a tool to identify the counterparty in any transaction and can aggregate data on legal entities held in repositories.<br><br>GLEIF’s digital strategy for the LEI centers on two methods for cryptographically binding the LEI to its organization – digital certificates and Verifiable Credentials.","From banking to production and supply chain management, industries worldwide are adjusting to the digitization of processes and transactions. ",https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei,,Post,,,Organization,,,,,,,,2022-06-08,,,,,,,,,,,,,
KERI,IDCommons,,,,GLEIF,,,,IIW,GLEIF vLEI with KERI,"The Global Legal Entity Identifier Foundation (GLEIF) proposes that the Legal Enitity Identifier (LEI) can be used to establish a chain of trust for organizational identity.<br><br>In this session, GLEIF shares plans and progress regarding its development program to create an ecosystem and credential governance framework, together with a technical supporting infrastructure, for a verifiable LEI (vLEI), a digitally verifiable credential containing the LEI.",,https://iiw.idcommons.net/20K/_GLEIF_vLEI_with_KERI,,Session Notes,,,Organization,,,,,,,,2021-05-07,,,,,,,,,,,,,
KERI,TOIP,,,,,,,,,ACDC (Authentic Chained Data Container) Task Force,The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that defines 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 supporting syntax of an ACDC.,,https://wiki.trustoverip.org/display/HOME/ACDC+%28Authentic+Chained+Data+Container%29+Task+Force,,page,,,Organization,,,,,,,,2021-01-19,,,,,,,,,,,,,
KERI,,Trusted Computing Group,,,,,,,,Trusted Computing Group,"The Trusted Computing Group (TCG) is a not-for-profit organization formed to develop, define and promote open, vendor-neutral, global industry specifications and standards, supportive of a hardware-based root of trust, for interoperable trusted computing platforms.TCG’s core technologies include specifications and standards for the Trusted Platform Module (TPM), Trusted Network Communications (TNC) and network security and self-encrypting drives. TCG also has work groups to extend core concepts of trust into cloud security, virtualization and other platforms and computing services from the enterprise to the Internet of Things.",,https://trustedcomputinggroup.org/,https://trustedcomputinggroup.org/wp-content/plugins/revslider/public/assets/assets/dummy.png,site,,,Organization,,,,,,,,,,,,,,,,,,,,,
KERI,Micro Controller Tips,,,Maria Guerra,,,,,,What is DICE architecture?,"DICE stands for Device Identifier Composition Engine, and it is a security standard created by the Trusted Computing Group (TCG) which has been addressing security issues for years. TCG announced the establishment of DICE Architecture, or DICE Architecture Work Group to address the need for increased security in the Internet of Things (IoT) therefore targeting products such as MCUs and systems on a chip (SoCs).",,https://www.microcontrollertips.com/what-is-dice-architecture-faq/,https://www.microcontrollertips.com/wp-content/uploads/2018/06/DICE-featured.jpg,faq,,,Organization,,,,,,,,2018-07-27,,,,,,,,,,,,,

1 main parent name supporting authors related location serving policy event title text description link image type status platform section sector industry market focus projects tech working group date github twitter youtube list feed discord crunchbase linkedin docs devtools app telegram forum
616 OpenID Connect OpenID ABConnectWG Rodriguez Fernandez OpenID Connect Client-Initiated Backchannel Authentication Flow – Core 1.0 OpenID Connect Client Initiated Backchannel Authentication Flow is an authentication flow like OpenID Connect. However, unlike OpenID Connect, there is direct Relying Party to OpenID Provider communication without redirects through the user's browser. This specification has the concept of a Consumption Device (on which the user interacts with the Relying Party) and an Authentication Device (on which the user authenticates with the OpenID Provider and grants consent). This specification allows a Relying Party that has an identifier for a user to obtain tokens from the OpenID Provider. The user starts the flow with the Relying Party at the Consumption Device, but authenticates and grants consent on the Authentication Device https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html Specification Working Group 2021-08-01
617 OpenID Connect OpenID ABConnectWG Oliver Terbu OpenID Connect for Verifiable Presentations This specification defines an extension of OpenID Connect to allow presentation of claims in the form of W3C Verifiable Credentials as part of the protocol flow in addition to claims provided in the id_token and/or via UserInfo responses. https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-08.html Specification Working Group 2022-01-28
618 OpenID Connect OpenID ABConnectWG Kristina Yasuda Self-Issued OpenID Provider v2 This specification extends OpenID Connect with the concept of a Self-Issued OpenID Provider (Self-Issued OP), an OP which is within the End-User's local control. End-Users can leverage Self-Issued OPs to authenticate themselves and present claims directly to the RPs. This allows users to interact with RPs directly, without relying on third-party providers or requiring the End-User to operate their own hosted OP infrastructure. https://openid.net/specs/openid-connect-self-issued-v2-1_0-07.html Specification Working Group 2022-01-28
619 OpenID Connect OpenID ABConnectWG OpenID Connect for Identity Assurance 1.0 This specification defines an extension to OpenID Connect [OpenID] for providing Relying Parties with identity information, i.e., Verified Claims, along with an explicit statement about the verification status of these Claims (what, how, when, according to what rules, using what evidence). This specification is aimed at enabling use cases requiring strong assurance, for example, to comply with regulatory requirements such as Anti-Money Laundering laws or access to health data, risk mitigation, or fraud prevention. https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html Specification Working Group 2022-08-19
620 OpenID Connect OpenID ABConnectWG OpenID Connect for Identity Assurance – Overview & Call to Action OpenID Connect for Identity Assurance is primarily focussed on addressing use-cases where the details of the assurance process used to verify and validate the end-users identity need to be explicitly communicated.<br><br>The working group believes it’s a good fit for account opening, staff on-boarding, account recovery and access to restricted services where communication of how the underlying identity was established is needed. https://openid.net/oidc4ida-overview-call-to-action/ Post Working Group 2022-08-25
621 OpenID Connect OpenID ABConnectWG OpenID Connect Extended Authentication Profile (EAP) ACR Values 1.0 This specification enables OpenID Connect Relying Parties to request that specific authentication context classes be applied to authentications performed and for OpenID Providers to inform Relying Parties whether these requests were satisfied. Specifically, an authentication context class reference value is defined that requests that phishing-resistant authentication be performed and another is defined that requests that phishing-resistant authentication with a hardware-protected key be performed. These policies can be satisfied, for instance, by using W3C scoped credentials or FIDO authenticators. https://openid.net/specs/openid-connect-eap-acr-values-1_0-01.html Specification Working Group 2021-10-03
622 OpenID Connect Self Issued Mike Jones The OpenID Connect Logout specifications are now Final Specifications The OpenID Connect Logout specifications are now Final Specifications<br>Thanks to all who helped us reach this important milestone! This was originally [announced on the OpenID blog](https://openid.net/2022/09/12/the-openid-connect-logout-specifications-are-now-final-specifications/). https://self-issued.info/?p=2298 Post Working Group 2022-09-27
623 OpenID Connect IDCommons Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker IIW Use-cases: OIDC for Verifiable Credentials - How do you want to use Identity Provider you control? We talk about users controlling their own identities, but what does it really mean in “real-life”?<br><br>For example, in OpenID Connect, what are the real-life use-cases and concrete needs to move from Identity Providers offered by Identity Companies to users controlling their own Identity Provider https://iiw.idcommons.net/12G/_Use-cases:_OIDC_for_Verifiable_Credentials_-_How_do_you_want_to_use_Identity_Provider_you_control%3F Session Notes Verifiable Credentials 2021-05-07
624 OpenID Connect IDCommons https://www.slideshare.net/TorstenLodderstedt/openid-connect-for-w3c-verifiable-credential-objects Oliver Terbu, Torsten Lodderstedt, Kristina Yasuda, Adam Lemmon, Tobias Looker IIW OpenID Connect for W3C Verifiable Credential Objects Have been incubated in OpenID Foundation and DIF’s joint Self-Issued OpenID Provider WG - contact Kristina ([kristina.yasuda@microsoft.com](mailto:kristina.yasuda@microsoft.com) for participation details) https://iiw.idcommons.net/2F/_OpenID_Connect_for_W3C_Verifiable_Credential_Objects Session Notes Verifiable Credentials 2021-05-06
647 KERI Jolocom Jolocom How KERI tackles the problem of trust In contrast to blockchain or central registry-based trust systems, KERI is based on a hash-chain data structure called a ‘key event receipt log’ (KERL). Conceptually, it’s similar in some ways to the Peer DID Method specification, except that its data model is a KERL rather than a DID document. And while KERI can be used as a DID method, it is fundamentally not reliant on any of the DID specifications and can be used in many other contexts as well. In particular, it is also useful for Internet of Things (IoT) networks and other security-conscious, low-resource use cases. https://jolocom.io/blog/how-keri-tackles-the-problem-of-trust/ Post About 2020-10-15
648 KERI Definitely Identity Samuel Smith Tim talks with Sam Smith, creator of KERI In this episode, we explore the Key Event Receipt Infrastructure (KERI)and how it relates to decentralized identity. We also touch topics in the white paper: trust domains, self-certifying identifiers, architectural implications, and more. https://podcasts.apple.com/ca/podcast/definitely-identity-episode-14-with-sam-smith/id1496565155?i=1000494102345 episode About 2020-10-08
649 KERI Human Colossus Foundation Thinking of DID? KERI On The current generation of DIDs has introduced an innovative approach to digital identifiers, which has triggered the SSI movement. However, the inclusion of the method space in the DID syntax has led to fragmentation and weak security properties of the identifier type. These known method-space issues give the community impetus to redress them. In light of these innovative developments, now is the time to embrace KERI as an improved interoperable and secure solution for digital identity. In this blog post, we address DIDs security from the viewpoint of KERI (Key Event Receipt Infrastructure), a novel, simple, and improved DKMS (Decentralized Key Management System) solution for digital identifiers. KERI provides a unifying solution to DID document authentication and resolution that will prove invaluable to use cases where security and interoperability are essential (e.g., for global supply chains and humanitarian applications). https://humancolossus.foundation/blog/thinking-of-did-keri-on Post About 2021-01-27
650 KERI Gleif GLEIF https://www.gleif.org/lei-solutions/gleifs-digital-strategy-for-the-lei/2022-06-28_lei-digital-strategy-current_version-focus-vlei_v0.17_work.pdf LEI Digital Strategy The Global LEI System (GLEIS) has a unique opportunity to solve the problem of trust for legal entities on a global scale. It can enable digital transformation in a way that is interoperable, independent and autonomous. As a regulatory endorsed system overseen by the Regulatory Oversight Committee (ROC), the GLEIS is the only system that establishes a recognized, monitored and standardized global identity for legal entities that, whenever possible, is linked to the national ID system in that jurisdiction. The system is underpinned by open data, meaning any person or company can access the LEI and its associated reference data. The GLEIS also bridges traditional and online processes by serving as a tool to identify the counterparty in any transaction and can aggregate data on legal entities held in repositories.<br><br>GLEIF’s digital strategy for the LEI centers on two methods for cryptographically binding the LEI to its organization – digital certificates and Verifiable Credentials. From banking to production and supply chain management, industries worldwide are adjusting to the digitization of processes and transactions. https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei Post Organization 2022-06-08
651 KERI IDCommons GLEIF IIW GLEIF vLEI with KERI The Global Legal Entity Identifier Foundation (GLEIF) proposes that the Legal Enitity Identifier (LEI) can be used to establish a chain of trust for organizational identity.<br><br>In this session, GLEIF shares plans and progress regarding its development program to create an ecosystem and credential governance framework, together with a technical supporting infrastructure, for a verifiable LEI (vLEI), a digitally verifiable credential containing the LEI. https://iiw.idcommons.net/20K/_GLEIF_vLEI_with_KERI Session Notes Organization 2021-05-07
652 KERI TOIP ACDC (Authentic Chained Data Container) Task Force The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that defines 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 supporting syntax of an ACDC. https://wiki.trustoverip.org/display/HOME/ACDC+%28Authentic+Chained+Data+Container%29+Task+Force page Organization 2021-01-19
653 KERI Trusted Computing Group Trusted Computing Group The Trusted Computing Group (TCG) is a not-for-profit organization formed to develop, define and promote open, vendor-neutral, global industry specifications and standards, supportive of a hardware-based root of trust, for interoperable trusted computing platforms.TCG’s core technologies include specifications and standards for the Trusted Platform Module (TPM), Trusted Network Communications (TNC) and network security and self-encrypting drives. TCG also has work groups to extend core concepts of trust into cloud security, virtualization and other platforms and computing services from the enterprise to the Internet of Things. https://trustedcomputinggroup.org/ https://trustedcomputinggroup.org/wp-content/plugins/revslider/public/assets/assets/dummy.png site Organization
654 KERI Micro Controller Tips Maria Guerra What is DICE architecture? DICE stands for Device Identifier Composition Engine, and it is a security standard created by the Trusted Computing Group (TCG) which has been addressing security issues for years. TCG announced the establishment of DICE Architecture, or DICE Architecture Work Group to address the need for increased security in the Internet of Things (IoT) therefore targeting products such as MCUs and systems on a chip (SoCs). https://www.microcontrollertips.com/what-is-dice-architecture-faq/ https://www.microcontrollertips.com/wp-content/uploads/2018/06/DICE-featured.jpg faq Organization 2018-07-27