Skip to content

Releases

v2.1.0 — Follow CaSk 5.3.0 (units of measure)

Choose a tag to compare

@Miguel2617 Miguel2617 released this 13 Nov 14:46

Follows CaSk 5.3.0, which adds units of measure.

The only change of its own is the import IRI, from cask/5.2.0 to cask/5.3.0. No axiom of this ontology is added, removed or tightened, so the version stays minor and existing A-boxes are unaffected.

What CaSkBot inherits from that version:

  • CaSk:hasUnit, a functional object property from DINEN61360:Type_Description to qudt:Unit, so that the unit of a property is a term that can be checked and converted instead of a string.
  • All 2940 units of the QUDT unit vocabulary and the 230 quantity kind dimension vectors they refer to, shipped as individuals. QUDT itself is not imported; the seven QUDT terms used are declared in cask.ttl.
  • The removal of a restriction owl:onProperty rdfs:isDefinedBy on OM-Math:Symbol, which took the OWL 2 DL profile violations of this ontology's import closure from 1599 down to 318. Of those 318, 303 come from the GeoSPARQL document itself and 15 from OpenMath's use of RDF collections; neither is fixable from here.

Verified with HermiT over the full import closure, resolved through the published version IRIs: consistent, no new unsatisfiable classes.

v2.0.0 — Zones carry a GeoSPARQL geometry

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

Zones carry a GeoSPARQL geometry.

A zone and its spatial extent are now two different things. caskbot:Zone is a geo:Feature with caskbot:RestrictedZone and the new caskbot:OperatingZone below it, the extent hangs on the zone through geo:hasGeometry and is a POS:PositionRegion, which the new bridge axiom POS:PositionRegion rdfs:subClassOf geo:Geometry also makes a geo:Geometry. The shape is a WKT literal and carries its coordinate reference system inside the literal. caskbot:zoneAppliesTo states whether a zone holds for a kind of platform or for an individual robot, and caskbot:hasOperatingZone is the counterpart of caskbot:hasRestrictedZone.

Breaking change. Up to 1.25.2 caskbot:RestrictedZone was a subclass of POS:PositionRegion and therefore, through POS:PositionMeasure, a physical quantity. GeoSPARQL declares geo:Feature and geo:Geometry disjoint, so that modelling would have made the import closure inconsistent. Data that typed a zone as a position region has to move the extent into a geo:hasGeometry of its own.

GeoSPARQL 1.1 (OGC 22-047r1) is imported from the OGC repository pinned to commit 0198218, because the version IRI the ontology declares for itself, http://www.opengis.net/ont/geosparql/1.1, does not resolve, and the unversioned IRI serves a catalogue page rather than the axioms.

Verified with HermiT over the full import closure: consistent, no new unsatisfiable classes.

v1.25.2 — Follow RobotCapabilities 2.0.2

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

Patch over 1.25.1: the import follows RobotCapabilities 2.0.2. No axiom of
this ontology is touched.

v1.25.1 — Follow RobotCapabilities 2.0.1

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

Patch over 1.25.0: the import follows RobotCapabilities 2.0.1, so that the
version IRI asked for and the one the pattern declares agree.

v1.25.0 — Bind RobotCapabilities with one axiom

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

RobotCapabilities 2.0.0 stands alone and imports nothing, so the axiom that
makes its types capabilities in the sense of CSS is here:
RobotCap:RobotCapability under CSS:Capability. Nine subclass axioms inside the
pattern become one alignment axiom in this ontology.

v1.24.0 — Align the MQTT ODP, invocation side only

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

The MQTT ODP 6.0.1 is aligned on the invocation side: MqttSkillInterface,
accessibleThroughMqttInterface, invokedByTopic and reachableViaMqttServer,
built as their REST counterparts.

The subscription side -- maximum QoS, topic filters, sessions -- and
MQTT:MQTTClient stay unaligned.

v1.23.1 — Comments in English

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

Patch over 1.23.0: the Turtle comments are in English and no longer point at
documents outside this repository. The 19 lines naming the alignment
mechanism after Hildebrandt et al. (2020) stay.

Comment-only change. The graph is isomorphic to 1.23.0 apart from the version
annotations.

v1.23.0 — Alignment ontology for capabilities and skills of autonomous robots

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59

The robotics layer of the three-level CaSkade architecture: it aligns the
capability and skill model of CSS and CaSk with IEEE 1872 (CORA, CORAX,
RPARTS, POS), IEEE 1872.2 and the WADL ODP, so that autonomous robots, their
structure, position, environment and interactions are described together with
the capabilities they provide. The MQTT interface is not yet aligned.

First release in this repository. Earlier versions are not part of its
history.