https://ontology.solveit-df.org/solveit/analysis/hasField
owl:ObjectProperty
Links a hypothesised record to a decoded field value. It is deliberately not solveit-observable:hasField, whose rdfs:domain is solveit-observable:SQLiteRecord: rdfs:domain is an entailment rule rather than a usage restriction, so reusing that property would infer the hypothesis to be an observed record. The hedge is carried once, by the class, which is why this property needs no 'hypothesised' prefix. Note that in SQLite a record is self-describing, so the values follow from the record header once the extent is fixed; which column each value belongs to does not, and follows instead from the table attribution.
| DOMAIN | PROPERTY | RANGE |
|---|---|---|
| solveit-analysis:HypothesisedRecord | solveit-analysis:hasField | solveit-observable:SQLiteField |
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix solveit-analysis: <https://ontology.solveit-df.org/solveit/analysis/> .
@prefix solveit-observable: <https://ontology.solveit-df.org/solveit/observable/> .
solveit-analysis:hasField a owl:ObjectProperty ;
rdfs:label "has field"@en ;
rdfs:comment "Links a hypothesised record to a decoded field value. It is deliberately not solveit-observable:hasField, whose rdfs:domain is solveit-observable:SQLiteRecord: rdfs:domain is an entailment rule rather than a usage restriction, so reusing that property would infer the hypothesis to be an observed record. The hedge is carried once, by the class, which is why this property needs no 'hypothesised' prefix. Note that in SQLite a record is self-describing, so the values follow from the record header once the extent is fixed; which column each value belongs to does not, and follows instead from the table attribution."@en ;
rdfs:domain solveit-analysis:HypothesisedRecord ;
rdfs:range solveit-observable:SQLiteField .