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
  • #26

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

Move unit classes to examples

Affects: SAREF

Situation: SAREF contains the classes saref:IlluminanceUnit, saref:PowerUnit, saref:PressureUnit, saref:TemperatureUnit, saref:EnergyUnit. However, they are not mentioned in the SAREF TS document. There are classes for these units in OM, QUDT, or even a datatype for this in cdt:ucum. Also, their definition is "The unit of measure for { ?label }". This is misleading as this is a class, not an instance. There is usually more than one unit of measure for a quantity kind

Proposal: delete these classes, moved to specific instance files using the ontology under consideration and that people can download to understand how SAREF can be used

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#26