Re: [Asdf] proposed charter revision

Hi all,

I too have read the proposed charter, and the text looks good to me. I am curious, what are the next steps in order for the charter to proceed?

Kind Regards,
Braeden
________________________________
From: ASDF <asdf-bounces@ietf.org> on behalf of Bart Brinckman (bbrinckm) <bbrinckm=40cisco.com@dmarc.ietf.org>
Sent: Tuesday, February 20, 2024 9:59 AM
To: Eliot Lear <lear@lear.ch>; Michael Richardson <mcr+ietf@sandelman.ca>; asdf@ietf.org <asdf@ietf.org>
Subject: Re: [Asdf] proposed charter revision

You don't often get email from bbrinckm=40cisco.com@dmarc.ietf.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Caution: This e-mail originated from outside of Philips, be careful for phishing.

Hi Eliot & Michael,

The proposed text looks good to me. Seen there was significant interest in the room in NIPC in IETF118, can we move forward with this?

Thanks,

Bart

On 11/12/2023, 14:49, "ASDF" <asdf-bounces@ietf.org> wrote:

Hi Michael,

This look good as far as it goes, and I suggest that you merge it so

that we have it as a base.  We discussed Non IP Control in Prague and

IMHO there was clearly interest in pursuing that use case.

I have created a PR on top of this to address the use case of non-IP

control.  Please see

https://github.com/elear/asdf-working-group-notes/blob/charter-revision-2023/charter-proposals/charter.md

for proposed text.

I've not specified the draft we presented as a starting point, but that

would be my general approach.

Eliot

On 09.12.2023 21:36, Michael Richardson wrote:

> https://github.com/ietf-wg-asdf/asdf-working-group-notes/pull/1

> contains a proposed revision to the charter.

>

> The resulting charter would look like:

>

>

> Background

> ----------

>

> 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 went through the IETF process, producing (draft-ietf-asdf-sdf).  This

> initial SDF Base document 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.

>

> 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 ASDF has developped 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 work 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 translations between IP and other

> transports.

>

> As work evolves, it will interact with the IRTF formal description techniques

> (FDT) Research Group.  ASDF will work with Thing-to-Thing Research Group

> (T2TRG) and its WISHI (Work on IoT Semantic/Hypermedia Interoperability,

> http://wishi.space<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.

>

>

>

>

>

--

ASDF mailing list

ASDF@ietf.org<mailto:ASDF@ietf.org>

https://www.ietf.org/mailman/listinfo/asdf

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.