Class: PropertyUsedWithDatatypeValuesAndObjects

A problem in which the same property is used two two different ways, one in which the range is a literal value, the other where it is an object.

URI: semsql_obo:PropertyUsedWithDatatypeValuesAndObjects

classDiagram Problem <|-- PropertyUsedWithDatatypeValuesAndObjects PropertyUsedWithDatatypeValuesAndObjects : predicate PropertyUsedWithDatatypeValuesAndObjects : subject PropertyUsedWithDatatypeValuesAndObjects : value

Usage

SELECT * FROM property_used_with_datatype_values_and_objects;

Inheritance

  • Problem
    • PropertyUsedWithDatatypeValuesAndObjects

Slots

Name Cardinality and Range Description
subject 0..1
Node		 The subject of the statement
predicate 0..1
PropertyNode		 The predicate of the statement
value 0..1
LiteralAsStringType		 Note the range of this slot is always a string

Usages

Comments

  • in OWL, if a property is typed as object or datatype, this will constrain its use. However, annotation properties have no such constraints in OWL, but we still consider this problematic and unintentional, unless it is a truly generic predicate, such as owl:annotatedTarget or rdf:object
  • sqlview>> SELECT DISTINCT s1.predicate AS subject, s1.predicate, s1.datatype AS value FROM statements AS s1, statements AS s2 ON (s1.predicate=s2.predicate) WHERE s1.value IS NOT NULL and s2.object IS NOT NULL

Identifier and Mapping Information

Schema Source

  • from schema: https://w3id.org/semsql/obo

SQL View

This class has a SQL view definition:

sqlview>>
  SELECT
    DISTINCT
      s1.predicate AS subject,
      s1.predicate,
      s1.datatype AS value
  FROM statements AS s1, statements AS s2 ON (s1.predicate=s2.predicate)
  WHERE s1.value IS NOT NULL and s2.object IS NOT NULL

Mappings

Mapping Type Mapped Value
self ['semsql_obo:PropertyUsedWithDatatypeValuesAndObjects']
native ['semsql_obo:PropertyUsedWithDatatypeValuesAndObjects']

LinkML Specification

Direct

name: property_used_with_datatype_values_and_objects
description: A problem in which the same property is used two two different ways,
  one in which the range is a literal value, the other where it is an object.
comments:
- in OWL, if a property is typed as object or datatype, this will constrain its use.
  However, annotation properties have no such constraints in OWL, but we still consider
  this problematic and unintentional, unless it is a truly generic predicate, such
  as owl:annotatedTarget or rdf:object
- "sqlview>>\n  SELECT\n    DISTINCT\n      s1.predicate AS subject,\n      s1.predicate,\n\
  \      s1.datatype AS value\n  FROM statements AS s1, statements AS s2 ON (s1.predicate=s2.predicate)\n\
  \  WHERE s1.value IS NOT NULL and s2.object IS NOT NULL"
from_schema: https://w3id.org/semsql/obo
see_also:
- https://github.com/information-artifact-ontology/ontology-metadata/issues/67
rank: 1000
is_a: problem

Induced

name: property_used_with_datatype_values_and_objects
description: A problem in which the same property is used two two different ways,
  one in which the range is a literal value, the other where it is an object.
comments:
- in OWL, if a property is typed as object or datatype, this will constrain its use.
  However, annotation properties have no such constraints in OWL, but we still consider
  this problematic and unintentional, unless it is a truly generic predicate, such
  as owl:annotatedTarget or rdf:object
- "sqlview>>\n  SELECT\n    DISTINCT\n      s1.predicate AS subject,\n      s1.predicate,\n\
  \      s1.datatype AS value\n  FROM statements AS s1, statements AS s2 ON (s1.predicate=s2.predicate)\n\
  \  WHERE s1.value IS NOT NULL and s2.object IS NOT NULL"
from_schema: https://w3id.org/semsql/obo
see_also:
- https://github.com/information-artifact-ontology/ontology-metadata/issues/67
rank: 1000
is_a: problem
attributes:
  subject:
    name: subject
    description: The subject of the statement
    from_schema: https://w3id.org/semsql/rdf
    aliases:
    - about
    - source
    - head
    rank: 1000
    slot_uri: rdf:subject
    alias: subject
    owner: property_used_with_datatype_values_and_objects
    domain_of:
    - term_association
    - owl_complex_axiom
    - owl_subclass_of_some_values_from
    - owl_equivalent_to_intersection_member
    - statements
    - relation_graph_construct
    - edge
    - subgraph_query
    - subgraph_edge_by_ancestor
    - subgraph_edge_by_descendant
    - subgraph_edge_by_parent
    - subgraph_edge_by_child
    - subgraph_edge_by_self
    - entailed_edge
    - entailed_edge_cycle
    - transitive_edge
    - repair_action
    - problem
    range: node
  predicate:
    name: predicate
    description: The predicate of the statement
    from_schema: https://w3id.org/semsql/rdf
    aliases:
    - relationship type
    - property
    rank: 1000
    slot_uri: rdf:predicate
    alias: predicate
    owner: property_used_with_datatype_values_and_objects
    domain_of:
    - term_association
    - owl_complex_axiom
    - owl_subclass_of_some_values_from
    - statements
    - relation_graph_construct
    - edge
    - subgraph_query
    - subgraph_edge_by_ancestor
    - subgraph_edge_by_descendant
    - subgraph_edge_by_parent
    - subgraph_edge_by_child
    - subgraph_edge_by_self
    - entailed_edge
    - entailed_edge_cycle
    - transitive_edge
    - problem
    range: property_node
  value:
    name: value
    description: Note the range of this slot is always a string. Only used the triple
      represents a literal assertion
    from_schema: https://w3id.org/semsql/rdf
    close_mappings:
    - rdf:object
    rank: 1000
    slot_uri: rdf:object
    alias: value
    owner: property_used_with_datatype_values_and_objects
    domain_of:
    - statements
    - problem
    range: literal as string type