Model Design Guidelines

Please capture considerations for a Model Design Guidelines document here.

• What should be modelled as object / affordance / sdfData (/ Thing)

  • identifying atomic, re-usable parts
    • "value of sensor" -> data
    • "get current value" -> affordance
    • "temperature sensor" -> object
    • "fridge" -> thing

• What kind of things should go to the SDF model and what to a mapping file

  • eco-system specifics (e.g., LwM2M IDs) and protocol details (e.g., if value is bitfield or set of booleans) to mapping file

• How to model special structures (bit fields, arrays, objects..)

  • useful to break down to separate affordances to give control (defined terms, descriptions, interactions, etc.) on SDF level
  • sometimes(?) better as a single data type
    • sub-structure defined with sdfData definitions

• How to name things

  • names are interpreted in the context (e.g., affordance name "current value" in the context of object "temperature" means "current value of temperature")
  • not adding structure to names of a single definition but building hierarchy of names