Skip to content
Open
Changes from 6 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
9ce9c4b
initial rewrite of charter
mcr Nov 9, 2023
fb45bd5
remove "initial"
mcr Dec 10, 2023
9a4a03f
typo
mcr Dec 10, 2023
e872626
fix name of the RG
mcr Dec 10, 2023
489ff1c
fix typo
mcr Dec 10, 2023
fa0625e
slight rework to connect second paragraph to first paragraph listing …
mcr Mar 17, 2024
fa640b2
change by to in consultation with
mcr Apr 4, 2024
27e88ac
added milestones, revised some text
mcr Apr 29, 2024
4d2ac4d
added instances and types
mcr Apr 29, 2024
b15d93c
added blank lines for milestone list
mcr Apr 29, 2024
718e4ee
fill in sdftype document
mcr Apr 29, 2024
dd28941
additinal word smithing
mcr Apr 29, 2024
0cc7dda
update README to be useful
mcr Nov 9, 2023
5b3d302
typing nits
cabo Apr 29, 2024
ab3f83f
use US speling of modeling
cabo Apr 29, 2024
c445619
Clarify that location is an example of a potential non-affordance att…
cabo Apr 29, 2024
9402cee
Update milestone list
cabo Apr 29, 2024
97bd525
Merge pull request #2 from ietf-wg-asdf/charter-revision-2023-discuss…
mcr Apr 29, 2024
9c803ed
Structurally align milestones
cabo May 13, 2024
50a6bbc
Add instance spec milestone
cabo May 13, 2024
dbdbdd7
Merge pull request #3 from ietf-wg-asdf/charter-revision-2023-streamline
cabo May 13, 2024
e97e4bc
Merge branch 'charter-revision-2023' into charter-revision-2023-add-i…
cabo May 13, 2024
7ed8f45
Identify starting point of NIPC work
cabo May 13, 2024
0243338
Cover first three milestones in program of work
cabo May 13, 2024
d440637
Merge pull request #4 from ietf-wg-asdf/charter-revision-2023-add-ins…
mcr May 14, 2024
1d22c10
Merge pull request #5 from ietf-wg-asdf/charter-revision-2023-nipc-st…
mcr May 14, 2024
3454b9d
Merge pull request #6 from ietf-wg-asdf/charter-revision-2023-program…
mcr May 15, 2024
0b8f736
Merge branch 'main' into charter-revision-2023
cabo May 16, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 8 additions & 9 deletions charter-proposals/charter.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,18 @@
Background
----------

Data and interaction models of IoT devices today exhibit unneeded diversity between different industry ecosystem standards development organizations (SDOs), hindering interoperability across these ecosystems with little discernible benefit from the diversity. Early 2019, One Data Model (OneDM) was started to bring several IoT SDOs and IoT device and platform vendors together under a broad, multi-party liaison agreement, with a goal of arriving at a common set of data and interaction models that describe IoT devices. Ideally, for every class of IoT device, there is just a single model selected/created by the participating organizations, which everyone can adopt.
In 2019 One Data Model (OneDM) was started to bring several IoT SDOs and IoT device and platform vendors together under a broad, multi-party liaison agreement, with a goal of arriving at a common set of data and interaction models that describe IoT devices. After some exploratory work this resulted in a successful proposal to create the ASDF WG.

As a common language for writing down these models, the Semantic Definition Format (SDF, draft-onedm-t2trg-sdf) was created, which can represent IoT Things, their composition from reusable Objects, their Interaction Affordances (Properties, Actions, Events), and the data models relevant to describe these Affordances. SDF represents these models in JSON, enabling re-use of specification formats such as CDDL (RFC8610) and the formats proposed at json-schema.org and their tooling, for describing both the SDF format itself and the structure of the data to be modelled in SDF.
As a common language for writing down these models, the Semantic Definition Format went through the IETF process, producing (draft-ietf-asdf-sdf). This SDF Base specification has now reached WG Consensus, to be published. SDF represents these models in JSON, enabling re-use of specification formats such as CDDL (RFC8610) and the formats proposed at json-schema.org and their tooling, for describing both the SDF format itself and the structure of the data to be modelled in SDF.

By July 2020, some 200 models in SDF format have been contributed by participating ecosystems; new models are being submitted continually. Version 1.0 of the SDF specification was published on the OneDM github repository and as an Internet-Draft. OneDM is now focusing on consolidating the body of submitted models and developing processes for arriving at harmonized models that span different industry ecosystems in a common way; as expressed at the IETF 108 ASDF BoF, they look to the IETF for developing SDF 1.0 further into a high-quality specification.

The IETF also defines the YANG data modelling language (RFC 7950). YANG has a strong focus on modelling the management interface for network devices, using a fairly small set of network management protocols, whereas SDF is designed to span (and transitively unify) many existing interaction models already present. While data associated with a YANG schema can be serialized to a variety of wire formats (e.g., XML, JSON, CBOR, and others), the serialization is driven directly by the structure of the data models defined in YANG; there is no separate "protocol binding" step as in the use of SDF.

Conversely, SDF does not deal directly with serialization at all, modelling only the structure and semantics of the data being interchanged, hence leaving data serialization (and RPC semantics) to other standards, most likely defined by existing IoT SDOs.
SDF does not deal directly with serialization at all, modelling only the structure and semantics of the data being interchanged, hence leaving data serialization (and RPC semantics) to other standards, most likely defined by existing IoT SDOs.

The ASDF Working Group
----------------------

The objective of the ASDF working group is to develop SDF into a standards-track specification for thing interaction and data modelling. In the process of developing this specification, further functional requirements that emerge in the usage of SDF for model harmonization will be addressed.
The ASDF has developed SDF into a standards-track specification for thing interaction and data modelling. In the process of developing this specification, further functional requirements have emerged that can be addressed as extensions to the base SDF specification.

The ASDF WG will develop these extensions by working with experts from OneDM and its contributing organizations to extend SDF to cover aspects such as digital twin, mapping to other IoT SDOs, and gateway interactions translating between IP and other transports.

As work evolves, ASDF will observe and may want to interact with IRTF Research Groups such as the Usable Formal Methods Research Group (UFMRG). ASDF will work with Thing-to-Thing Research Group (T2TRG) and its WISHI (Work on IoT Semantic/Hypermedia Interoperability, http://wishi.space) program to engage researchers and other SDOs in this space, such as W3C Web of Things, which is working on Thing Models and related specifications.

The ASDF WG will work with experts from OneDM and its contributing organizations. In the IETF, it will work closely with the CBOR WG, home of the CDDL specification. It will also engage the still active mailing list of the concluded JSON WG. Recent proposals to form an IRTF formal description techniques (FDT) Research Group might lead to another collaboration partner. ASDF will work with Thing-to-Thing Research Group (T2TRG) and its WISHI (Work on IoT Semantic/Hypermedia Interoperability, http://wishi.space) program to engage researchers and other SDOs in this space, such as W3C Web of Things, which is working on Thing Models and related specifications.<