You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at unusual schema subclasses, I stumbled upon these two:
croissant:SegmentationMask a rdf:class ;
rdfs:label "SegmentationMask" ;
rdfs:comment "A data type representing a segmentation mask." ;
rdfs:subClassOf schema:StructuredValue .
A segmentation mask is an array of pixels, right? Then schema:StructuredValue, if you look at its properties, is not at all appropriate.
You could use xsd:base64binary for the payload, but should also describe dimensions (width, height, pixel bit size).
croissant:BoundingBox a rdf:class ;
rdfs:label "Label" ;
rdfs:comment "A data type representing a bounding box." ;
rdfs:subClassOf schema:Text .
The idea is to be able to specify the bounding box using different formats, which schema.org/box doesn't allow.
In general, with Croissant, we tried to define a format which can be used to describe datasets packaged with most common formats, without imposing a particularly way of packaging such datasets (either file format, or data format).
Looking at unusual schema subclasses, I stumbled upon these two:
A segmentation mask is an array of pixels, right? Then schema:StructuredValue, if you look at its properties, is not at all appropriate.
You could use xsd:base64binary for the payload, but should also describe dimensions (width, height, pixel bit size).
geosparql:wktLiteral
datatype (but I think that's overkill for a simple bounding box)The text was updated successfully, but these errors were encountered: