Update annnotations on gist:hasAccuracy

[rjyounes]

The skos:definition should not be limited to magnitudes. A measuring instrument or a measurement event could also have an accuracy.

Current:

gist:hasAccuracy
    a
        owl:ObjectProperty ,
        owl:FunctionalProperty
        ;
    rdfs:range gist:Magnitude ;
    skos:definition "Relates a magnitude to the accuracy of its numeric value."^^xsd:string ;
    skos:example "Temperature accurate to tenth of a degree C; length accurate to the nearest centimeter."^^xsd:string ;
    skos:prefLabel "has accuracy"^^xsd:string ;
    skos:scopeNote """A typical way to use accuracy is to have it represent 2 standard deviations of the distribution of measurement errors. With this convention, when the measurement method is well-calibrated (has an average error of zero) and its errors have a normal distribution, there is a 95% chance that the actual error in measurement, in either direction, is less than the accuracy.

Note that the unit of measure of the accuracy has to be compatible with the unit of measure of the original magnitude (e.g. something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance)."""^^xsd:string ;
    .

Proposed:

gist:hasAccuracy
    a
        owl:ObjectProperty ,
        owl:FunctionalProperty
        ;
    rdfs:range gist:Magnitude ;
        gist:domainIncludes gist:Magnitude ;
    skos:definition "Relates a resource such as a magnitude to the accuracy of its numeric value."^^xsd:string ;
    skos:example "Temperature accurate to tenth of a degree C; length accurate to the nearest centimeter."^^xsd:string ;
    skos:prefLabel "has accuracy"^^xsd:string ;
        skos:scopeNote "Could also apply to measurement events (activities) or measuring instruments." ;
    skos:scopeNote """A typical way to use accuracy is to have it represent 2 standard deviations of the distribution of measurement errors. With this convention, when the measurement method is well-calibrated (has an average error of zero) and its errors have a normal distribution, there is a 95% chance that the actual error in measurement, in either direction, is less than the accuracy.

Note that the unit of measure of the accuracy has to be compatible with the unit of measure of the original magnitude (e.g. something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance)."""^^xsd:string ;
    .

[MichaelSullivanArchitect]

[like] Michael J. Sullivan reacted to your message:

---

From: Rebecca Younes @.> Sent: Tuesday, August 13, 2024 8:00:26 PM To: semanticarts/gist @.> Cc: Subscribed @.***> Subject: [External] : [semanticarts/gist] Update annnotations on gist:hasAccuracy (Issue #1146)

The skos:definition should not be limited to magnitudes. A measuring instrument or a measurement event could also have an accuracy.

Current:

gist:hasAccuracy a owl:ObjectProperty , owl:FunctionalProperty ; rdfs:range gist:Magnitude ; skos:definition "Relates a magnitude to the accuracy of its numeric value."^^xsd:string ; skos:example "Temperature accurate to tenth of a degree C; length accurate to the nearest centimeter."^^xsd:string ; skos:prefLabel "has accuracy"^^xsd:string ; skos:scopeNote """A typical way to use accuracy is to have it represent 2 standard deviations of the distribution of measurement errors. With this convention, when the measurement method is well-calibrated (has an average error of zero) and its errors have a normal distribution, there is a 95% chance that the actual error in measurement, in either direction, is less than the accuracy.

Note that the unit of measure of the accuracy has to be compatible with the unit of measure of the original magnitude (e.g. something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance)."""^^xsd:string ; .

Proposed:

gist:hasAccuracy a owl:ObjectProperty , owl:FunctionalProperty ; rdfs:range gist:Magnitude ; gist:domainIncludes gist:Magnitude ; skos:definition "Relates a resource such as a magnitude to the accuracy of its numeric value."^^xsd:string ; skos:example "Temperature accurate to tenth of a degree C; length accurate to the nearest centimeter."^^xsd:string ; skos:prefLabel "has accuracy"^^xsd:string ; skos:scopeNote "Could also apply to measurement events (activities) or measuring instruments." ; skos:scopeNote """A typical way to use accuracy is to have it represent 2 standard deviations of the distribution of measurement errors. With this convention, when the measurement method is well-calibrated (has an average error of zero) and its errors have a normal distribution, there is a 95% chance that the actual error in measurement, in either direction, is less than the accuracy.

Note that the unit of measure of the accuracy has to be compatible with the unit of measure of the original magnitude (e.g. something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance)."""^^xsd:string ; .

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/semanticarts/gist/issues/1146__;!!ACWV5N9M2RV99hQ!MzfRcdYrBbHYj2aJRMi19xfDp5vT03x1GTUqiMKIipLh1w6C-M2F3oDLGp8BztU3_bXSKzPLqG4b15zz9J1fO1OtJr1KdeI$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AOMYTHZD3FOHHIW6SEFIEODZRJQVVAVCNFSM6AAAAABMO6QQZKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DIMJRHE3DKOA__;!!ACWV5N9M2RV99hQ!MzfRcdYrBbHYj2aJRMi19xfDp5vT03x1GTUqiMKIipLh1w6C-M2F3oDLGp8BztU3_bXSKzPLqG4b15zz9J1fO1OtekniO24$. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[rjyounes]

Fix with #1149.

[MichaelSullivanArchitect]

Is there an example of an instance of an "accuracy" magnitude in the style of "plus or minus 5%" ?

[uscholdm]

Is there an example of an instance of an "accuracy" magnitude in the style of "plus or minus 5%" ?

No, but that is an interesting idea. We do have something similar in the operators ontology. See the properties:

• hasTargetValue
• hasPercentVariation
• hasAbsoluteVariation

[MichaelSullivanArchitect]

Regarding "This is an abstract superproperty, not intended for use in triples" I suppose this means that we should create our own subproperty based on this – correct? And in the use-case of a precision of "plus or minus 5%" what exactly would that subproperty reference (i.e. its rdfs:range)? Some sort of Magnitude? Blank node? Or something else?

M

---

From: Michael Uschold @.> Sent: Wednesday, September 11, 2024 3:25 PM To: semanticarts/gist @.> Cc: Michael J. Sullivan @.>; Comment @.> Subject: [External] : Re: [semanticarts/gist] Update annnotations on gist:hasAccuracy (Issue #1146)

Is there an example of an instance of an "accuracy" magnitude in the style of "plus or minus 5%" ?

No, but that is an interesting idea. We do have something similar in the operators ontologyhttps://urldefense.com/v3/__https://github.com/semanticarts/operators-ontology__;!!ACWV5N9M2RV99hQ!I7OtTR8UEY0jAfKogMvJH8dhOblmMymd_VVCs20gWzqSy7nDqsvTlRUSfLoUVj14m74tpGTfQir50jjEXLHLChcvD0dDzhU$. See the properties:

• hasTargetValue
• hasPercentVariation
• hasAbsoluteVariation

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/semanticarts/gist/issues/1146*issuecomment-2344532877__;Iw!!ACWV5N9M2RV99hQ!I7OtTR8UEY0jAfKogMvJH8dhOblmMymd_VVCs20gWzqSy7nDqsvTlRUSfLoUVj14m74tpGTfQir50jjEXLHLChcvSgN6mdM$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AOMYTH3O6MCJWLM7IM5W6G3ZWCKI7AVCNFSM6AAAAABMO6QQZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBUGUZTEOBXG4__;!!ACWV5N9M2RV99hQ!I7OtTR8UEY0jAfKogMvJH8dhOblmMymd_VVCs20gWzqSy7nDqsvTlRUSfLoUVj14m74tpGTfQir50jjEXLHLChcv-yPYTXY$. You are receiving this because you commented.

[uscholdm]

The second scopeNote is far more technical and detailed than is the norm for gist. I read it several times, I have a math background, and I still can't work out exactly what it means or how to make use of it. If this information is likely to be useful to gist users, I propose to use rdf:seeAlso to a link that has a good explanation. In the meantime, here is my proposal:

gist:hasAccuracy
    a
        owl:ObjectProperty ,
        owl:FunctionalProperty
        ;
    rdfs:range gist:Magnitude ;
        gist:domainIncludes gist:Magnitude ;
    skos:definition "Relates a resource such as a magnitude to the accuracy of its numeric value."^^xsd:string ;
    skos:example "Temperature accurate to tenth of a degree C; length accurate to the nearest centimeter."^^xsd:string ;
    skos:prefLabel "has accuracy"^^xsd:string ;
        skos:scopeNote "Could also apply to measurement events (activities) or measuring instruments." ;
    skos:scopeNote "Note that the unit of measure of the accuracy has to be compatible with the unit of measure of the original magnitude (e.g. something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance)."^^xsd:string ;
    .

[rjyounes]

I agree that the original is too technical. Do you think "compatible" needs to be elaborated on or is it self-explanatory enough?

[uscholdm]

something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance

It already is explained, to wit:

"something measured in meters could have a accuracy in terms of millimeters or any other unit that measures distance"