Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S saref4bldg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SAREFSAREF
  • saref4bldg
  • Issues
  • #5
Closed
Open
Issue created Apr 07, 2021 by Maxime Lefrançois@lefranoisOwner

Wrong local restriction on saref:Measurement

The ontology contains the following axiom:

saref:Measurement rdfs:subClassOf _:genid315 .

_:genid315 a owl:Restriction ;
	owl:onProperty saref:hasValue ;
	owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ;
	owl:onDataRange xsd:float .

As per SAREF V3.1.1, this axiom no longer holds. IT creates an issue for measurements with other datatypes such as integers or durations, as in example https://saref.etsi.org/saref4lift/v1.1.1/example/TS103735_Clause_6_15_BCSSignals#

Assignee
Assign to
Time tracking