-
Key: ROSO-7
-
Status: open
-
Source: JARA ( Mr. Koji Kamei)
-
Summary:
Every component parameter in RoIS 1.2 (and the RoIS 2.0 draft, if possible) must be instantiated and described in relation to the component.
As an example of detail missing for a PSM, there is a class named Direction with no properties or definitions for how a specific direction would be represented. -
Reported: ROSO 1.0b1 — Mon, 20 May 2024 14:06 GMT
-
Updated: Sat, 9 Nov 2024 15:45 GMT
-
Attachments:
- Classes for Person Detection.svg 23 kB (image/svg+xml)
- RoIS Parameters.svg 19 kB (image/svg+xml)
- Robotic Service Function Ontology (OWL classes).svg 20 kB (image/svg+xml)
- Robotic Service Function Ontology (OWL properties).svg 21 kB (image/svg+xml)
- RoboticInteactionServiceComponentOntology.rdf 11 kB (application/rdf+xml)
- RoboticServiceFunctionOntology.rdf 5 kB (application/rdf+xml)
- RoboticServiceInteractionOntology.rdf 12 kB (application/rdf+xml)
- RoboticServiceOntology.rdf 17 kB (application/rdf+xml)
ROSO — Definition of RoIS parameters to be described by name in addition to classes.
- Key: ROSO-7
- OMG Task Force: Robotic Service Ontology (RoSO) 1.0 FTF
