Re: problem parsing TD securityDefinitions

• From: Kaebisch, Sebastian <sebastian.kaebisch@siemens.com>
• Date: Fri, 19 Jun 2020 14:18:50 +0000
• To: Nikos Fotiou <fotiou@aueb.gr>, "public-wot-wg@w3.org" <public-wot-wg@w3.org>
• Message-ID: <DEBEB9AA-28F9-470F-9B88-9DF0C8250AFE@siemens.com>

Hi Nikos,

many thanks for your mail.

I think, there is a mistake in the context file. The security declaration contains items that should actually be covered in the securityDefinitions and vice versa.

I will double check this and we have to fix this soon.

Thanks
Sebastian

Am 19.06.20, 15:30 schrieb "Nikos Fotiou" <fotiou@aueb.gr>:

    Hi, 
    I am wondering if somebody can help me with the following. I have this TD (extracted from the specifications examples).

    {
      "@context": "https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%2Fv1&amp;data=02%7C01%7Csebastian.kaebisch%40siemens.com%7Cead64d01e56542aa5c2c08d81454e451%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C1%7C637281702128711076&amp;sdata=s%2B3428ylFHHH8kmKRrh7ZN4o2Vo1x2C8UP6AqGThOtY%3D&amp;reserved=0",
      "id": "urn:dev:ops:32473-WoTLamp-1234",
      "title": "MyLampThing",
      "securityDefinitions": {
        "basic_sc": {
          "scheme": "basic",
          "in": "header"
        }
      },
      "security": [
        "basic_sc"
      ]
    }

    I try to parse it with https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frdf.greggkellogg.net%2Fdistiller&amp;data=02%7C01%7Csebastian.kaebisch%40siemens.com%7Cead64d01e56542aa5c2c08d81454e451%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C1%7C637281702128711076&amp;sdata=6teJWzLFI1201tzF8sRw7T%2Bgo7w96LuzAf8zr%2FtyboI%3D&amp;reserved=0 and json-ld playground https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjson-ld.org%2Fplayground%2F&amp;data=02%7C01%7Csebastian.kaebisch%40siemens.com%7Cead64d01e56542aa5c2c08d81454e451%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C1%7C637281702128711076&amp;sdata=ToYaSCtWIiBqGLoJnMuEhyGEMxYMv4B%2BSkWp7Gn4OAQ%3D&amp;reserved=0


    Both parsers miss the  "scheme"  and "in" parameters. They only see them if I add a "@type" inside "basic_sc", i.e.,

    "basic_sc": {
          "@type":"security",
          "scheme": "basic",
          "in": "header"
        }

    But this is not reasonable.

    I have opened this issue but still I haven’t managed to find the solution https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwot-thing-description%2Fissues%2F915&amp;data=02%7C01%7Csebastian.kaebisch%40siemens.com%7Cead64d01e56542aa5c2c08d81454e451%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C1%7C637281702128711076&amp;sdata=SfTOoClqsahMtJ6eriPpE2K7yvLVSqpWYVq6z8izMPI%3D&amp;reserved=0


    Best,
    Nikos

Received on Friday, 19 June 2020 14:19:05 UTC