Subproperties of hasBooleanValue

[mereolog]

The current subproperties of hasBooleanValue looks wrong when applied to instances:

Consider for example gram:

Because gram has the property isSIQuantity it also has the property hasBooleanValue. The former makes sense, the latter less so: what could it mean that gram has a Boolean value?

[ElisaKendall]

@mereolog - these are all subproperties of the IDMP has boolean value property because they are tagged with 'BL' from the ISO IDMP datatypes standard. We could eliminate that, but the relationships are in the standard. I could rename it once we have the tag for deviating from the standard?

[mereolog]

Fair enough, but then shouldn't these be instances of a (new) subtype of owl:DatatypeProperty by the name of hasBooleanValue (instead of being its sub properties)?

[ElisaKendall]

@mereolog There is a datatype in the harmonized datatypes ontology for these boolean values already, and a code for it 'BL', but Heiner and I agreed that we would use the xsd types in the ontology, at least for the MVP, to simplify the implementation. There is a page in Confluence, at https://wiki.edmcouncil.org/pages/viewpage.action?pageId=86474903 that talks about this.

[mereolog]

@mereolog There is a datatype in the harmonized datatypes ontology for these boolean values already, and a code for it 'BL', but Heiner and I agreed that we would use the xsd types in the ontology, at least for the MVP, to simplify the implementation. There is a page in Confluence, at https://wiki.edmcouncil.org/pages/viewpage.action?pageId=86474903 that talks about this.

Again, that's sounds fine, but my point was not about having a new datatype - I suggested adding a new property type, i.e., a subtype of owl:DatatypeProperty.

[ElisaKendall]

@mereolog So you are saying, add a new data property called something like 'isTrueOrFalse', and then use that instead of the 'hasBooleanValue' property from the IDMP standard (which is required to be conformant and then say that 'hasBooleanValue' is a synonym of 'isTrueOrFalse'? I'm still not getting what you would like to see, in other words.

[mereolog]

I mean something along these lines:

<https://spec.pistoiaalliance.org/idmp/ontology/ISO/ISO11240-UnitsOfMeasurement/isSIQuantity> rdf:type ex:BooleanValueDatatypeProperty , owl:DatatypeProperty.

ex:BooleanValueDatatypeProperty rdf:type rdfs:Class ;
     rdfs:label "BooleanValueDatatypeProperty" ;
     rdfs:comment "The class of data properties with boolean values." ;
     rdfs:subClassOf owl:DatatypeProperty .

owl:DatatypeProperty type in the first line is only to fool Protege to display isSIQuantity - actually the former is redundant.

ex:BooleanValueDatatypeProperty cannot be displayed in Protege, but I think our onto-viewer can be persuaded to display it.

[ElisaKendall]

@merelog In the ISO 21090 Harmonized Datatypes ontology I've represented some of the datatypes as classes - under Aspect / Classifier / ISO21090-Datatype / ISO21090-AnyDatatype / ISO21090-Boolean ...they have a bunch of properties, in fact. That representation for boolean is complete I think. the 'has boolean value' class is used in that 'class' to link to the actual boolean value, so if we choose to use this instead of xsd:boolean in the next phase of the project, we can.