Markdown Version | Recording 1 | Recording 2

Session Date/Time: 27 Sep 2023 15:40

ASDF

Summary

The ASDF working group met for a virtual interim to process comments received during the Working Group Last Call (WGLC) of draft-ietf-asdf-sdf-base-15. The discussion primarily focused on addressing terminology inconsistencies, clarifying document evolution, and editorial improvements identified by a key review. A significant decision was made to remove all version numbers (e.g., SDF 1.0, 1.1) from the document, referring to it as "base SDF" moving forward. The group also planned for an additional round of targeted external reviews and scheduled a future interim to discuss the re-chartering and scope of other ASDF-related documents.

Key Discussion Points

• Meeting Logistics: The meeting started later than planned due to issues with MeetEcho links and participant availability (e.g., Michael Coster attending a W3C meeting). Participants were reminded of IETF procedures, the Note Well, and best practices for using MeetEcho.
• Working Group Last Call (WGLC) Review:
  • draft-ietf-asdf-sdf-base-15 underwent WGLC from September 4th to 20th.
  • A single, comprehensive review was provided by Christian Heinberg, approaching the document from a new reader's perspective, which proved highly valuable.
  • Most issues identified have associated pull requests on the GitHub repository, with a few remaining open tasks.
• Proposed Changes and Improvements:
  • Consistent Language:
    • Clarified use of "object" to distinguish between JSON objects (now "maps") and SDF objects (Issue #119).
    • Differentiated "thing" (general concept) from "SDF thing" (aggregate structure), reducing references to "Internet of Things" (IoT) to avoid artificial terminology fences (Issue #121).
    • Replaced "SDF file" with "SDF document" throughout the text (Issue #116), with a pending action to add this to the terminology section.
  • Missing Details:
    • Added a pointer to the idiom of returning an action resource for ongoing actions, linking to SDF type link for further extension (Issue #120).
  • SDF Evolution:
    • Clarified the evolution of SDF, naming the current specification "base SDF." Extensions are to be made via existing Registries or the feature quality mechanism, rather than new document versions (Issue #125).
    • Provided a more explicit definition of "affordances" to improve clarity for new readers.
  • Editorial Chores:
    • Standardized references to JSON Schema (draft-04 and draft-07 for both base and validation specs).
    • Clarified the connotation of "state" to avoid confusion with "state machine" concepts.
    • Outstanding Issues:
      • Refining the usage of the term "instance" (identified as a "significant surgery" affecting ~20 instances in the document).
      • Adding terminology entries for "SDF model" and "SDF document."
• Discussion on Versioning (SDF 1.0/1.1):
  • A lengthy discussion ensued regarding the presence of "SDF 1.0" and "SDF 1.1" references in the document and CDDL.
  • Consensus: The group agreed to remove all such version references to avoid future confusion. The published document will be known simply as "base SDF." Subsequent developments will be considered extensions or new, distinct specifications, following a model similar to CBOR (RFC 7049 to RFC 8949).
  • The intent is to provide a few sentences in the introduction explaining this change management philosophy.
• Future Work and Re-chartering:
  • Discussion touched upon the other ASDF-related documents (links, relations, instances, protocol bindings/mappings).
  • The working group anticipates needing to re-charter to continue work on these additional documents after the base SDF specification is published.
  • Consideration was given to how "quality namespaces" for specific ecosystems (e.g., OMA) or best practice guides might fit, noting that some might be handled via IANA registries, independent submissions, or even potentially within the research group.

Decisions and Action Items

• Decision: The draft-ietf-asdf-sdf-base document will remove all references to "SDF 1.0" and "SDF 1.1" from its text and CDDL. The document will be referred to as "base SDF," and future evolution will occur through extensions or new specifications without incremental version numbers.
• Decision: An additional round of targeted external reviews of draft-ietf-asdf-sdf-base-16 will be conducted to gather further "new reader" perspectives from the ecosystem.
• Action Item: Karsten to complete the remaining open issues (refining "instance" usage, adding terminology for "SDF model" and "SDF document") and publish draft-ietf-asdf-sdf-base-16 by Monday, October 2nd.
• Action Item: Michael (chair) to identify and contact potential external reviewers for draft-ietf-asdf-sdf-base-16, aiming for reviews to be submitted to the mailing list within 10 days of the -16 publication (i.e., by October 12th).
• Action Item: Chairs to schedule an additional virtual interim meeting for Wednesday, October 25th, at 9 AM Pacific / 16:00 UTC, to discuss the scope and future of other ASDF documents (e.g., links, relations, instances, protocol bindings/mappings) and their implications for a potential re-chartering of the working group.

Next Steps

1. October 2nd (approx.): Publication of draft-ietf-asdf-sdf-base-16.
2. October 2nd - October 12th: Period for targeted external reviews of draft-ietf-asdf-sdf-base-16.
3. October 12th - October 19th: Process any new reviews received and publish draft-ietf-asdf-sdf-base-17 (target submission by October 19th for IETF 118 deadline).
4. Prepare Shepherd's Report: For submission to the IESG.
5. October 25th (9 AM Pacific / 16:00 UTC): Virtual interim meeting to discuss future work items, specific ASDF companion documents, and preliminary proposals for the ASDF WG re-chartering.
6. IETF 118 (Prague): A portion of the ASDF WG session will be dedicated to discussing the re-chartering process and the path forward for other ASDF-related documents, including a brief overview of "base SDF."

Session Date/Time: 27 Sep 2023 15:40

ASDF

Summary

The ASDF working group met for a virtual interim to process comments received during the Working Group Last Call (WGLC) of draft-ietf-asdf-sdf-base-15. The discussion primarily focused on addressing terminology inconsistencies, clarifying document evolution, and editorial improvements identified by a key review. A significant decision was made to remove all version numbers (e.g., SDF 1.0, 1.1) from the document, referring to it as "base SDF" moving forward. The group also planned for an additional round of targeted external reviews and scheduled a future interim to discuss the re-chartering and scope of other ASDF-related documents.

Key Discussion Points

• Meeting Logistics: The meeting started later than planned due to issues with MeetEcho links and participant availability (e.g., Michael Coster attending a W3C meeting). Participants were reminded of IETF procedures, the Note Well, and best practices for using MeetEcho.
• Working Group Last Call (WGLC) Review:
  • draft-ietf-asdf-sdf-base-15 underwent WGLC from September 4th to 20th.
  • A single, comprehensive review was provided by Christian Heinberg, approaching the document from a new reader's perspective, which proved highly valuable.
  • Most issues identified have associated pull requests on the GitHub repository, with a few remaining open tasks.
• Proposed Changes and Improvements:
  • Consistent Language:
    • Clarified use of "object" to distinguish between JSON objects (now "maps") and SDF objects (Issue #119).
    • Differentiated "thing" (general concept) from "SDF thing" (aggregate structure), reducing references to "Internet of Things" (IoT) to avoid artificial terminology fences (Issue #121).
    • Replaced "SDF file" with "SDF document" throughout the text (Issue #116), with a pending action to add this to the terminology section.
  • Missing Details:
    • Added a pointer to the idiom of returning an action resource for ongoing actions, linking to SDF type link for further extension (Issue #120).
  • SDF Evolution:
    • Clarified the evolution of SDF, naming the current specification "base SDF." Extensions are to be made via existing Registries or the feature quality mechanism, rather than new document versions (Issue #125).
    • Provided a more explicit definition of "affordances" to improve clarity for new readers.
  • Editorial Chores:
    • Standardized references to JSON Schema (draft-04 and draft-07 for both base and validation specs).
    • Clarified the connotation of "state" to avoid confusion with "state machine" concepts.
    • Outstanding Issues:
      • Refining the usage of the term "instance" (identified as a "significant surgery" affecting ~20 instances in the document).
      • Adding terminology entries for "SDF model" and "SDF document."
• Discussion on Versioning (SDF 1.0/1.1):
  • A lengthy discussion ensued regarding the presence of "SDF 1.0" and "SDF 1.1" references in the document and CDDL.
  • Consensus: The group agreed to remove all such version references to avoid future confusion. The published document will be known simply as "base SDF." Subsequent developments will be considered extensions or new, distinct specifications, following a model similar to CBOR (RFC 7049 to RFC 8949).
  • The intent is to provide a few sentences in the introduction explaining this change management philosophy.
• Future Work and Re-chartering:
  • Discussion touched upon the other ASDF-related documents (links, relations, instances, protocol bindings/mappings).
  • The working group anticipates needing to re-charter to continue work on these additional documents after the base SDF specification is published.
  • Consideration was given to how "quality namespaces" for specific ecosystems (e.g., OMA) or best practice guides might fit, noting that some might be handled via IANA registries, independent submissions, or even potentially within the research group.

Decisions and Action Items

• Decision: The draft-ietf-asdf-sdf-base document will remove all references to "SDF 1.0" and "SDF 1.1" from its text and CDDL. The document will be referred to as "base SDF," and future evolution will occur through extensions or new specifications without incremental version numbers.
• Decision: An additional round of targeted external reviews of draft-ietf-asdf-sdf-base-16 will be conducted to gather further "new reader" perspectives from the ecosystem.
• Action Item: Karsten to complete the remaining open issues (refining "instance" usage, adding terminology for "SDF model" and "SDF document") and publish draft-ietf-asdf-sdf-base-16 by Monday, October 2nd.
• Action Item: Michael (chair) to identify and contact potential external reviewers for draft-ietf-asdf-sdf-base-16, aiming for reviews to be submitted to the mailing list within 10 days of the -16 publication (i.e., by October 12th).
• Action Item: Chairs to schedule an additional virtual interim meeting for Wednesday, October 25th, at 9 AM Pacific / 16:00 UTC, to discuss the scope and future of other ASDF documents (e.g., links, relations, instances, protocol bindings/mappings) and their implications for a potential re-chartering of the working group.

Next Steps

1. October 2nd (approx.): Publication of draft-ietf-asdf-sdf-base-16.
2. October 2nd - October 12th: Period for targeted external reviews of draft-ietf-asdf-sdf-base-16.
3. October 12th - October 19th: Process any new reviews received and publish draft-ietf-asdf-sdf-base-17 (target submission by October 19th for IETF 118 deadline).
4. Prepare Shepherd's Report: For submission to the IESG.
5. October 25th (9 AM Pacific / 16:00 UTC): Virtual interim meeting to discuss future work items, specific ASDF companion documents, and preliminary proposals for the ASDF WG re-chartering.
6. IETF 118 (Prague): A portion of the ASDF WG session will be dedicated to discussing the re-chartering process and the path forward for other ASDF-related documents, including a brief overview of "base SDF."