Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S saref-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SAREF
  • saref-core
  • Issues
  • #8

Closed
Open
Created May 22, 2019 by Maxime Lefrançois@lefranoisOwner

Think of naming patterns Command / Device / command

Affects: SAREF and its extensions Situation: instances of patterns may be identified in SAREF, but sometimes only partially, and with naming heterogeneities

procedure act obs notif meter
name of the command ActuatingCommand SensingCommand NotifyingCommand MeteringCommand
name of the device Actuator Sensor Notifier Meter
link between device and property actsUpon observes notifiesAbout measures

Proposal: There should be a clear classification/hierarchy that is common to Commands, Devices, Functions. And properties. The current relation between commands and devices is partial and misleading.

Status: discussions started

Assignee
Assign to
Time tracking