Requirements

The following table lists the VICINITY WoT ontology requirements and the VICINITY WoT ontology satisfies them.

There are four possible results for each requirement:

• : The requirements is passed by the ontology
• Undefined: There are terms in the requirements that are not defined in the ontology
• : The are relations and restrictions in the requirements that are absent in the ontology
• : There is a conflict between the requirement and the ontology

Identifier	Category	Competency Question	Result
WoT1	Thing	What is a thing in the web thing context?
WoT15	Property	What is a property?
WoT16	Action	What is an action?
WoT17	Event	What is an event?
WoT21	Thing	A thing interaction can be available over different or multiple protocols
WoT22	Protocol	What is a protocol?
WoT24	Thing	Each thing has at least an interaction pattern
WoT25	Interaction pattern	An interaction pattern can have different endpoints
WoT26	Interaction pattern	Each interaction pattern has its own attributes
WoT27	Interaction pattern	Each interaction pattern has an endpoint
WoT28	Interaction pattern	Each endpoints has minimun two attributes URI and mediatype
WoT29	Security	Security is associated with things
WoT31	Link	An endpoint can be associated with a thing without determine the interaction patterns
WoT32	Link	Each interaction pattern has a name and a Web Resource address
WoT33	Interaction	An interaction has a type and attributes
WoT34	Interaction	An interaction has a type and attributes
WoT35	Interaction pattern	Each interaction pattern can be readable or writable through an endpoint

Metrics

The following table summarises the metrics related to the VICINITY WoT ontology

Metric	Result
Percentage of covered requirement	100%
Percentage of requirements with terms that are undefined in the ontology	0%
Percentage of requirements that lead to conflict	0%
Percentage of tested terms	48.64%