FPWD Feedback from Cristiano

[relu91]

Security Element

In current spec, the security element allows an array of strings. However, as far as I know, it is not well tested/understood feature of the TD. For example, node-wot does not implement this mechanism. Considering that in the future TD will have a dedicated SecuritySchema to handle combinations, should we constraint this field to just a simple string?

Data Schema Constraints

Format type constraint as the others (i.e. in section 5.1.4): one of boolean, integer, number, string, array or object -> one of boolean , string , number , integer , object or array . The type value null MUST NOT be used.

Action Affordances

objectSchema -> ObjectSchema (probably we could also link it to TD spec)

[mlagally]

Arch call on 21.1.:
Security related comment willl be discussed in next call,
@relu91 will create a MR for the other two topics.

[mlagally]

@relu91
The corresponding text on DataSchema constraints and Action Affordances is no longer part of Profile-1.0
Security related questions are discussed in several other issues, e.g. #221 and #220.

Suggest to close this issue.