id: http://purl.org/mira-science/mira#
name: mira
prefixes:
  rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
  rdfs: http://www.w3.org/2000/01/rdf-schema#
  owl: http://www.w3.org/2002/07/owl#
  mira: http://purl.org/mira-science/mira#

default_prefix: mira
# language: en
default_range: string
imports:
  - prov
  - schemaorg
  - discoursegraphs_base

classes:
  Argument:
    class_uri: mira:Argument
    mixin: true
    description: A node that can support or oppose another node
    slots:
      - supports
      - opposes

  Question:
    class_uri: mira:Question
    mixins:
      - NodeSchema
    description: Scientific unknowns that we want to make known, and are addressable by the systematic application of research methods

  Claim:
    class_uri: mira:Claim
    mixins:
      - NodeSchema
    description: Atomic, generalized assertions about the world that (propose to) answer research questions
    slots:
      - addresses

  Evidence:
    class_uri: mira:Evidence
    mixins:
      - NodeSchema
    description: A specific empirical observation from a particular application of a research method
    slots:
      - grounds
      - observationStatement
      - observationOriginActivity
      - observationBase
      - sourceDocument

  Study:
    class_uri: mira:Study
    description: An activity — an experiment or analysis — that produces evidence.
    mixins:
      - NodeSchema
      - Activity
    slots:
      - request_for
      - follows
      - grounds

  Request:
    class_uri: mira:Request
    description: A unit of work the community can pick up — issue-tracker-shaped.
    mixins:
      - NodeSchema
    slots:
      - request_for
      - request_target

  Protocol:
    class_uri: mira:Protocol
    description: The method or experimental approach a Study follows to generate the evidence.
    mixins:
      - NodeSchema
      - Activity

  SourceDocument:
    class_uri: mira:SourceDocument
    is_a: CreativeWork
    mixins:
      - NodeSchema
      # [rdf:type owl:Restriction ; owl:onProperty describesActivity ; owl:minCardinality 1].
    title: Source document
    description: Some research source document that reports/generates evidence, like a book, conference paper, or journal article
    slots:
      - describesActivity

slots:
  follows:
    domain: Study
    range: Protocol
    multivalued: true
  grounds:
    domain: Study
    range: Evidence
    inverse: is_grounded_in
    multivalued: true
  is_grounded_in:
    domain: Evidence
    range: Study
  request_for:
    domain: Request
    range: Study
    multivalued: true
  request_target:
    domain: Request
    range: Claim
    multivalued: true
  describesActivity:
    slot_uri: mira:describesActivity
    title: Describes activity
    subproperty_of: subject
    domain: CreativeWork
    range: Activity

  observationStatement:
    slot_uri: mira:observationStatement
    subproperty_of: RelationDef
    title: Observation statement
    domain: Evidence
    range: Claim

  observationOriginActivity:
    slot_uri: mira:observationOriginActivity
    subproperty_of: RelationDef
    title: Observation origin process
    description: An experiment or study at the origin of the data on which the observation is based
    domain: Evidence
    range: Activity
  # I would like to add:
  #  owl:propertyChainAxiom (sourceDocument describesActivity).
  # But it is not strictly accurate; the document may describe many activities
  # HOWEVER it is true that, if sourceDocument is defined, the observationOriginActivity should should follow one of these chains.

  observationBase:
    slot_uri: mira:observationBase
    title: Observation base
    description: The data on which the observation is based
    range: Entity
    # That range is very, very provisional. could also involve schema:DigitalDocument , schema:Dataset
    domain: Evidence
    mixins:
      - RelationDef
  # The Entity should be prov:wasGeneratedBy the Activity that is either the Source, or one subject of the Source.
  # I would like to add:
  #  owl:propertyChainAxiom (observationOriginActivity prov:generated).
  # But it is not strictly accurate; the activity may generate many entities.
  # HOWEVER it is true that the observationBase should follow one of these chains, which should exist.

  sourceDocument:
    slot_uri: mira:sourceDocument
    subproperty_of: RelationDef
    title: Source document
    description: A document that described the activity which led to the data on which the observation is based
    domain: Evidence
    range: SourceDocument

  opposes:
    slot_uri: mira:opposes
    subproperty_of: RelationDef
    title: Opposes
    range: Claim
    # Or Arguable?
    domain: Argument
    multivalued: true
  opposedBy:
    slot_uri: mira:opposedBy
    subproperty_of: RelationDef
    title: Opposed by
    inverse: opposes
    domain: Claim
    # Or Arguable?
    range: Argument
    multivalued: true
  supports:
    slot_uri: mira:supports
    subproperty_of: RelationDef
    title: Supports
    range: Claim
    # Or Arguable?
    domain: Argument
    multivalued: true
  supportedBy:
    slot_uri: mira:supportedBy
    subproperty_of: RelationDef
    title: Supported by
    inverse: supports
    domain: Claim
    # Or Arguable?
    range: Argument
    multivalued: true

  addresses:
    slot_uri: mira:addresses
    subproperty_of: RelationDef
    title: Addresses
    range: Question
    domain: Claim
    multivalued: true

  addressedBy:
    slot_uri: mira:addressedBy
    subproperty_of: RelationDef
    title: Addressed by
    inverse: addresses
    range: Claim
    domain: Question
    multivalued: true