search

w3c / wot-profile

Web of Things (WoT) Profile
http://w3c.github.io/wot-profile/
Other
16 stars 8 forks source link

Normative Canonicalisation format #132

Open mlagally opened 3 years ago

mlagally commented 3 years ago

We need a normative canonicalisation format in the profile specification. This depends on the testability, i.e. 2 implementations. The TD should make a definition the profile should reference it.

benfrancis commented 3 years ago

We need a normative canonicalisation format in the profile specification.

Since the current WoT Profile 1.0 draft does not use canonicalisation (previous drafts did, but those references have now been removed), are there features you think are currently missing from the specification which would rely on canonicalisation?

The TD should make a definition the profile should reference it.

See section 6.6 Canonicalization of the WoT Thing Description 1.1 specification.

mlagally commented 3 years ago

Canonical TDs help to identify if two different TDs describe the same thing. Determining identity is a simple string comparison.

Usually there are globally unique IDs for that purpose, however during the publication of the 1.0 TD specification there were concerns raised that a unique ID may cause privacy issues.

egekorkan commented 3 years ago

I agree that canonicalisation is important but how does it help the interoperability claim of the core profile? I think how it is used should made more clear

mlagally commented 3 years ago

@ege, @benfrancis : without canonicalisation and a unique id, a consumer is not able to check identity of 2 TDs that describe the same thing.

egekorkan commented 3 years ago

But why should I do that in the first place a profile compliant consumer? What is the use case?

mlagally commented 2 years ago

arch call on 25.11. The term "canonicalisation" is no longer appropriate, however the TD section on canonicalisation contains several constraints. These constraints should be moved out of the TD and constraints are considered for inclusion in the profile. Canonical format is not a requirement at this point.

mlagally commented 2 years ago

After the TD has defined a canonicalisation format, Profile 2.0 will adopt it.