- It should be possible to express the fact that User can discover Services,
that Services can discover Resources, that Resources can discover
Resources (to be discussed which combinations make most sense); - Some links between IoT Domain Model and IoT Information Model
should be explicitly described within the IoT Domain Model, like ―*-
description publishing‖ - Discovery and publishing are important concepts in IoT they should be
very visible in the IoT Domain model as said in 7/ and 8/ - We don‘t show here the reverse mapping to the IoT Information model,
but it was pretty clear that the IoT Information Model is a meta-model that
cannot really be used to model the class structure of the EPCglobal data
handled at the different levels in the architecture (e.g. at Tag level,
reader level, Filtering & Collection etc...), in particular the IoT Information
Model does not consider events (and EPCglobal is intensively using the
notion of event). We reckon that most likely this is not the role of the IoT
Information Model to model in a fine-grained way the class structure of a
software system, especially when the class structure is clearly not IoT-
specific.
elliott
(Elliott)
#1