TD Processor definition contain assertions

[egekorkan]

The definition for the TD Processor is currently:

• A system that can serialize some internal representation of a Thing Description in a given format and/or deserialize it from that format. A TD Processor must detect semantically inconsistent Thing Descriptions, that is, Thing Descriptions that cannot satisfy constraints on the Instance Relation of the Thing class. For that purpose, a TD Processor may compute forms of Thing Descriptions in which all possible Default Values are assigned. A TD Processoris typically a sub-system of a WoT Runtime. Implementations of a TD Processor may be a TD producer only (able to serialize to TD Documents) or a TD consumer only (able to deserialize from TD Documents).

Even though this is purely a definition, it contains 3 sentence with assertion-like meaning. This is problematic because:

• I am pretty sure that definitions should not contain assertions
• If they can contain, they should use the span and RFC keywords, otherwise they are not picked up testing tools and possibly implementors.
• We do not see this kind of sentences as the working group. This text is very assertive on what a consumer should do, i.e. it says that a processor should detect invalid TDs. We have written a whole validation chapter but it does not exactly correlate perfectly with this definition.

In my opinion, these 3 sentences should be removed from the definition and placed elsewhere.