From nobody Fri Dec 4 10:23:30 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91083A0A83 for ; Fri, 4 Dec 2020 10:23:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smartthings.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iBsMDPJszcI for ; Fri, 4 Dec 2020 10:23:27 -0800 (PST) Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 574563A0A7E for ; Fri, 4 Dec 2020 10:23:27 -0800 (PST) Received: by mail-pj1-x1035.google.com with SMTP id iq13so3580560pjb.3 for ; Fri, 04 Dec 2020 10:23:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smartthings.com; s=google; h=from:mime-version:subject:message-id:date:to; bh=Uneblj31EXfRVxo5JjF0QcHiyoKUGpijwOZ9T+m+K1g=; b=QoukwIunQIScDq5gURqz6HjNK6VlhiIQl6j7ILRN+ubgme9d9SOWQKyRk9um9BjqT8 xqG3w7J5SNH1uLwxUJmN0mUAkJZwM4DqXpsc9UOf9MKpEb8H86/IGB7DVfANTU50UmwD ZbgXpmX/7dwDjBdq9LQfp4qsyXYIuAWnsQtpTz+oQYF9WZ9P0iimyGpp2ROiPp9FIR3O k5V6xtIgWIUoC4NFzHZzc1F+dVtvbx1w592OJxdXxQf4BLS0lL2wZ/HIPs1mOoAQs6uY uZFjNBJQsXUX53Ag84ZZngSTQLpImP5ENV0J+CX6DLBYAKNpgQ2Zh/eLOgp2eesNtWZ1 U1sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=Uneblj31EXfRVxo5JjF0QcHiyoKUGpijwOZ9T+m+K1g=; b=ZKCk+g+yjTlwHqii0gPjdHVmTiamMZ9jjq/Yo5xiK7PfsoEaQBAexeZ6KQotJUlZ3b eWNp/05fWapp/+5J47MEGB1UHjB8SzCBPmlZTTG8oYhmeFq5RWUfjdxbV+XEXJSwD6DU KjVB5Rlt8cvSJj6/TUo7HTeiOq/FkIp2QWdvWdZyO2smA6fr6hByaoqc0IzOuFOUiLRr uP6yu6yYLeQitsGHWzJYliS8dxLOOlQO+dN+rxrWPXWeyOmEZ+WAQzBsfgdgBeqRrn9M OS75mOuXgOlkYcfrjK6tpqADrIv4Viz55ZNCHlWE0+hcMYvlxDRjStA+semN+09m4Y85 2mfw== X-Gm-Message-State: AOAM532XPsHSd4tkBLx1z5cLpcVcLgYVnsfhQeLWuxJwEtYDkp6KDlLT IlDht3rig87IWSVlWqN71jtKdCvCVamQ46bgoa2yUybMobo7Op4G8+P/9awyeVaLvalEUSjoaFb I3dlZTREp51Q/RQ5/7GJuZGHkvtPACePBIa2Sz8cQ1fF46dAn9j/vMLSLDpM7ItpDfCo2vcXq X-Google-Smtp-Source: ABdhPJzjaOtXJG9BlF350gqKf1wSLFFgY1IN0ldejhSQvtnWKK1inwmALWBj78JrVFdHJIe4cBi2Mw== X-Received: by 2002:a17:90a:6445:: with SMTP id y5mr5217103pjm.64.1607106206096; Fri, 04 Dec 2020 10:23:26 -0800 (PST) Received: from [172.16.0.11] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id nk11sm2830676pjb.26.2020.12.04.10.23.24 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Dec 2020 10:23:24 -0800 (PST) From: Michael Koster Content-Type: multipart/alternative; boundary="Apple-Mail=_62E551CD-5C61-4863-9399-A1665BF9A0C6" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: Date: Fri, 4 Dec 2020 10:23:23 -0800 To: asdf@ietf.org X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [Asdf] Syntax idea for SDF 1.1 X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2020 18:23:29 -0000 --Apple-Mail=_62E551CD-5C61-4863-9399-A1665BF9A0C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii An obvious simplification occurred to me whilst refactoring some of the = models, wrt the way we define the input and output data for actions and = events. the current 1.1 feature syntax example: { "sdfAction": { "setOvenMode": {=20 "description": "Action to set the oven mode", "label": "Set Oven Mode", "sdfInputData": { "required": [ "ovenMode" ], "type": "object", "properties": { "ovenMode": { "sdfRef": "ex:#/sdfData/OvenMode" } } } } } } The idea is to factor out the redundant construct "type": = "object","properties": {} and have the properties be JSON properties of = the sdfInputData object, (also changing how "required" works): { "sdfAction": { "setOvenMode": {=20 "description": "Action to set the oven mode", "label": "Set Oven Mode", "sdfRequired": [ "sdfInputData/ovenMode" ], "sdfInputData": { "ovenMode": { "sdfRef": "ex:#/sdfData/OvenMode" } } } } } This removes an extra level from the JSON and enables a consistent use = of "sdfRequired".=20 Since sdfRequired now only refers to something inside its parent scoped = block, we could adopt a simple locally scoped pointer scheme which is a = hybrid of jso required property name and sdf 1.0 json-pointer scheme. We = would need to add a pointer type for this in the schema. This will work also for the required Properties, Actions, and Events in = a sdfObject, which makes it much more readable. ... "sdfObject": { "ovenMode": { "label": "Oven Mode", "sdfRequired": [ "sdfProperty/ovenMode", "sdfProperty/supportedOvenModes", "sdfAction/setOvenMode" ], "sdfProperty": { "ovenMode": { (etc.) --Apple-Mail=_62E551CD-5C61-4863-9399-A1665BF9A0C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii An obvious simplification occurred to me whilst refactoring = some of the models, wrt the way we define the input and output data for = actions and events.

the current 1.1 feature syntax example:


{
  "sdfAction": {
    "setOvenMode": = { 
      "description": "Action to set the oven = mode",
      "label": "Set Oven = Mode",
      "sdfInputData": {
        = "required": [ "ovenMode" ],
        "type": "object",
        "properties": {
          = "ovenMode": {
            "sdfRef": = "ex:#/sdfData/OvenMode"
          }
        = }
  =     }
    }
  }
}

The idea is to factor out the redundant construct "type": "object","properties": = {} and have the properties be JSON properties of the = sdfInputData object, (also changing how "required" works):

{
  "sdfAction": {
    = "setOvenMode": { 
      "description": "Action to set the oven = mode",
      "label": "Set Oven = Mode",
      "sdfRequired": [ "sdfInputData/ovenMode" = ],
  =     "sdfInputData": {
        = "ovenMode": {
          "sdfRef": = "ex:#/sdfData/OvenMode"
        = }
  =     }
    }
  }
}

This removes an extra level from the JSON and enables a = consistent use of "sdfRequired". 

Since sdfRequired now only refers to = something inside its parent scoped block, we could adopt a simple = locally scoped pointer scheme which is a hybrid of jso required property = name and sdf 1.0 json-pointer scheme. We would need to add a pointer = type for this in the schema.

This will work also for the required = Properties, Actions, and Events in a sdfObject, which makes it much more = readable.
...
  "sdfObject": {
    "ovenMode": = {
  =     "label": "Oven Mode",
      "sdfRequired": = [
  =       "sdfProperty/ovenMode",
        = "sdfProperty/supportedOvenModes",
        = "sdfAction/setOvenMode"
      ],
      "sdfProperty": = {
  =       "ovenMode": {
(etc.)


= --Apple-Mail=_62E551CD-5C61-4863-9399-A1665BF9A0C6-- From nobody Sun Dec 6 21:32:08 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D8C3A0CEF for ; Sun, 6 Dec 2020 21:32:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61XgIvkWKcGS for ; Sun, 6 Dec 2020 21:32:03 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6793A1013 for ; Sun, 6 Dec 2020 21:32:02 -0800 (PST) Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CqBl4231kzyWM; Mon, 7 Dec 2020 06:32:00 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 629011919.791907-50c24032098a832871718f95740b16d0 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Mon, 7 Dec 2020 06:31:59 +0100 Message-Id: To: asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 05:32:07 -0000 I have pushed text for the sdfChoice proposal, which should be = addressing #2 and #5. Please have a look at: https://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice (Commit https://github.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo = commit.) If this is accepted by the WG, we should be getting closer to declaring = SDF 1.1. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Dec 7 01:03:06 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA2F3A11A3 for ; Mon, 7 Dec 2020 01:03:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rV1pywFQlPq8 for ; Mon, 7 Dec 2020 01:03:03 -0800 (PST) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3578C3A11A1 for ; Mon, 7 Dec 2020 01:03:03 -0800 (PST) Received: by mail-wr1-x42e.google.com with SMTP id u12so12000353wrt.0 for ; Mon, 07 Dec 2020 01:03:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=MyJoI/BXvI7UW4DdTlUr9pFl+w+iDOd41KvEFQwfMpU=; b=HlldRCWjLWcYovXKan2IDByG3bow2w0bYQ5+QbhFnlkQe3LoH/8GB3+TFd0T85ZUcj me/XsuYz7TWPO2H+H2gNvGAeMBMBSxNYDGvoCdOrhBwN5vULaQAJSoxkekRPH26Eaq9A WQSMdtXYO9A8PQvE+zLUBqcXJzj6SsSpTsex1JTnrVC8kLdbUOlTwzASQ59RIlf91QOQ fRLbELNnPySuoLJf8unvTm/1mJAgnrstimpOk8ibbmANFv0HZKzS429ME3QRRVh2HllY yHQH+dIc4scTvIzzRCoqIT6lkvNmOwvOdQpclxwAIAG+qCMTG/cfaZDCMLcoQsetoZ0k HdFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=MyJoI/BXvI7UW4DdTlUr9pFl+w+iDOd41KvEFQwfMpU=; b=eIj1nzht91x6AAmd2+E0wyQjPV6zCIJh7OZhKhn8PPKvtmAztW2thcNots/09zfXVI t45S+Hb2tucRQSUfJGTeWpwvgWfX7jj2ptNPxS0pW590PS60B6FXnj709VBUo9ZLOhuN da94/lM0j3j/C1AODLytLRSeuBgAN0Zkm7AjvUb+aY0n2Zq1QGKxLPcp2PP5gLXBuSw1 cajJvUZBN/pX4MzBCxKj65v5ySdanp5reiIUWoEGeLLv5F+Pc4GWLZBWeSwn3OGgFcuo 4i/3FvZNXrQIhk+Fji34kfrNTtM/v8WiVghP7elVnOla4gZ1udAoAI/500PDCWulG7iT jvjA== X-Gm-Message-State: AOAM530FFjMp5NhB7NOX6QAzZTCGtitZsMnX1/CNYyE4HVHM63lqJpzH VPvYW7F9B3eo5MdhVkRKnd1oveaXGaU= X-Google-Smtp-Source: ABdhPJxw+owN4j8fOeLNNzH+EIuUS0LOoUXU4nt969qd8t9k0vnzT+M3SSzOOkIWdAC5siFPkiNRdw== X-Received: by 2002:adf:9b91:: with SMTP id d17mr5959781wrc.32.1607331781371; Mon, 07 Dec 2020 01:03:01 -0800 (PST) Received: from LAPTOPL39HIA21 ([37.46.21.139]) by smtp.gmail.com with ESMTPSA id f4sm12935436wmb.47.2020.12.07.01.02.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Dec 2020 01:03:00 -0800 (PST) From: To: "'Carsten Bormann'" , References: In-Reply-To: Date: Mon, 7 Dec 2020 09:02:59 -0000 Message-ID: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJbsVIey3sX/gsr9VIgy9R01WMPJqjhimjw Content-Language: en-ie Archived-At: Subject: Re: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 09:03:05 -0000 Hi Carsten, Thanks for doing this. The discussion on "with what to extend the current enums" did not go = further than mentioning that the current enum mechanism of JSON schema = did not have the possibility of a description field. Hence no other = additions have been identified. I still do not like how sdfChoice is handling the none string enums.=20 The none string value is multiple levels down in the description, which = is frankly awkward.=20 =20 I rather want to go for the simpler model of having a table that extend = the normal enum with additional fields. So that the existing enum structure can be used and thus the enum values = are directly known e.g. "myenum" :{ "type": "number", "enum": [1, 2, 3] } "myenum2" :{ "type": "string", "enum": [ "blah", "blahblah"] } By having a top level extension mechanism to add more info to these = fields if needed/wanted: sdfExtensions: { ".../myenum/1" : { "description": "This is a foonly" } ... ".../myenum/blah" : { "description": "This is a blah" } } Let's discuss this on the call today. Kind Regards, Wouter -----Original Message----- From: ASDF On Behalf Of Carsten Bormann Sent: Monday 7 December 2020 05:32 To: asdf@ietf.org Subject: [Asdf] Issues #2 and #5: sdfChoice I have pushed text for the sdfChoice proposal, which should be = addressing #2 and #5. Please have a look at: https://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice (Commit https://github.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo = commit.) If this is accepted by the WG, we should be getting closer to declaring = SDF 1.1. Gr=C3=BC=C3=9Fe, Carsten --=20 ASDF mailing list ASDF@ietf.org https://www.ietf.org/mailman/listinfo/asdf From nobody Mon Dec 7 05:57:41 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA693A13DE for ; Mon, 7 Dec 2020 05:57:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nosyy1hV_zHs for ; Mon, 7 Dec 2020 05:57:36 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B00D3A13DD for ; Mon, 7 Dec 2020 05:57:36 -0800 (PST) Received: from [192.168.217.120] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CqPyQ5K2jzyTT; Mon, 7 Dec 2020 14:57:34 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Mon, 7 Dec 2020 14:57:34 +0100 Cc: asdf@ietf.org X-Mao-Original-Outgoing-Id: 629042254.243274-dc282a901d8729c2115a5d92c8984a10 Content-Transfer-Encoding: quoted-printable Message-Id: <6F7FED8B-3A2F-4892-9F8F-57A3B6482D8A@tzi.org> References: To: Michael Koster X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Asdf] Syntax idea for SDF 1.1 X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 13:57:39 -0000 Hi Michael, On 2020-12-04, at 19:23, Michael Koster = wrote: >=20 > An obvious simplification occurred to me whilst refactoring some of = the models, wrt the way we define the input and output data for actions = and events. >=20 > the current 1.1 feature syntax example: >=20 >=20 > { > "sdfAction": { > "setOvenMode": {=20 > "description": "Action to set the oven mode", > "label": "Set Oven Mode", > "sdfInputData": { > "required": [ "ovenMode" ], > "type": "object", > "properties": { > "ovenMode": { > "sdfRef": "ex:#/sdfData/OvenMode" > } > } > } > } > } > } >=20 > The idea is to factor out the redundant construct "type": = "object","properties": {} and have the properties be JSON properties of = the sdfInputData object, That is similar to my original proposal, which we seemed to move away = from in favor of adopting jso type=3Dobject wholesale. > (also changing how "required" works): Actually, not really wanting to change that really was the motivator to = go for the jso variant. > { > "sdfAction": { > "setOvenMode": {=20 > "description": "Action to set the oven mode", > "label": "Set Oven Mode", > "sdfRequired": [ "sdfInputData/ovenMode" ], > "sdfInputData": { > "ovenMode": { > "sdfRef": "ex:#/sdfData/OvenMode" > } > } > } > } > } >=20 > This removes an extra level from the JSON and enables a consistent use = of "sdfRequired".=20 That is really the interesting question that pops up: What does = sdfRequired mean? So far we have the wholesale requiredness of affordances, as well as the = requiredness of specific substructures in the data models. Should these be handled the same? Can you have an optional (SDF) property that, when present, has a = required map entry (jso property)? How would this map into = sdfRequired? (It maps easily into a jso required for the data model = part.) .oOo. Then there is this whole can of worms, which we can reopen once we have = a good grasp on what we want to do about the former. > Since sdfRequired now only refers to something inside its parent = scoped block, we could adopt a simple locally scoped pointer scheme = which is a hybrid of jso required property name and sdf 1.0 json-pointer = scheme. We would need to add a pointer type for this in the schema. >=20 > This will work also for the required Properties, Actions, and Events = in a sdfObject, which makes it much more readable. > ... > "sdfObject": { > "ovenMode": { > "label": "Oven Mode", > "sdfRequired": [ > "sdfProperty/ovenMode", > "sdfProperty/supportedOvenModes", > "sdfAction/setOvenMode" > ], > "sdfProperty": { > "ovenMode": { > (etc.) Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Dec 7 11:34:37 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDBC3A0763 for ; Mon, 7 Dec 2020 11:34:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smartthings.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6RY4oWn-eqnz for ; Mon, 7 Dec 2020 11:34:34 -0800 (PST) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45B3A3A074E for ; Mon, 7 Dec 2020 11:34:34 -0800 (PST) Received: by mail-pf1-x42c.google.com with SMTP id w6so11112372pfu.1 for ; Mon, 07 Dec 2020 11:34:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smartthings.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=A6fIphWv5Ez6Igk/Um1gUBoguqpfozJE98+LnqM31bg=; b=Xmn7VYjEqfCkaTu586kRVQ7/E0BGjhH/n9eNh35v4Bq1Nt09WRRx/Xi5lf4jnN5UEh 08GEY3GxpBbznMV3Y4X0ab1Jq8s/nIhf+fqnAHKJNUaoGngLi6LJU3urwF9QQkcgg38A s0YYQ25UbAtuPXaQFcIg56/9mqe7+W4qv8eaXh1+kqW77koZiIpL8PBU2g6E70+GeYm2 bZ8NfXr3jYVCCdFl3gAgqQLMiEfP2BjVRZ+KoeiOa2EghiVpUL2nzk47yVw9+0TBSAJ+ qxSig1afnuGyrIcMAR5htqPcpobJAi4kq0OwvE+JE9i/KIyLx4PdGw9xKtOWDdyVqf5c SSpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=A6fIphWv5Ez6Igk/Um1gUBoguqpfozJE98+LnqM31bg=; b=RBTOq6i6oN5acb3dIut/60GvQ5pRbrE3/MSYIfKiuCR0/Q3MBfWMfEObRoq3E7TDf+ KMCn3nWBSrFPd5aRDERc9i8oyNB7UegPSpObgHwL/phCNluHjx+N30FPPYVICFXUB90K TDFN4ImhB6Nr/lJnID9O0+JXbARlu9wi4wYIJcXJ8eMzaEfaQM03mM2lGmIYGpGXm62S 2rH30m7JvJoiYh0OPlVCWsNiQ1ul/6ae0FlnuhtGhB/g2m9f41CAKV5JqK6LNv9wFtUW Qbwnonl1YVG7DCPhruSRP8ed5uPoO3hG9pTaJCuNEy8gqvk5UeWHVOHfbG6VidG8zyCV 60Fw== X-Gm-Message-State: AOAM532JmL14JHoMB1jpOZabxTToX2S86S24VAYKiCTTQNXXtQf5jN27 +e1Cn0ytLflHBv+hMbAXCORNQA== X-Google-Smtp-Source: ABdhPJwGI9mtEeU+x28V80djqReh4YdmPf5nsr5/r3Xq7mnt6FDkc4p2/9ItF0O2Q8RW4PTGJh+/1Q== X-Received: by 2002:a62:6d06:0:b029:19d:9728:2b71 with SMTP id i6-20020a626d060000b029019d97282b71mr16944523pfc.69.1607369673589; Mon, 07 Dec 2020 11:34:33 -0800 (PST) Received: from [172.16.0.4] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id u1sm129801pjn.40.2020.12.07.11.34.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Dec 2020 11:34:32 -0800 (PST) From: Michael Koster Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_7838F859-90B3-4DE6-A634-853BE7B3EF61" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\)) Date: Mon, 7 Dec 2020 11:34:30 -0800 In-Reply-To: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> Cc: Carsten Bormann , asdf@ietf.org To: wavdb66@gmail.com References: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> X-Mailer: Apple Mail (2.3445.104.15) Archived-At: Subject: Re: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 19:34:36 -0000 --Apple-Mail=_7838F859-90B3-4DE6-A634-853BE7B3EF61 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Taking this to some examples, we could start with an enum and an = extension, call it sdfMap for now: "sdfData": { "SwitchState": { "enum": [ "on", "off" ] } }, "sdfMap": { "#/sdfData/SwitchState/enum/on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "#/sdfData/SwitchState/enum/off": { "label": "Off", "description": "The un-powered or functionally inactive state", "default": "off" } =20 } But it isn=E2=80=99t clear how e.g. the pointer to a label would work in = the above example. It=E2=80=99s not clear how the expected construct = would resolve: #/sdfData/SwitchState/enum/on/label We could provide a local mapping for the enum instead: "sdfData": { "SwitchState": { "enum": [ "on", "off" ], "sdfMap": { "on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "off": { "label": "Off", "description": "The un-powered or functionally inactive = state", "default": "off" } } Here the pointer could point to the sdfMap: #/sdfData/SwitchState/sdfMap/on/label Hmm, we could just change the name from sdfMap to sdfAny and we have a = parallel construct for mapping enums (that we can also use for the anyOf = use case): "sdfData": { "SwitchState": { "enum": [ "on", "off" ], =E2=80=9CsdfAny": { "on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "off": { "label": "Off", "description": "The un-powered or functionally inactive = state", "default": "off" } } The pointer works the same as with the local map: #/sdfData/SwitchState/sdfAny/on/label > On Dec 7, 2020, at 1:02 AM, = wrote: >=20 > Hi Carsten, >=20 > Thanks for doing this. > The discussion on "with what to extend the current enums" did not go = further than mentioning that the current enum mechanism of JSON schema = did not have the possibility of a description field. Hence no other = additions have been identified. >=20 > I still do not like how sdfChoice is handling the none string enums.=20= > The none string value is multiple levels down in the description, = which is frankly awkward.=20 >=20 > I rather want to go for the simpler model of having a table that = extend the normal enum with additional fields. > So that the existing enum structure can be used and thus the enum = values are directly known > e.g. > "myenum" :{ > "type": "number", > "enum": [1, 2, 3] > } > "myenum2" :{ > "type": "string", > "enum": [ "blah", "blahblah"] > } >=20 > By having a top level extension mechanism to add more info to these = fields if needed/wanted: >=20 > sdfExtensions: { > ".../myenum/1" : { > "description": "This is a foonly" > } > ... > ".../myenum/blah" : { > "description": "This is a blah" > } > } >=20 > Let's discuss this on the call today. >=20 > Kind Regards, > Wouter >=20 > -----Original Message----- > From: ASDF On Behalf Of Carsten Bormann > Sent: Monday 7 December 2020 05:32 > To: asdf@ietf.org > Subject: [Asdf] Issues #2 and #5: sdfChoice >=20 > I have pushed text for the sdfChoice proposal, which should be = addressing #2 and #5. >=20 > Please have a look at: >=20 > https://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice >=20 > (Commit https://github.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo = commit.) >=20 > If this is accepted by the WG, we should be getting closer to = declaring SDF 1.1. >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 > --=20 > ASDF mailing list > ASDF@ietf.org > https://www.ietf.org/mailman/listinfo/asdf >=20 > --=20 > ASDF mailing list > ASDF@ietf.org > https://www.ietf.org/mailman/listinfo/asdf --Apple-Mail=_7838F859-90B3-4DE6-A634-853BE7B3EF61 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Taking this to some examples, we could start with an enum and = an extension, call it sdfMap for now:

  "sdfData": {
    = "SwitchState": {
      "enum": [
    =     "on",
        "off"
    =   ]
    }
  },
  "sdfMap": = {
    "#/sdfData/SwitchState/enum/on": = {
      "label": "On",
    =   "description": "The powered or functionally active = state",
      "default": "on"
    = },
    "#/sdfData/SwitchState/enum/off": = {
      "label": "Off",
    =   "description": "The un-powered or functionally inactive = state",
      "default": "off"
    } =  
  }

But it isn=E2=80=99t clear how e.g. the pointer to a label = would work in the above example. It=E2=80=99s not clear how the expected = construct would resolve:

#/sdfData/SwitchState/enum/on/label


We could provide a local mapping for the enum = instead:

  = "sdfData": {
    "SwitchState": {
    =   "enum": [
        "on",
    =     "off"
      ],
    =   "sdfMap": {
        "on": = {
          "label": = "On",
          "description": "The = powered or functionally active state",
        =   "default": "on"
        },
    =     "off": {
          "label": = "Off",
          "description": "The = un-powered or functionally inactive state",
    =       "default": "off"
        = }
      }

Here the pointer could = point to the sdfMap:

#/sdfData/SwitchState/sdfMap/on/label


Hmm, we could just change the name from = sdfMap to sdfAny and we have a parallel construct for mapping enums = (that we can also use for the anyOf use case):

  "sdfData": {
    = "SwitchState": {
      "enum": [
    =     "on",
        "off"
    =   ],
      =E2=80=9CsdfAny": = {
        "on": {
    =       "label": "On",
        =   "description": "The powered or functionally active = state",
          "default": = "on"
        },
    =     "off": {
          "label": = "Off",
          "description": "The = un-powered or functionally inactive state",
    =       "default": "off"
        = }
      }

The pointer works the = same as with the local map:

#/sdfData/SwitchState/sdfAny/on/label


On Dec 7, 2020, at 1:02 AM, <wavdb66@gmail.com> = <wavdb66@gmail.com> wrote:

Hi = Carsten,

Thanks for doing this.
The discussion on "with what to extend the current enums" did = not go further than mentioning that the current enum mechanism of JSON = schema did not have the possibility of a description field. Hence no = other additions have been identified.

I = still do not like how sdfChoice is handling the none string enums.
The none string value is multiple levels down in the = description, which is frankly awkward.

I = rather want to go for the simpler model of having a table that extend = the normal enum with additional fields.
So that the = existing enum structure can be used and thus the enum values are = directly known
e.g.
"myenum" :{
"type": "number",
"enum": [1, 2, 3]
}
"myenum2" :{
"type": = "string",
"enum": [ "blah", "blahblah"]
}

By having a top level extension mechanism to = add more info to these fields if needed/wanted:

sdfExtensions: {
".../myenum/1" : {
"description": "This is a foonly"
}
...
".../myenum/blah" : {
"description": "This is a blah"
}
}

Let's discuss this on the call = today.

Kind Regards,
Wouter

-----Original Message-----
From: = ASDF <asdf-bounces@ietf.org> On Behalf Of Carsten Bormann
Sent: Monday 7 December 2020 05:32
To: asdf@ietf.org
Subject: [Asdf] Issues #2 and #5: sdfChoice

I have pushed text for the sdfChoice proposal, which should = be addressing #2 and #5.

Please have a look = at:

https://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice<= br class=3D"">
(Commit = https://github.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo = commit.)

If this is accepted by the WG, we = should be getting closer to declaring SDF 1.1.

Gr=C3=BC=C3=9Fe, Carsten

--
ASDF mailing list
ASDF@ietf.org
https://www.ietf.org/mailman/listinfo/asdf

--
ASDF mailing list
ASDF@ietf.org
https://www.ietf.org/mailman/listinfo/asdf

= --Apple-Mail=_7838F859-90B3-4DE6-A634-853BE7B3EF61-- From nobody Thu Dec 10 04:10:27 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61CA13A0D32 for ; Thu, 10 Dec 2020 04:10:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4iHluysKoEw for ; Thu, 10 Dec 2020 04:10:23 -0800 (PST) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83A93A0D31 for ; Thu, 10 Dec 2020 04:10:22 -0800 (PST) Received: by mail-wr1-x42a.google.com with SMTP id k14so5242938wrn.1 for ; Thu, 10 Dec 2020 04:10:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=ZlGgg4gNOobJ+RfQdLOM060DV/9/ez2nSnHAsgUGgYs=; b=GEDF89GUjmDE18LjQENCiI4r8S8fjNrzm0JwN9cbVxfKOc8jQUQZxJ3sA9A8E9P1rc 3Qj09/c7Ji6Z7iwmPKT6QYejWfZIUNs4vQUC6QYTI8qWfL+mgEz7JISdldPpWYg9RbBE C+niUHrX+LoF4j6gz1M6v4BzAx6qZfPAVs+qdfcVOcBPVnwmKWhObWc0v3KC7CpY6eDa kXuOVCj0EVuGg7Rfmi//2hPBSc8Y2y9G54JU19uFTYu+AIueWr75d7lpkJTm58A3ehCl bAWzFB8PIu9va/5rAffKNpZtbLdL4n1YggXaNNGsZlupUvyy2/6pVwnJZ5KV+qftK/vo eAwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=ZlGgg4gNOobJ+RfQdLOM060DV/9/ez2nSnHAsgUGgYs=; b=pygE9qkg/OV1j6VhxjNIMI5z3YJGj+v6RlaM43VbbhZZAJD40eTLGaG7Gbys4UZGL5 0zk8oCxVvcrSTYtbvEXgufDw2rEt5tDjnLIo/5KO2X/geMFIdkdLEKT813OBMPjr8WTn g+GbwPzg9de5JoMO0pDH8sr7I0ALdg0SFwgczQhfPjWqxC7T064x8k/u8gQTkmcr1PLr k+i6V2krBysVDqpkV8f/ITyPycXVdAQKAgo1+NNLaSWzaU3RJZSEBdhnZjT3vIUqWRmx co6aXcsrDWwmU8mOG+tc3pSUINJ8Q6MLJWKeEI8cyfOuoBXGA803hwFEbsxmnNzmERn8 VGLw== X-Gm-Message-State: AOAM533tkFa5IeuWUsrvQ7azpQmJsay9XEUpXCiFIMU9JoM1jjrw5zVc azGrcV/dyzgwiKjVjHAaktJfvOzWqLR+qw== X-Google-Smtp-Source: ABdhPJxm4aiinIr/Ujvk+8JMg13+VjTYyEkyV+I1guTAGW/o9XZHaaTu5cUa6sm8Qgv4UG5nNp9IhQ== X-Received: by 2002:a5d:660b:: with SMTP id n11mr7850588wru.407.1607602219673; Thu, 10 Dec 2020 04:10:19 -0800 (PST) Received: from LAPTOPL39HIA21 ([93.92.10.207]) by smtp.gmail.com with ESMTPSA id h5sm10079359wrp.56.2020.12.10.04.10.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Dec 2020 04:10:18 -0800 (PST) From: To: "'Michael Koster'" Cc: "'Carsten Bormann'" , References: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> In-Reply-To: Date: Thu, 10 Dec 2020 12:10:16 -0000 Message-ID: <001001d6ceed$6c66dd60$45349820$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01D6CEED.6C68B220" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJbsVIey3sX/gsr9VIgy9R01WMPJgK178SkAfvAeBeowOpdgA== Content-Language: en-ie Archived-At: Subject: Re: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2020 12:10:25 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0011_01D6CEED.6C68B220 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Michael, =20 What is the intent of the label? E.g. why is the external reference of = that label needed? =20 Kind Regards, Wouter =20 From: Michael Koster =20 Sent: Monday 7 December 2020 19:35 To: wavdb66@gmail.com Cc: Carsten Bormann ; asdf@ietf.org Subject: Re: [Asdf] Issues #2 and #5: sdfChoice =20 Taking this to some examples, we could start with an enum and an = extension, call it sdfMap for now: =20 "sdfData": { "SwitchState": { "enum": [ "on", "off" ] } }, "sdfMap": { "#/sdfData/SwitchState/enum/on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "#/sdfData/SwitchState/enum/off": { "label": "Off", "description": "The un-powered or functionally inactive state", "default": "off" } =20 } =20 But it isn=E2=80=99t clear how e.g. the pointer to a label would work in = the above example. It=E2=80=99s not clear how the expected construct = would resolve: =20 #/sdfData/SwitchState/enum/on/label =20 =20 We could provide a local mapping for the enum instead: =20 "sdfData": { "SwitchState": { "enum": [ "on", "off" ], "sdfMap": { "on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "off": { "label": "Off", "description": "The un-powered or functionally inactive = state", "default": "off" } } =20 Here the pointer could point to the sdfMap: =20 #/sdfData/SwitchState/sdfMap/on/label =20 =20 Hmm, we could just change the name from sdfMap to sdfAny and we have a = parallel construct for mapping enums (that we can also use for the anyOf = use case): =20 "sdfData": { "SwitchState": { "enum": [ "on", "off" ], =E2=80=9CsdfAny": { "on": { "label": "On", "description": "The powered or functionally active state", "default": "on" }, "off": { "label": "Off", "description": "The un-powered or functionally inactive = state", "default": "off" } } =20 The pointer works the same as with the local map: =20 #/sdfData/SwitchState/sdfAny/on/label =20 =20 On Dec 7, 2020, at 1:02 AM, > > wrote: =20 Hi Carsten, Thanks for doing this. The discussion on "with what to extend the current enums" did not go = further than mentioning that the current enum mechanism of JSON schema = did not have the possibility of a description field. Hence no other = additions have been identified. I still do not like how sdfChoice is handling the none string enums.=20 The none string value is multiple levels down in the description, which = is frankly awkward.=20 I rather want to go for the simpler model of having a table that extend = the normal enum with additional fields. So that the existing enum structure can be used and thus the enum values = are directly known e.g. "myenum" :{ "type": "number", "enum": [1, 2, 3] } "myenum2" :{ "type": "string", "enum": [ "blah", "blahblah"] } By having a top level extension mechanism to add more info to these = fields if needed/wanted: sdfExtensions: { ".../myenum/1" : { "description": "This is a foonly" } ... ".../myenum/blah" : { "description": "This is a blah" } } Let's discuss this on the call today. Kind Regards, Wouter -----Original Message----- From: ASDF > On = Behalf Of Carsten Bormann Sent: Monday 7 December 2020 05:32 To: asdf@ietf.org =20 Subject: [Asdf] Issues #2 and #5: sdfChoice I have pushed text for the sdfChoice proposal, which should be = addressing #2 and #5. Please have a look at: https://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice (Commit https://github.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo = commit.) If this is accepted by the WG, we should be getting closer to declaring = SDF 1.1. Gr=C3=BC=C3=9Fe, Carsten --=20 ASDF mailing list ASDF@ietf.org =20 https://www.ietf.org/mailman/listinfo/asdf --=20 ASDF mailing list ASDF@ietf.org =20 https://www.ietf.org/mailman/listinfo/asdf =20 ------=_NextPart_000_0011_01D6CEED.6C68B220 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Michael,

 

What is the = intent of the label? E.g. why is the external reference of that label = needed?

 

Kind = Regards,
Wouter

 

From: Michael Koster = <michael.koster@smartthings.com>
Sent: Monday 7 = December 2020 19:35
To: wavdb66@gmail.com
Cc: = Carsten Bormann <cabo@tzi.org>; asdf@ietf.org
Subject: = Re: [Asdf] Issues #2 and #5: = sdfChoice

 

Taking this = to some examples, we could start with an enum and an extension, call it = sdfMap for now:

 

  = "sdfData": {

    = "SwitchState": {

      = "enum": [

      =   "on",

      =   "off"

      = ]

    = }

  = },

  "sdfMap": = {

    = "#/sdfData/SwitchState/enum/on": = {

      = "label": "On",

      = "description": "The powered or functionally active = state",

      = "default": "on"

    = },

    = "#/sdfData/SwitchState/enum/off": = {

      = "label": "Off",

      = "description": "The un-powered or functionally inactive = state",

      = "default": "off"

    } =  

  = }

 

But it isn=E2=80=99t clear how e.g. the pointer to a = label would work in the above example. It=E2=80=99s not clear how the = expected construct would resolve:

 

#/sdfData/SwitchState/enum= /on/label

 

 

We could provide a local mapping for the enum = instead:

 

  = "sdfData": {

    = "SwitchState": {

      = "enum": [

      =   "on",

      =   "off"

      = ],

      = "sdfMap": {

      =   "on": {

      =     "label": = "On",

      =     "description": "The powered or functionally = active state",

      =     "default": = "on"

      =   },

      =   "off": {

      =     "label": = "Off",

      =     "description": "The un-powered or = functionally inactive state",

      =     "default": = "off"

      =   }

      = }

 

Here the pointer could point to the = sdfMap:

 

#/sdfData/SwitchState/sdfM= ap/on/label

 

 

Hmm, we could just change the name from sdfMap to = sdfAny and we have a parallel construct for mapping enums (that we can = also use for the anyOf use case):

 

  = "sdfData": {

    = "SwitchState": {

      = "enum": [

      =   "on",

      =   "off"

      = ],

    =   =E2=80=9CsdfAny": {

      =   "on": {

      =     "label": = "On",

      =     "description": "The powered or functionally = active state",

      =     "default": = "on"

      =   },

      =   "off": {

      =     "label": = "Off",

      =     "description": "The un-powered or = functionally inactive state",

      =     "default": = "off"

      =   }

      = }

 

The pointer works the same as with the local = map:

 

#/sdfData/SwitchState/sdfA= ny/on/label

 

 

On Dec 7, 2020, at 1:02 AM, <wavdb66@gmail.com> <wavdb66@gmail.com> = wrote:

 

Hi = Carsten,

Thanks for doing this.
The discussion on "with = what to extend the current enums" did not go further than = mentioning that the current enum mechanism of JSON schema did not have = the possibility of a description field. Hence no other additions have = been identified.

I still do not like how sdfChoice is handling = the none string enums.
The none string value is multiple levels down = in the description, which is frankly awkward.

I rather want to = go for the simpler model of having a table that extend the normal enum = with additional fields.
So that the existing enum structure can be = used and thus the enum values are directly = known
e.g.
"myenum" :{
"type": = "number",
"enum": [1, 2, = 3]
}
"myenum2" :{
"type": = "string",
"enum": [ "blah", = "blahblah"]
}

By having a top level extension = mechanism to add more info to these fields if = needed/wanted:

sdfExtensions: {
".../myenum/1" : = {
"description": "This is a = foonly"
}
...
".../myenum/blah" : = {
"description": "This is a = blah"
}
}

Let's discuss this on the call = today.

Kind Regards,
Wouter

-----Original = Message-----
From: ASDF <asdf-bounces@ietf.org> On = Behalf Of Carsten Bormann
Sent: Monday 7 December 2020 05:32
To: = asdf@ietf.org
Subject: [Asdf] = Issues #2 and #5: sdfChoice

I have pushed text for the sdfChoice = proposal, which should be addressing #2 and #5.

Please have a = look at:

https= ://ietf-wg-asdf.github.io/SDF/sdf.html#name-sdfchoice

(Commit = https://githu= b.com/ietf-wg-asdf/SDF/commit/be0fd37 plus a typo commit.)

If = this is accepted by the WG, we should be getting closer to declaring SDF = 1.1.

Gr=C3=BC=C3=9Fe, Carsten

--
ASDF mailing = list
ASDF@ietf.org
https://www.ietf.org/= mailman/listinfo/asdf

--
ASDF mailing list
ASDF@ietf.org
https://www.ietf.org/= mailman/listinfo/asdf

 

------=_NextPart_000_0011_01D6CEED.6C68B220-- From nobody Thu Dec 10 05:15:58 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32DBC3A0DD2 for ; Thu, 10 Dec 2020 05:15:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shS5mOwPsKTC for ; Thu, 10 Dec 2020 05:15:54 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22F553A098D for ; Thu, 10 Dec 2020 05:15:53 -0800 (PST) Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CsDtw0jjdzyW8; Thu, 10 Dec 2020 14:15:52 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Thu, 10 Dec 2020 14:15:51 +0100 Cc: wavdb66@gmail.com, asdf@ietf.org X-Mao-Original-Outgoing-Id: 629298951.399098-7a40f66a87b660d7b70313421d262271 Content-Transfer-Encoding: quoted-printable Message-Id: References: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> To: Michael Koster X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2020 13:15:56 -0000 On 2020-12-07, at 20:34, Michael Koster = wrote: >=20 > Taking this to some examples, we could start with an enum and an = extension, call it sdfMap for now: I don=E2=80=99t think we should come up with a contorted structure just = to achieve some superficial similarity with the json-schema.org way of = doing this. This is much harder to generate and consume, as well as read/check, so = there really is no benefit. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Dec 11 04:57:46 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9243A0BBC; Fri, 11 Dec 2020 04:57:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tz2RrzyGz10G; Fri, 11 Dec 2020 04:57:42 -0800 (PST) Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2054.outbound.protection.outlook.com [40.107.22.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EB1C3A0BB8; Fri, 11 Dec 2020 04:57:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IApuABb1JBVG1fZ6yXgdHTKl6IipA/E9NiRad4p0X+JcSsfadqqqUhKVBMYGJAup9v0dTK77MWLKB77V5csKQFORQ8AvVBF9Jdk7u0LcAOZm/wy6UYju8Copig8XPFHiDTCT9dYVmHmSlYbE8Sk7rIl5isHL5ZEMTx8N4nHzwXW5KPzybMidm89XLWzbx8g3zuKvz7zaJfeQDkfSIXuTRqcKR9ri+7X3Sy9WtWzCNK8652yTHJUnRFv/BJkenoUnuXv+3aXkAmYbhJUktQE5hYZOLnVXdxQE1sk/u3eDLGiX+1v80kto2laYJNX3ZLYlPLi4Zj3SBhwJ7u/rnWerPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=061cGxFEGWUoaKpVMNCsbSbOp0C+LzV85J1e3VSRW5k=; b=Vv487W1V68BrUl3Q8tIBfTVfFkfDA9MVe1SYF2TDd7SJsCZjBJ+4S7KB1tmAL4gNAyc4X/k3eUD6m/upxvlV/CMenveujcsolQiD2jMuHkn/0SlxoZjbYvIfO+fXPa53yidHc6imEem3LEoqGGUzL7id1wTNJu0E3AMKPP6q8sgOTk5y9LqdJQRuPhlRW+s+Xe42bWheCa9YvONJd23fUiWco1gdtmj0doa89/LT5fkyNgrn4+0ntcgPBPfmT47ewo+xtg1rZjx0Vc0quxVIhzagvq890/GOkDyXvlvIwYye72jIxoGitqI3o3RERtw4D+iTGLlr90q6ZJ6r2aDzAw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=061cGxFEGWUoaKpVMNCsbSbOp0C+LzV85J1e3VSRW5k=; b=TJmBKgx1qFlZilWGkrhct10WQGjyOgtz56RCiHUdCIawSMDXVE0kUAdTrRMjT54iogGwcqQpGQDMj8AKs6gBztxm+kiHTF/kAgRaHKw6Aq54AdMDe6j1/AZnBjKfmZlIBrHhwJCYmMJGTioH4YgtVKBSns1r1ODRPsJgAkHtV0k= Received: from HE1PR0702MB3818.eurprd07.prod.outlook.com (2603:10a6:7:8c::18) by HE1PR0701MB2138.eurprd07.prod.outlook.com (2603:10a6:3:2b::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3676.9; Fri, 11 Dec 2020 12:57:39 +0000 Received: from HE1PR0702MB3818.eurprd07.prod.outlook.com ([fe80::f022:4a17:5be2:f049]) by HE1PR0702MB3818.eurprd07.prod.outlook.com ([fe80::f022:4a17:5be2:f049%6]) with mapi id 15.20.3654.015; Fri, 11 Dec 2020 12:57:39 +0000 From: Niklas Widell To: "asdf@ietf.org" , "asdf-chairs@ietf.org" Thread-Topic: ASDF WG Virtual interim, 1400-1530 UTC, Dec 14th, 2020 Thread-Index: AQHWz7w2zZlNXejQE06jLVGXfveZQQ== Date: Fri, 11 Dec 2020 12:57:39 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com; x-originating-ip: [37.123.165.254] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 0cd2295b-f8d3-4dc6-ef85-08d89dd4575b x-ms-traffictypediagnostic: HE1PR0701MB2138: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:6790; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 7MrWMmup0HqACabLBOSjQKwfEciAF0A1MOSCiG3OwSPM1pOV3YhhmGqx2DlNOriFnxSyzFEVv+VBbtdCXk/gpiS1ysSYQJWg7ccurKszIZBH8seZ3zzuk8G0canfuTkEcQMCv8HoTnyilgl6VeNTZfMBWwZx/tI9sFR62D6tEv9muv9M6HaI5aFu4Y1vDEqjkWjr/RcHH7VV3nZMW41vvCjijHRQYgtC9JDqxfjPN0md2mTdFtFmJwGrJBHSKLkV4eunXJyI77HlKu8QDsgo6hrGMiwGS3UUhfnwfll+eZ/x6TD+jpL1VEi6mVU3hRsRxPa5RsCEcCwWpHBMTBPlB89KHusECNJBQQSimAwT/t3V/LfQM+Gf0DpZY5vCYTcDbqLBGgoZSBlfmbmBfAlqZm+BxA8mwSX6wBpf+JXreI/xMGKhUD1vfMt9nQqBZsWq x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HE1PR0702MB3818.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(136003)(346002)(376002)(396003)(39860400002)(5660300002)(166002)(71200400001)(8676002)(4001150100001)(16799955002)(55016002)(9686003)(6506007)(966005)(478600001)(186003)(26005)(7696005)(8936002)(110136005)(316002)(450100002)(86362001)(83380400001)(66556008)(2906002)(4744005)(33656002)(52536014)(66446008)(76116006)(64756008)(66476007)(66946007)(44832011); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata: =?us-ascii?Q?ZHi3VK+RaOZROzEp8agVrl+6Da315qknEFJFO6FQ0bS4ClJ2y+a+vS20/Nh+?= =?us-ascii?Q?5RXT0vsNP2+7Hgs0GNBO+fY90U2o99HPCUt4suVL+YXhF0K67L/4tR7L6Q2E?= =?us-ascii?Q?Mqbuhvx9r+JdSzwp074JtOIxv5ozySXogev2tssfwzj2v1lDlCN7o5WXPsKI?= =?us-ascii?Q?lW61lK9xm+1PLeR3G+LfVh/OQLERPSbhcEww4kGKNGdys89u+Iz7zc0r0F2v?= =?us-ascii?Q?++IONvzaz4QG1qwR94mA3yVFLnH2RdRCa6+BvgCvlV5AH8oBqHJ0WDUpj47U?= =?us-ascii?Q?LqfMB29Vo9nc9MtC1OIlWuc/smS+S9dSlKNhPxnUHYKSc3sndRXN0OfcHR/2?= =?us-ascii?Q?yuqyEYDeV5/fpEYFRo+L3HykUNRWRh+YuRKw1HpG4tV5GCPCT7IKB/t0Fq4G?= =?us-ascii?Q?OdTnlAORlZcUkBzx1s+AwjvITYUhCRs1aCldyfA/0h8hfXGs0sQxVi+YfmH4?= =?us-ascii?Q?dHB1KV0qylakNeaZPbYC1hNZlyfcQnxx7EY1u3pnkrMqxwc9we5dxFIxekJH?= =?us-ascii?Q?k7jysv6v9RqwFwq4xDMskRmD6StAH+Rx+k5bI2bxlPwDDoF1vxK/iHbqZbk5?= =?us-ascii?Q?yXNZT16EluU9q0QFuIjXvt/6IWdMT8vRFaXJ3AiF+RSBpqCUkhqYfHSA99SJ?= =?us-ascii?Q?WsLdyQ0Plop0HhUS5Jhp3qR4smxiZtzFI2hVAaUq14pN+jAEu0Yg8q4jJOv7?= =?us-ascii?Q?0SrWJ2mxuY25DZni6BJqOaxuCtTFc0hastajmloiSgRpXlaXD+GcHZL0gLb4?= =?us-ascii?Q?o4J0F7YjLOyt5xsUWBt5uX/p05C1QiwOlgULMgej9gEg6VmdwS+d6FTaCvlY?= =?us-ascii?Q?OJKqMCC4HW9dukTtpCWWJEVTHJAQ+fPE6s9M+Llf5Au2IfDlcmHh9lj2MiNk?= =?us-ascii?Q?4ygjtenZ8FQAULEbxdKK1BlWK/S0ouRfxoddvI4588LKWBIASD1dVNzhiFe2?= =?us-ascii?Q?S4ayb4Ikc1/q7QBPKnYnE/hyxJ54A3FnVbwlH0eTnN6oc6InxJLyoocdFl8v?= =?us-ascii?Q?2vHJZbCmOMDCOJToC44OneMJvg=3D=3D?= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_HE1PR0702MB38180B31233112565BC30C988ACA0HE1PR0702MB3818_" MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3818.eurprd07.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 0cd2295b-f8d3-4dc6-ef85-08d89dd4575b X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2020 12:57:39.6556 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: x13Hn1o8b++OP912W6EJjIAw2DP/VWd5PQ53MIi4SC8zNLFZNZhnR3Puk2qW+tNMHuPR7aPL1bvAYuuzuVf4f4fp84BCQfTLkdgkAPQSR80= X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2138 Archived-At: Subject: [Asdf] ASDF WG Virtual interim, 1400-1530 UTC, Dec 14th, 2020 X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Dec 2020 12:57:45 -0000 --_000_HE1PR0702MB38180B31233112565BC30C988ACA0HE1PR0702MB3818_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Gentle reminder to all that we have a ASDF virtual interim on Monday next w= eek: ASDF WG Virtual interim, 1400-1530 UTC, Dec 14th, 2020 Webex: https://ietf.webex.com/ietf/j.php?MTID=3Dm0d089a7c8ac2d5a188c733c810= 7cb390 Agenda: https://github.com/ietf-wg-asdf/asdf-working-group-notes/blob/main/= agendas/2020-12-14-agenda.md Cheers, Niklas (for the chairs) More info: draft-ietf-asdf-sdf https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/ SDF overview (from virtual previous interim) https://youtu.be/_8i6X4AxuOk (= 17 minutes) --_000_HE1PR0702MB38180B31233112565BC30C988ACA0HE1PR0702MB3818_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

Gentle reminder to all that we = have a ASDF virtual interim on Monday next week:

 

ASDF WG Virtual interim, 1400-1= 530 UTC, Dec 14th, 2020

 

Webex:&nb= sp;https://ietf.webex.com/ietf/j.php?MTID=3Dm0= d089a7c8ac2d5a188c733c8107cb390

 

Agenda:&n= bsp;https://github.com/= ietf-wg-asdf/asdf-working-group-notes/blob/main/agendas/2020-12-14-agenda.m= d

 =

Cheers,

Niklas (f= or the chairs)

&nbs= p;

More info= :

draft-ietf-asdf-sdf https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/=

 =

SDF overview (from virtu= al previous interim) https://youtu.be/_8i6X4AxuOk (17 minutes)

 

 

--_000_HE1PR0702MB38180B31233112565BC30C988ACA0HE1PR0702MB3818_-- From nobody Fri Dec 11 16:05:46 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAD1A3A106D for ; Fri, 11 Dec 2020 16:05:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smartthings.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o68yqpvmCMnr for ; Fri, 11 Dec 2020 16:05:42 -0800 (PST) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CCBC3A1069 for ; Fri, 11 Dec 2020 16:05:41 -0800 (PST) Received: by mail-pg1-x529.google.com with SMTP id w16so8248565pga.9 for ; Fri, 11 Dec 2020 16:05:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smartthings.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TTnZBN7EcoA48yJr6KwBMzjem2nayDyFbtAxId7p9YU=; b=N+w0OXZwXYuJ7xS/5qqH3Ae5jh8x9NyHCnDMBIffo/QA3EWhNjwiGlooU/qGOK249Q CiKsWviaXOOj6/693MtizPtgSEHvZGjptXuPyTYeQcaUQbcdPiwA6txF3oQNcmBl7GnS N6c+0ZW+/Ilrx4QJe/mldCdnQuigm2Q44G5U8eMitwd4DnP3BqTjqER5hDhsw+3VN31G bSaLQl1kzO1MGOY4PS1J/MvNVeFhUSK512KDcBdnLy2ZsgjJPuc2O3gyJNe9rsSSpQKb dWnDNGWX8f0SVgAIh1JtOEPUGTxMTVYdtrqyonaNh86E6aYNFjlcvTLXwALzM635O3TX K8Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TTnZBN7EcoA48yJr6KwBMzjem2nayDyFbtAxId7p9YU=; b=OZT3MktEHDuz+47hSlP4C9Mf181/UUi+uxyrRh1rXIJWp5Nps+f2LlYQrjh/K1+JvF isO2NVr7bmiorhiD03eROWr6uigDLx1BDu6wzVRJrFiD1OKlzVvgDLEIMuEXIXgXmCu6 dJquMq0CNce2O9xAhatqZQrMJABpm3s+S6leJD+hKotuuT5WnUsjteipW+n5H7WBBa1O xzrRjXlY8+6fXjeQ7zVeWhCqxQBtsTbYL4PW011Aj5TavySUngqrCQjX35hDJdDYDbS5 Ga+NPyhc5n0jzF0bMnatpbUnrjXcXf2NNzlV3HFSVtUZ6VlCajP801uA4PyfuiQqGcPF 0Irg== X-Gm-Message-State: AOAM533elx2sBTkEFjyo7YGyo9Jf0mpMxFyZeAYnwPEz757PTq5y9SFh G1EsV6Msw/+mAuda4zA7CDS7MQ== X-Google-Smtp-Source: ABdhPJwFNYfPCgPKmbhmVNsxLEyfSCjEaK57zVrVgLSm1OiFwG76szA3bbZPJNckoQKDBpTAdSW++g== X-Received: by 2002:a63:d45:: with SMTP id 5mr14427578pgn.0.1607731541440; Fri, 11 Dec 2020 16:05:41 -0800 (PST) Received: from [172.16.0.11] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id k15sm11556927pfh.40.2020.12.11.16.05.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Dec 2020 16:05:40 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Michael Koster In-Reply-To: Date: Fri, 11 Dec 2020 16:05:39 -0800 Cc: wavdb66@gmail.com, asdf@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <0219A070-C8AD-4EB5-8E02-C69AACC91573@smartthings.com> References: <006e01d6cc77$c33eb6d0$49bc2470$@gmail.com> To: Carsten Bormann X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Asdf] Issues #2 and #5: sdfChoice X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Dec 2020 00:05:45 -0000 I agree, and I want to propose the third option in the above message, = using sdfAny. > On Dec 10, 2020, at 5:15 AM, Carsten Bormann wrote: >=20 > On 2020-12-07, at 20:34, Michael Koster = wrote: >>=20 >> Taking this to some examples, we could start with an enum and an = extension, call it sdfMap for now: >=20 > I don=E2=80=99t think we should come up with a contorted structure = just to achieve some superficial similarity with the json-schema.org way = of doing this. > This is much harder to generate and consume, as well as read/check, so = there really is no benefit. >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 From nobody Sat Dec 12 14:19:49 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9CA3A0AF8 for ; Sat, 12 Dec 2020 14:19:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.003 X-Spam-Level: X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vOFHDVW03CB for ; Sat, 12 Dec 2020 14:19:45 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6156C3A07F0 for ; Sat, 12 Dec 2020 14:19:44 -0800 (PST) Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CthsT3B5jzybs; Sat, 12 Dec 2020 23:19:41 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 629504380.8461159-8943a91aa29cb87b5015d7ad45256c04 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Sat, 12 Dec 2020 23:19:40 +0100 Message-Id: <067ADF16-7E0D-4B3D-AD89-20F8B8D3E69E@tzi.org> To: asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] Model versioning X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Dec 2020 22:19:48 -0000 Netmod has a great discussion about data model versioning, e.g.: = = I think Juergen is on the right track with proposing to manage (at least = some aspects of) compatibility between evolving models outside the = models themselves. (In a followup, Andy mentions that semver (*) doesn=E2=80=99t work right = for him. This is not a surprise, as semver was developed and honed for software = versions, which are different from data model evolution. In any case, = semver version =E2=80=9Cnumbers=E2=80=9D are statements of intent that = can be (and often are) wrong; it is hard to version number version = numbers.) Gr=C3=BC=C3=9Fe, Carsten (*) https://tools.ietf.org/html/draft-ietf-netmod-yang-semver-01 Based on https://semver.org/ From nobody Sat Dec 12 23:55:58 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AC03A15B8 for ; Sat, 12 Dec 2020 23:55:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=RawdV8xJ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oPAlANuo Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nmslaUx2QQ1 for ; Sat, 12 Dec 2020 23:55:55 -0800 (PST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE2813A15B5 for ; Sat, 12 Dec 2020 23:55:54 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E9B8F5C00C5 for ; Sun, 13 Dec 2020 02:38:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 13 Dec 2020 02:38:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=wZFgu/RQWWx8l0F2+uar+Y2lOoTZrMUYRD/vJG0mmqc=; b=RawdV8xJ TXWxY+VqmQInOIeCky2rLoBLZgafc70OGs5la7Kl8fpvqEckwaxVHTv2jV52j05i uH3LaALEjuVL8zm6XhexwNcDmapYD5ze4JmcypzjJsz3WxIY1xgjduorxwXtAUie ZW+7pDvW+6rhv9SeBvSlIqgt53hflgXwnZxgXTE5V5GXDRJ/db/fKok2CBW3h/cp bzR2x7+Ukh6glMhgbmYmmOa5rb31J8gDg6xfYagL5MH/WpLR/qaNtV1a+nVtQzn/ arBW44A8ICp0cCcZR8QZTjgO6g6gQxQrJnW/FIxuZfuB0cHvfmsHuKM400UHiTMJ Qo3XoK9udoBsnA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=wZFgu/RQWWx8l0F2+uar+Y2lOoTZr MUYRD/vJG0mmqc=; b=oPAlANuoWJaGJ2S+A/ZqMItR7wZT4e3R4CkPzCUbhKS0P yW9xbstOBxZ4cQDkzJYKmpRhsaSGTJfBUMN9tgeDKVGd/NxrsXcgDnssM5f3V5oS uWFMRnFBqhf5gBiLtAmhfmG8RB51DyYskhHnjR+FeybQ/EXiMr4mhEGgtn0vgCeg fuJqrxubQutlpDgK3UrpZyc9nHBWi/WNcWYLB2oFKZXM/jrKEiRqnh4JJvx7z1dt X4hOS+zzAdgQybyKLmp8FURiqtcH1Wgnp7asTTA7gi1180cOJjpJ7Bl9WSRPTUlm wcM2vC3hujv+LQJkcM0FZfB4dIO2umAgkvOjUE1rg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudekhedgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppedufedrjeejrdekuddrud eileenucevlhhushhtvghrufhiiigvpeejnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght X-ME-Proxy: Received: from fv-az184-911.internal.cloudapp.net (unknown [13.77.81.169]) by mail.messagingengine.com (Postfix) with ESMTPA id BEFBE240057 for ; Sun, 13 Dec 2020 02:38:41 -0500 (EST) Content-Type: multipart/alternative; boundary="===============4351832351875366829==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: asdf@ietf.org Message-Id: <20201213073841.BEFBE240057@mailuser.nyi.internal> Date: Sun, 13 Dec 2020 02:38:41 -0500 (EST) Archived-At: Subject: [Asdf] Weekly github digest (ASDF Activity Summary) X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 07:55:56 -0000 --===============4351832351875366829== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; format="flowed" Events without label "editorial" Issues ------ * ietf-wg-asdf/SDF (+0/-2/=F0=9F=92=AC5) 5 issues received 5 new comments: - #7 Issue: does sdfRef add or also override? (1 by mjkoster) https://github.com/ietf-wg-asdf/SDF/issues/7=20 - #5 Feature: "anyOf" construct to model design pattern for overloaded pr= operty (1 by mjkoster) https://github.com/ietf-wg-asdf/SDF/issues/5=20 - #4 Feature: Composite sdfData types and sdfProperty types (1 by mjkoste= r) https://github.com/ietf-wg-asdf/SDF/issues/4=20 - #3 Feature: Allow reusable sdfProperty types (1 by mjkoster) https://github.com/ietf-wg-asdf/SDF/issues/3=20 - #2 Feature Request: SDF Enum Type (1 by mjkoster) https://github.com/ietf-wg-asdf/SDF/issues/2=20 2 issues closed: - Feature: Allow reusable sdfProperty types https://github.com/ietf-wg-as= df/SDF/issues/3=20 - Feature: Composite sdfData types and sdfProperty types https://github.c= om/ietf-wg-asdf/SDF/issues/4=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-asdf/SDF --===============4351832351875366829== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (ASDF Activity Summary)

Sunday December 13, 2020

Events without label "editorial"

Issues

ietf-wg-asdf/SDF (+0/-2/=F0=9F=92=AC5)

5 issues received 5 new comments:

2 issues closed:

Repositories tracked by this digest:

--===============4351832351875366829==-- From nobody Mon Dec 14 05:47:59 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8943A0ACB for ; Mon, 14 Dec 2020 05:47:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3VU99QPLiYF for ; Mon, 14 Dec 2020 05:47:54 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87CFA3A0AC4 for ; Mon, 14 Dec 2020 05:47:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id EB5DE3898E for ; Mon, 14 Dec 2020 08:50:26 -0500 (EST) Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jFc9HEYebtHM for ; Mon, 14 Dec 2020 08:50:26 -0500 (EST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 578953898C for ; Mon, 14 Dec 2020 08:50:26 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C608F53F for ; Mon, 14 Dec 2020 08:47:52 -0500 (EST) From: Michael Richardson To: asdf@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Dec 2020 08:47:52 -0500 Message-ID: <10879.1607953672@localhost> Archived-At: Subject: [Asdf] 2020-12-14: virtual interim meeting starting in 15 minutes X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2020 13:47:56 -0000 Hi, the agenda as posted did not include the webex link. The IETF datatracker does know it. Here is the complete agenda: --- # ASDF -- AGENDA for Virtual interim meeting ## Info Meeting: ASDF WG, Virtual interim, 1400-1530 UTC, Dec 14th, 2020 Location: Webex https://ietf.webex.com/ietf/j.php?MTID=3Dm0d089a7c8ac2d5a= 188c733c8107cb390 Chairs: Michael Richardson and Niklas Widell Etherpad/CodiMD: https://codimd.ietf.org/notes-asdf-2020-12-14 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D ## Agenda 1. Note Well. https://www.ietf.org/about/note-well/ 2. Logistics for Meeting. 2a. CodiMD for notes https://codimd.ietf.org/notes-asdf-2020-12-14 2b. Webex https://ietf.webex.com/ietf/j.php?MTID=3Dm0d089a7c8ac2d5a188c73= 3c8107cb390 2c. Agenda bash 3. WG status update (Chairs - 10 min) 3a. Welcome and discussion of WG proceedures 4. SDF 1.1 4a. Issues 5. W3C Web of Things collaboration (to be confirmed) 6. AOB? =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D ## Meeting material: draft-ietf-asdf-sdf https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/ SDF overview (from virtual interim) https://youtu.be/_8i6X4AxuOk (17 minut= es) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D From nobody Mon Dec 14 08:06:06 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CC43A11BD for ; Mon, 14 Dec 2020 08:06:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WNKUO1uPQcHp for ; Mon, 14 Dec 2020 08:06:03 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2BB3A11BE for ; Mon, 14 Dec 2020 08:06:02 -0800 (PST) Received: from [192.168.217.120] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CvmTP1kFHzyVJ; Mon, 14 Dec 2020 17:06:01 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 629654760.543373-ca826526a9d282c8424b97d314ace427 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Mon, 14 Dec 2020 17:06:00 +0100 Message-Id: To: asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] PR #9: Clarify sdfRef based on discussion at 2020-12-14 interim X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2020 16:06:06 -0000 https://github.com/ietf-wg-asdf/SDF/pull/9 Enjoy. Please comment in the PR and/or here. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Dec 14 09:27:32 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC8D3A1252 for ; Mon, 14 Dec 2020 09:27:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.003 X-Spam-Level: X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Su8Dq6x9cjMa for ; Mon, 14 Dec 2020 09:27:29 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EEAE3A1250 for ; Mon, 14 Dec 2020 09:27:28 -0800 (PST) Received: from [192.168.217.120] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CvpHM2Cy9zyRd; Mon, 14 Dec 2020 18:27:27 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 629659646.670191-6a99c8a78ac705a5079d85629d94eaa6 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Mon, 14 Dec 2020 18:27:26 +0100 Message-Id: <7A673423-2DF3-4658-B2ED-0AD1D712400E@tzi.org> To: asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] Updated PR #8 to today's compromise X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2020 17:27:32 -0000 I implemented the compromise we seem to have reached at today=E2=80=99s = interim in PR #8. I kept the name sdfChoice, as there haven=E2=80=99t been consistent = directions to use a different one. I also picked up the opportunity to restrict the =E2=80=9Cenum=E2=80=9D = shortcut to text strings only, as discussed. Comments welcome! https://github.com/ietf-wg-asdf/SDF/pull/8 https://github.com/ietf-wg-asdf/SDF/pull/8/files = https://raw.githack.com/ietf-wg-asdf/SDF/sdfchoice/sdf.html#name-sdfchoice= Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Dec 14 13:45:17 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A06C93A14AD for ; Mon, 14 Dec 2020 13:45:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1xk85w4D7sz for ; Mon, 14 Dec 2020 13:45:13 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47E9E3A14AE for ; Mon, 14 Dec 2020 13:45:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 273473898F for ; Mon, 14 Dec 2020 16:47:47 -0500 (EST) Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZkjAyeUrM65E for ; Mon, 14 Dec 2020 16:47:46 -0500 (EST) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 014D838988 for ; Mon, 14 Dec 2020 16:47:45 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 31AF818B for ; Mon, 14 Dec 2020 16:45:11 -0500 (EST) From: Michael Richardson to: asdf@ietf.org In-Reply-To: <10879.1607953672@localhost> References: <10879.1607953672@localhost> X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: [Asdf] notes from meeting -- 2020-12-14: virtual interim meeting starting in 15 minutes X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2020 21:45:16 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Uploaded presently at: https://github.com/ietf-wg-asdf/asdf-working-group-notes/blob/main/meetin= gs/minutes20201214.md please send pull-requests with edits. Niklas and I will upload to datatracker later this week. # ASDF -- AGENDA for Virtual interim meeting ## Info Meeting: ASDF WG, Virtual interim, 1400-1530 UTC, Dec 14th, 2020 Location: Webex https://ietf.webex.com/ietf/j.php?MTID=3Dm0d089a7c8ac2d5a1= 88c733c8107cb390 Chairs: Michael Richardson and Niklas Widell Etherpad/CodiMD: https://codimd.ietf.org/notes-asdf-2020-12-14 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D Blue sheet: 1. Michael Richardson 2. Niklas Widell 3. Ari Ker=C3=A4nen 4. Barry Leiba 5. Carsten Bormann 6. Francesca Palombini 7. Kaz Ashimura (W3C) 8. Kunihiko Toumura 9. Michael Koster 10. Nigel Davis 11. Tomoaki Mizushima 12. Wouter van der Beek 13. Michael Lagally 14. Klaus Hartke 15. Sebastian Kaebisch ## Agenda 1. Note Well. https://www.ietf.org/about/note-well/ 2. Logistics for Meeting. 2a. CodiMD for notes https://codimd.ietf.org/notes-asdf-2020-12-14 2b. Webex https://ietf.webex.com/ietf/j.php?MTID=3Dm0d089a7c8ac2d5a188c733= c8107cb390 2c. Agenda bash slides: https://datatracker.ietf.org/meeting/interim-2020-asdf-02/materials= /slides-interim-2020-asdf-02-sessa-slides-for-2020-12-14-asdf-virtual-inter= im-00 3. WG status update (Chairs - 10 min) 3a. Welcome and discussion of WG proceedures [slides 6, 7, 8, 9] Questions: Michael Koster quite a bit of external input to the model (4+ named). So the requirements that were collected were very broad, but we need to= finish the language before we can ask them to come back and contribute mod= els. Discussion about RFC vs Implementation Draft. 4. SDF 1.1 4a. Issues https://github.com/ietf-wg-asdf/SDF/issues/3 https://github.com/ietf-wg-asdf/SDF/issues/4 ACTION: create wiki page on what the different ecosystems are dealing w= ith converation to/from SDF. MK: mapping files (leverages JSON pointer).... also inline extension po= ints. WvdB: already a web page: https://onedm.org/terminology/ "pressure test" now needed. https://github.com/ietf-wg-asdf/SDF/issues/7 - sdfRef issue "This thing is like that thing, but this restriction does not apply" How can we set that part to "null"? _What if you do it the other way around? Then it is an extend!_ Subtypes vs overrides. Declaration vs Definition distinction. CB: When you say "override"... would it be okay to define RGB, and then= override...with a different colour scheme? (Answer NO) When say motor speed 0..255, but then restrict to 0..50. Convention that override is only used for subtyping, new type should be= a subtype. thus, we don't need to set qualities for null. https://github.com/ietf-wg-asdf/SDF/issues/2 https://github.com/ietf-wg-asdf/SDF/issues/5 enum and anyOf and mixes! Data Model vs Info Model The problem is reusing syntax from data modelling to do information mod= elling. YES: sdfChoice: https://github.com/ietf-wg-asdf/SDF/pull/8 . o O ( what MCR hears is that pure JSO pointer has to be extended, so = no common code ) SK points to: https://github.com/w3c/wot-thing-description/issues/997 consensus proposal: do not deprecate JSON Schema ORG ENUM, but *do* inc= lude solution for MK need. Will go into #8. 5. W3C Web of Things collaboration (to be confirmed) https://github.com/roman-kravtsov/sdf-object-converter Kaz mentios the [W3C liaison table for IETF](https://www.w3.org/2001/11/Std= Liaison#IETF) and suggests further discussin by email. 6. AOB? - discussion about liason needs. - =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D ## Meeting material: draft-ietf-asdf-sdf https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/ SDF overview (from virtual interim) https://youtu.be/_8i6X4AxuOk (17 minute= s) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D =2D- Michael Richardson . o O ( IPv6 I=C3=B8T consulti= ng ) Sandelman Software Works Inc, Ottawa and Worldwide --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/X3OYACgkQgItw+93Q 3WVlDAf+KEZFZE7akx1AkBp/Dm25Z4aJ6uyZ5fw01+EOn1HNyv7iqK4PcOPliqmA 1PoqNE+m4dBqsUB2VUFdrJy7BVBBpdRNKxgCDfm1l9Y78aOMR/KmeqZw9PquokeE sxLkAwL6rJFj3cVxNYMaJZ87WLteExXy0WUCtSR/xpf3EbMznzOO42EVJ0zICiip nBlXUVL08TxYrFZBp2qWXaxWHu8TiKETOBIX2a+muAaJ7+x8skQXGgIa4fes0QwP 2Eb3kKEN8bUsu2JSqUsWIiw88cXDQSmtJ/i/cTlwxOhMqhQlKNkI7YesusTHEwb6 qnc+hodkFxB2aOoL1sLO5kpaRa7hqA== =vv4D -----END PGP SIGNATURE----- --=-=-=-- From nobody Sat Dec 19 23:55:59 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94943A0BF5 for ; Sat, 19 Dec 2020 23:55:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Ufzg+Qsb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nFXeu/st Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZ4N7Us7Zfjs for ; Sat, 19 Dec 2020 23:55:55 -0800 (PST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7683A0BF4 for ; Sat, 19 Dec 2020 23:55:55 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B3A755C007D for ; Sun, 20 Dec 2020 02:40:39 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 20 Dec 2020 02:40:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=OBHc7A52sJI9rrmuRjVPwQuWq/T2Xq0bU4k0HlZZbo8=; b=Ufzg+Qsb WBHooklUbTRT4KNI+nY4OOMyR1T5whSasE8oHHXfMuDU+HAuPzy9I21euJTCls3W qnZ2uoUJGM0DpgNTU2fGsMuHa/hGA4npXa7x0fVVjsYCsvb+QR6da4QwIdoFCNeT D+3z/31mMczLBnDSDO2pKlBQdPA3tAm+4zrC1XVdE42OdTrApD6zUPozTI/Gvftl px6S09VLxDn0kcFlrvNUG49LR2ot75+LWoARkpItFaKGgk5fmSUb9yD4vFh/o694 DbR6rSNjYMKm04x3liYrNp5LFr12YEBmmcf22z0Ort/71WjJPSz/hJ6PX+dpv+OI 5I3EdescAn9wig== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=OBHc7A52sJI9rrmuRjVPwQuWq/T2X q0bU4k0HlZZbo8=; b=nFXeu/stDZlo7YvCVu/CK+GP61QyItHi7ytXyKvEjfsSz mzkyFigbQrUX8gSaR4zgMCYpTmjKe+XueEqBTiuH7tAVIdXQP4oofsB6U+8ErWVN 6drQdJXK/bDMjEyTTTjU+FZCXRJkyaiU/SliXqiF1TjgrM3hsGVlxGO00JF3Iztc Mr/v/v7ScvjzwylXPlc8FLm8ppZnYW58GGc4Z8Rj4x3Xc/vW63khH8ERMvVitifY DyOAS/bDV+q1fHhOoyKlPIJOtK/d3duBBCK0+flJQgVgbsyLBRVjelwrzLz2gkeX v5U3ZxufCpS6X80ML3gm22YDlBvE4jVFIPykc3m4g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudelledgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeegtddrjedtrdejuddrud dtleenucevlhhushhtvghrufhiiigvpeefnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght X-ME-Proxy: Received: from fv-az59-708.internal.cloudapp.net (unknown [40.70.71.109]) by mail.messagingengine.com (Postfix) with ESMTPA id 8BC311080057 for ; Sun, 20 Dec 2020 02:40:39 -0500 (EST) Content-Type: multipart/alternative; boundary="===============0194338463784043687==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: asdf@ietf.org Message-Id: <20201220074039.8BC311080057@mailuser.nyi.internal> Date: Sun, 20 Dec 2020 02:40:39 -0500 (EST) Archived-At: Subject: [Asdf] Weekly github digest (ASDF Activity Summary) X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2020 07:55:57 -0000 --===============0194338463784043687== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; format="flowed" Events without label "editorial" Issues ------ * ietf-wg-asdf/SDF (+0/-0/=F0=9F=92=AC1) 1 issues received 1 new comments: - #7 Issue: does sdfRef add or also override? (1 by cabo) https://github.com/ietf-wg-asdf/SDF/issues/7=20 Pull requests ------------- * ietf-wg-asdf/SDF (+2/-0/=F0=9F=92=AC0) 2 pull requests submitted: - Clarify sdfref based on discussion at 2020-12-14 interim. (by cabo) https://github.com/ietf-wg-asdf/SDF/pull/9=20 - Sdfchoice (by cabo) https://github.com/ietf-wg-asdf/SDF/pull/8=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-asdf/SDF --===============0194338463784043687== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (ASDF Activity Summary)

Sunday December 20, 2020

Events without label "editorial"

Issues

ietf-wg-asdf/SDF (+0/-0/=F0=9F=92=AC1)

1 issues received 1 new comments:

Pull requests

ietf-wg-asdf/SDF (+2/-0/=F0=9F=92=AC0)

2 pull requests submitted:

Repositories tracked by this digest:

 --===============0194338463784043687==-- From nobody Mon Dec 21 05:24:37 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3B23A0FD3 for ; Mon, 21 Dec 2020 05:24:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehhVSpa73x1o for ; Mon, 21 Dec 2020 05:24:32 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01493A0FCD for ; Mon, 21 Dec 2020 05:24:31 -0800 (PST) Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4D00Yn0tfMzyrW; Mon, 21 Dec 2020 14:24:29 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 630249868.411674-596cc267b2f97a308339065c0123b10e Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Mon, 21 Dec 2020 14:24:28 +0100 Message-Id: <4B57269E-2FEA-42D6-9EBD-E38E35197BA3@tzi.org> To: asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] PR #10: Describe next I-D as candidate implementation draft X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2020 13:24:35 -0000 Next steps:=20 * Bundle up #8, #9, and #10 into a -02 * Do a consensus-call of -02 as SDF 1.1 * Publish -03, marked as SDF 1.1 based on consensus (or not) Note that one PR is still missing: The JSO versions of the CDDL. I=E2=80=99m not entirely sure I will manage to generate that before -02, = but it definitely should be in -03. Gr=C3=BC=C3=9Fe, Carsten From nobody Sat Dec 26 23:56:07 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAADE3A048B for ; Sat, 26 Dec 2020 23:56:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Y8SE8YOF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=K/f2MCun Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E72mfUDSe-jg for ; Sat, 26 Dec 2020 23:56:01 -0800 (PST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A1E3A0544 for ; Sat, 26 Dec 2020 23:56:01 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 936407AB for ; Sun, 27 Dec 2020 02:49:42 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 27 Dec 2020 02:49:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=FLC8XxpwAtc41ny2AaYRQmrf2uetdvsY69cbmKsrQvs=; b=Y8SE8YOF hrUnMC0OhVIi2aNoYndaCLujI5PtwYuVxcNvUqNMghzUinU4u695ihD2YBkD6rAr qtfnSU5b2JPwNvSVgEWenmPh4vpAxlN5NEgnysbWkZd08qGtG7+aRJqGNxeKTwYO aofg9gtr7Xh+R6OWMWM+ovNbD3941EoPoj2wTrQg7dTUtpcP708YIr9hknt0rwfl S2qBx1KGErjnHPaNxspv2I8bWCwEFwNQ1ZPIxpNYLykIfIjeL86CNAyklAbMh5dp jZbqDQ1dL0ZX/0odcUl+7Uo0f1OvtDBNeLVQC7ny1yt0RqVhxpDELgVjyDA+JEod Oi3qUv7hVCigpA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=FLC8XxpwAtc41ny2AaYRQmrf2uetd vsY69cbmKsrQvs=; b=K/f2MCun/ghxioSkqxYBXqBqUJBMEPbCASxqYOc2+ACfi kIxLiDOldLzMYnNuNbaPCNpXZwA5HrYvROTOysP7nCQSHyZ095Pn3N++IQ2xP2y4 8Hr8EvUNe6LufFsaSl3XfQhLvSLWkf7yLihiXj4JQ7OCf7Ue+rUHbBrZhsYO1WwK l6EYzYLzyXpwruBFuq47OXTKEsoR9j78xOpZMb9maguDL+dXiyFYo6Wj15f/TgV2 bb/r+V33dZo3iVfiph7i0sBAUhLjit2yC7DoTy6Kn3Yj2/JIsfCGvtdyQ9113iKX 3YUx58gQFBItQFT+zA6aZw5XIoNAOb7KDr8fdc6rQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdduiedguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudei teenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeegtddrieehrddvtdehrd dvfeefnecuvehluhhsthgvrhfuihiivgepgeenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth X-ME-Proxy: Received: from fv-az60-573.internal.cloudapp.net (unknown [40.65.205.233]) by mail.messagingengine.com (Postfix) with ESMTPA id 11C8E24005B for ; Sun, 27 Dec 2020 02:49:42 -0500 (EST) Content-Type: multipart/alternative; boundary="===============4884065841051546834==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: asdf@ietf.org Message-Id: <20201227074942.11C8E24005B@mailuser.nyi.internal> Date: Sun, 27 Dec 2020 02:49:42 -0500 (EST) Archived-At: Subject: [Asdf] Weekly github digest (ASDF Activity Summary) X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2020 07:56:04 -0000 --===============4884065841051546834== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; format="flowed" Events without label "editorial" Issues ------ * ietf-wg-asdf/SDF (+1/-1/=F0=9F=92=AC0) 1 issues created: - When do we use "sdfXxx", when do we use "xxx"? (by cabo) https://github.com/ietf-wg-asdf/SDF/issues/11=20 1 issues closed: - Issue: does sdfRef add or also override? https://github.com/ietf-wg-asd= f/SDF/issues/7 [1.1] [has PR]=20 Pull requests ------------- * ietf-wg-asdf/SDF (+1/-1/=F0=9F=92=AC2) 1 pull requests submitted: - Describe candidate implementation draft procedure (by cabo) https://github.com/ietf-wg-asdf/SDF/pull/10=20 1 pull requests received 2 new comments: - #8 Sdfchoice (2 by WAvdBeek, cabo) https://github.com/ietf-wg-asdf/SDF/pull/8=20 1 pull requests merged: - Clarify sdfref based on discussion at 2020-12-14 interim. https://github.com/ietf-wg-asdf/SDF/pull/9=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-wg-asdf/SDF --===============4884065841051546834== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (ASDF Activity Summary)

Sunday December 27, 2020

Events without label "editorial"

Issues

ietf-wg-asdf/SDF (+1/-1/=F0=9F=92=AC0)

1 issues created:

1 issues closed:

Pull requests

ietf-wg-asdf/SDF (+1/-1/=F0=9F=92=AC2)

1 pull requests submitted:

1 pull requests received 2 new comments:

1 pull requests merged:

Repositories tracked by this digest:

--===============4884065841051546834==-- From nobody Mon Dec 28 16:02:50 2020 Return-Path: X-Original-To: asdf@ietfa.amsl.com Delivered-To: asdf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2698C3A0EFB; Mon, 28 Dec 2020 16:02:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFlXCumdXO_J; Mon, 28 Dec 2020 16:02:40 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C5323A0EF9; Mon, 28 Dec 2020 16:02:38 -0800 (PST) Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4D4ZNn04ZJzySQ; Tue, 29 Dec 2020 01:02:32 +0100 (CET) From: Carsten Bormann Content-Type: multipart/alternative; boundary="Apple-Mail=_28C2E0E8-D0E6-4871-BBE2-4800E2B01141" X-Mao-Original-Outgoing-Id: 630892953.982962-594906e021fda5f70c9ec3d55e5d42a9 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Tue, 29 Dec 2020 01:02:34 +0100 Message-Id: References: To: cbor@ietf.org, asdf@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Asdf] Fwd: Invitation to comment on Specification for JSON Abstract Data Notation v1.0 - ends January 27th X-BeenThere: asdf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2020 00:02:44 -0000 --Apple-Mail=_28C2E0E8-D0E6-4871-BBE2-4800E2B01141 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 This is an interesting piece of work, somewhat related to both CDDL and = SDF, and (contrary to its JSON-centric name) with a CBOR-related generic = data model and CBOR serialization rules. =20 I don=E2=80=99t have an immediate opinion how this might become useful = for IETF work, but it certainly exhibits an elaborate set of design = choices worth pondering. Gr=C3=BC=C3=9Fe, Carsten > Begin forwarded message: >=20 > From: Paul Knight > Subject: Invitation to comment on Specification for JSON Abstract Data = Notation v1.0 - ends January 27th > Date: 2020-12-28 at 23:38:26 CET > To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, = OASIS TAB , openc2@lists.oasis-open.org, = openc2-comment@lists.oasis-open.org > Message-Id: = >=20 > OASIS members and other interested parties, >=20 > OASIS and the OASIS Open Command and Control (OpenC2) TC are pleased = to announce that Specification for JSON Abstract Data Notation Version = 1.0 is now available for public review and comment. This is the first = public review for this specification. >=20 > JSON Abstract Data Notation (JADN) is an information modeling = language. It has several purposes including defining data structures, = validating data instances, informing user interfaces working with = structured data, and facilitating protocol internationalization. JADN = specifications consist of two parts: abstract type definitions that are = independent of data format, and serialization rules that define how to = represent type instances using specific data formats. A JADN schema is = itself a structured information object that can be serialized and = transferred between applications, documented in multiple formats such as = text-based interface definition languages, property tables or diagrams, = and translated into concrete schemas used to validate specific data = formats. >=20 > The documents and related files are available here: >=20 > Specification for JSON Abstract Data Notation Version 1.0 > Committee Specification Draft 01 > 21 October 2020 >=20 > Editable source: > https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.md = >=20 > HTML: > = https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.html = >=20 > PDF (Authoritative): > https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.pdf = >=20 > For your convenience, OASIS provides a complete package of the = specification document and any related files in ZIP distribution files. = You can download the ZIP file at: > https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.zip = >=20 > How to Provide Feedback >=20 > OASIS and the OpenC2 TC value your feedback. We solicit input from = developers, users and others, whether OASIS members or not, for the sake = of improving the interoperability and quality of our technical work. >=20 > The public review starts 29 December 2020 at 00:00 UTC and ends 27 = January 2021 23:59 UTC. >=20 > Comments may be submitted to the TC by any person through the use of = the OASIS TC Comment Facility, which can be used by following the = instructions on the TC's "Send A Comment" page = (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=3Dopen= c2 = ). >=20 > Comments submitted by TC non-members for this work and for other work = of this TC are publicly archived and can be viewed at: > https://lists.oasis-open.org/archives/openc2-comment/ = >=20 > All comments submitted to OASIS are subject to the OASIS Feedback = License, which ensures that the feedback you provide carries the same = obligations at least as the obligations of the TC members. In connection = with this public review, we call your attention to the OASIS IPR Policy = [1] applicable especially [2] to the work of this technical committee. = All members of the TC should be familiar with this document, which may = create obligations regarding the disclosure and availability of a = member's patent, copyright, trademark and license rights that read on an = approved OASIS specification. >=20 > OASIS invites any persons who know of any such claims to disclose = these if they may be essential to the implementation of the above = specification, so that notice of them may be posted to the notice page = for this TC's work. >=20 > Additional information about the specification and the OpenC2 TC can = be found at the TC's public home page: > https://www.oasis-open.org/committees/openc2/ = >=20 > Additional information related to this public review can be found in = the public review metadata document [3]. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Additional references: >=20 > [1] https://www.oasis-open.org/policies-guidelines/ipr = >=20 > [2] https://www.oasis-open.org/committees/openc2/ipr.php = > https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode = > Non-Assertion Mode >=20 > [3] Public review metadata document: > - = https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01-public-= review-metadata.html = > --=20 >=20 > Paul Knight > Document Process > OASIS Open >=20 >=20 > +1 781-883-1783 > paul.knight@oasis-open.org > www.oasis-open.org --Apple-Mail=_28C2E0E8-D0E6-4871-BBE2-4800E2B01141 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 This = is an interesting piece of work, somewhat related to both CDDL and SDF, = and (contrary to its JSON-centric name) with a CBOR-related generic data = model and CBOR serialization rules.  
I don=E2=80=99t = have an immediate opinion how this might become useful for IETF work, = but it certainly exhibits an elaborate set of design choices worth = pondering.

Gr=C3=BC=C3=9Fe, Carsten


Begin forwarded message:

From: = Paul Knight <paul.knight@oasis-open.org>
Subject: = Invitation to = comment on Specification for JSON Abstract Data Notation v1.0 - ends = January 27th
Date: 2020-12-28 at 23:38:26 CET
To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, OASIS TAB <tab@lists.oasis-open.org>, openc2@lists.oasis-open.org, openc2-comment@lists.oasis-open.org
Message-Id: <CADgeAH8ZHQaFPKd5N8Rfk=3D2xORZHHFDw=3D7eEk7k0cVhOG42nEw@mail.gm= ail.com>

OASIS members and = other interested parties,

OASIS and the = OASIS Open Command and Control (OpenC2) TC are pleased to announce that = Specification for JSON Abstract Data Notation Version 1.0 is now = available for public review and comment. This is the first public review = for this specification.

JSON Abstract Data = Notation (JADN) is an information modeling language. It has several = purposes including defining data structures, validating data instances, = informing user interfaces working with structured data, and facilitating = protocol internationalization. JADN specifications consist of two parts: = abstract type definitions that are independent of data format, and = serialization rules that define how to represent type instances using = specific data formats. A JADN schema is itself a structured information = object that can be serialized and transferred between applications, = documented in multiple formats such as text-based interface definition = languages, property tables or diagrams, and translated into concrete = schemas used to validate specific data formats.

The documents and related files are available here:

Specification for JSON Abstract Data Notation = Version 1.0
Committee Specification Draft 01
21 October 2020

Editable = source:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-cs= d01.md

HTML:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-cs= d01.html

PDF (Authoritative):
https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-cs= d01.pdf

For your convenience, OASIS = provides a complete package of the specification document and any = related files in ZIP distribution files. You can download the ZIP file = at:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-cs= d01.zip

How to Provide Feedback

OASIS and the OpenC2 TC value your feedback. = We solicit input from developers, users and others, whether OASIS = members or not, for the sake of improving the interoperability and = quality of our technical work.

The public = review starts 29 December 2020 at 00:00 UTC and ends 27 January 2021 = 23:59 UTC.

Comments may be submitted to the = TC by any person through the use of the OASIS TC Comment Facility, which = can be used by following the instructions on the TC's "Send A Comment" = page (https://www.oasis-open.org/committees/comments/index.php?wg_abb= rev=3Dopenc2).

Comments submitted by TC = non-members for this work and for other work of this TC are publicly = archived and can be viewed at:
https://lists.oasis-open.org/archives/openc2-comment/

All comments submitted to OASIS are subject to = the OASIS Feedback License, which ensures that the feedback you provide = carries the same obligations at least as the obligations of the TC = members. In connection with this public review, we call your attention = to the OASIS IPR Policy [1] applicable especially [2] to the work of = this technical committee. All members of the TC should be familiar with = this document, which may create obligations regarding the disclosure and = availability of a member's patent, copyright, trademark and license = rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to = disclose these if they may be essential to the implementation of the = above specification, so that notice of them may be posted to the notice = page for this TC's work.

Additional = information about the specification and the OpenC2 TC can be found at = the TC's public home page:
https://www.oasis-open.org/committees/openc2/

Additional information related to this public = review can be found in the public review metadata document [3].

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Additional = references:

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/openc2/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertio= n-Mode
Non-Assertion Mode

[3] Public review metadata document:
- https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-cs= d01-public-review-metadata.html
--

Paul Knight

Document Process
OASIS Open

+1 781-883-1783
paul.knight@oasis-open.org
www.oasis-open.org

= --Apple-Mail=_28C2E0E8-D0E6-4871-BBE2-4800E2B01141--