Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
  • Sign in
S
saref-core
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 18
    • Issues 18
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • SAREF
  • saref-core
  • Issues
  • #8

Closed
Open
Opened May 22, 2019 by lefranois@lefranois
  • Report abuse
  • New issue
Report abuse New issue

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
1 - Needs discussion Enhancement
Assign labels
  • View project labels
Reference: SAREF/saref-core#8