Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Figure 1 - Identifier States. A component diagram showing the inputs and semantic counterparts of a balanced network model

...

Scope

The mission of the ISWG is to define a decentralized key management infrastructure (Inputs domain) and data capture architecture (Semantic domain) for Internet-scale deployment. The scope of the ISWG is to define specifications and best practices that bring cohesion to data entry (aka Inputs) and data capture (aka Semantic) processes and standards throughout the ToIP stack whether these standards are hosted at the Linux Foundation or external to it. Other working group activities will include creating template Requests for Proposal (RFPs) and additional guidance to utility and service providers regarding implementations in that capacity. This WG will be divided into Inputs and Semantic domain groups and may also organise Task Forces and Focus Groups to escalate the development of certain components if deemed appropriate by the majority of the WG members and in line with the overall mission of the ToIP Foundation.

Meetings

Schedule:

  • Inputs Group

US/EU: TBC

  • Semantics Group

US/EU: The ISWG meets weekly on a Tuesday from 09:00-10:00 PT / 17:00-18:00 UTC

Deliverables

  • Technical specifications for all core components required within the Inputs domain as defined by the Scope statement for Inputs Group.
  • Technical specifications for all core components required within the Semantic domain as defined by the Scope statement for Semantics Group.
  • Also check out the ToIP Deliverables document for high-level deliverables of the Trust over IP Foundation.

Chairs / Leads 

How to join

You can join the ISWG by signing up for the Foundation mailing list at lists.trustoverip.org. Our mailing list is inputs-and-semantics-wg@lists.trustoverip.org 

...

Figure 2 - Active State. A component diagram highlighting the Inputs domain within a balanced network model.

...

Scope of the Inputs Group

The mission of the Inputs group (ISWG-I) is to define a decentralized key management infrastructure that provides self-certifying identifier issuance underpinned by cryptographic one-way functions for Internet-scale deployment. The scope of this sub-group is to define specifications and best practices that bring cohesion to data entry processes and other Inputs standards throughout the ToIP stack, whether these standards are hosted at the Linux Foundation or external to it. Other sub-group activities will include creating template Requests for Proposal (RFPs) and additional guidance to utility and service providers regarding implementations in this domain. This sub-group may also organise Task Forces and Focus Groups to escalate the development of certain components if deemed appropriate by the majority of the sub-group members and in line with the overall mission of the ToIP Foundation.

...

  • Technical specifications for all core components required within the Inputs domain as defined by the Mission and Scope statement.
  • Also check out the ToIP Deliverables document for high-level deliverables of the Trust over IP Foundation.

...

Figure 3 - Passive State. A component diagram highlighting the Semantic domain within a balanced network model.

...

Scope of the Semantics Group

The mission of the Semantics group (ISWG-S) is to define a data capture architecture consisting of immutable schema bases and interoperable overlays for Internet-scale deployment. The scope of this sub-group is to define specifications and best practices that bring cohesion to data capture processes and other Semantic standards throughout the ToIP stack, whether these standards are hosted at the Linux Foundation or external to it. Other sub-group activities will include creating template Requests for Proposal (RFPs) and additional guidance to utility and service providers regarding implementations in this domain. The sub-group may also organise Task Forces and Focus Groups to escalate the development of certain components if deemed appropriate by the majority of the sub-group members and in line with the overall mission of the ToIP Foundation.

...

  • Technical specifications for all core components required within the Semantic domain as defined by the Mission and Scope.
  • Also check out the ToIP Deliverables document for high-level deliverables of the Trust over IP Foundation.

...