Producer definition

[sebastiankb]

fixes #656

Producer definition for terminology section

---

Preview | Diff

[mlagally]

@sebastiankb
"... for a specific Thing" sounds like a limitation and I think it is more generic.

Suggest "for a specific Thing or multiple Things" or to just remove that part of the definition.

[mlagally]

Is this a limitation?

[mmccool]

This exactly corresponds to the term "Generator" that I proposed in my comment. I'm ok with "Producer" under this specific definition, however. As long as we are clear that "Exposer != Provider != Producer", since these might all be separate entities.

[egekorkan]

"... for a specific Thing" sounds like a limitation and I think it is more generic.

Well, a Producer can write multiple TDs but a TD is for a single Thing. But there is an extra s there I think.

[mlagally]

Arch call on Jan 27th:

Other specifications use "Exposer", relationship should be defined. Please seek alignment.
Exposer does not imply generating a TD.
"TD Producer" could be used to make it more unambiguous
A directory service is a producer, however the current text talks about "a thing" which could be read as a limitation.

[benfrancis]

This definition looks OK to me, but how about simply "An entity which generates WoT Thing Descriptions."

It would simpler if there were just two roles:

• Producer - Generates and exposes the metadata and interfaces of a Thing
• Consumer - Processes and interacts with the metadata and interfaces of a Thing

The reality seems to be more complex, and the roles can be broken down as (paraphrasing):

• Thing - An abstraction of a physical device whose capabilities and interfaces are described by a Thing Description
• Thing Description - Describes the capabilities and interfaces of a Thing
• Producer - Produces Thing Descriptions for one or more Things
• Exposer - Exposes Thing Descriptions for one or more Things
• Consumer - Processes Thing Descriptions and interacts with Things