[Asdf] Roman Danyliw's No Objection on charter-ietf-asdf-00-03: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 07 October 2020 19:01 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: asdf@ietf.org
Delivered-To: asdf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF513A1304; Wed, 7 Oct 2020 12:01:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: asdf-chairs@ietf.org, asdf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <160209731074.26116.1051344896376154622@ietfa.amsl.com>
Date: Wed, 07 Oct 2020 12:01:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/eW5EgG-7-q9N0MyY96KnRE0g0Eg>
Subject: [Asdf] Roman Danyliw's No Objection on charter-ietf-asdf-00-03: (with COMMENT)
X-BeenThere: asdf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" <asdf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/asdf>, <mailto:asdf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/asdf/>
List-Post: <mailto:asdf@ietf.org>
List-Help: <mailto:asdf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/asdf>, <mailto:asdf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2020 19:01:51 -0000
Roman Danyliw has entered the following ballot position for charter-ietf-asdf-00-03: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-asdf/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- To revisit my two items of feedback from the initial charter review: ** What is "Thing Interaction and Data Modelling"? ** What is currently outstanding to make SDF “IETF quality”? I worry that the text currently reads as “start with SDF and make it better”. Here is text that could address those: OLD The objective of the ASDF working group is to develop SDF to an IETF-quality specification for Thing Interaction and Data Modelling, working with experts from OneDM and its contributing organizations. On the way to that specification, further functionality requirements will be addressed that emerge in the usage of SDF for model harmonization. The ASDF WG will work closely with the CBOR WG, home of the CDDL specification. NEW The objective of the ASDF working group is to develop a standards-track SDF specification for thing interaction and data modelling. In the course of developing this specification, further functional requirements that emerge from the model harmonization will be addressed. The ASDF WG will work with the experts from OneDM and its contributing organization. In the IETF, it will work closely with the CBOR WG, home of the CDDL specification. Explanation of the edit proposed edit: -- s/an IETF-quality specification/standards-track specification/ which speaks more concretely the quality bar expected -- s/Thing Interaction and Data Modelling/thing interaction and data modeling/ because none of these are proper nouns. I got confused in the initial charter review because the capitalization made it read like this was a formal name for something (proper noun) -- s/working with experts from OneDM and its contributing organizations// because this paragraph should describe what the WG is doing. The reference to OneDM and contribution organization should be noted with the rest of partners (in the next paragraph). -- s/On the way to that specification, further functionality requirements will be addressed that emerge in the usage of SDF for model harmonization/ In the course of developing this specification, further functional requirements that emerge from the model harmonization will be addressed/ to make clear the source of the functional requirements and why they can’t be articulated now. If the basis of how any deconfliction will be done can be noted, this would be helpful (e.g., minimize disruptive change across the existing models in the ecosystem now)
- [Asdf] Roman Danyliw's No Objection on charter-ie… Roman Danyliw via Datatracker
- Re: [Asdf] Roman Danyliw's No Objection on charte… Niklas Widell
- Re: [Asdf] Roman Danyliw's No Objection on charte… Roman Danyliw
- Re: [Asdf] Roman Danyliw's No Objection on charte… Barry Leiba