Expired
Milestone
Sep 28, 2023–Jul 31, 2024
Display by
Error fetching burnup chart data
Burndown chart
Remaining
Burnup chart
Total
Completed
Ongoing Issues (open and assigned)
30
- Promote fabrication and versioning metadata to Core
- Should extensions define individuals of the class saref:FeatureOfInterest ?
- Modeling System capabilities
- Promotion of triggers and isTriggeredBy ?
- Promotion of MemoryStorage, PowerSupply, Software, User ?
- Delete s4wear:hasCommand
- isLocatedIn / isLocatedNear / isLocatedOn
- Modeling the power supply of devices
- Promotion of s4wear:controlsFeature, s4wear:measuresFeature and inverses
- Modeling of time series ?
- Explicit what property sensors measure ?
- Modeling events
- Highly generic properties
- Use of SKOS in extensions
- Pattern for specializing saref:Function ?
- PhysicalObject in SAREF ?
- Decoupling kinds of evaluations and kinds of properties
- Spatial ontologies
- W3C Time ontology
- Stop hijacking SAREF Core terms
- Extensions copy declarations and definitions from SAREF Core
- Use the same local name in specializations
- SAREF4WEAR-2. The extension defines domain restrictions on saref:Device
- SAREF4WEAR-1. The extension defines restrictions on saref:Device
- Harmonise the way of representing geospatial information
- Harmonise naming of properties "hasX" versus "X"
- Use naming pattern: Command / Device / command.
- Harmonise modeling pattern for Property taxonomy: Specific vs Generic, or both, or separate ?
- Property individuals used differently
- Reconcile ontological types of same-named SAREF entities.
Loading
Loading
Loading