Export to GitHub

information-artifact-ontology - issue #158

Revise Report and Documenting


Posted on Mar 8, 2014 by Helpful Giraffe

During the OBI core review several concerns were raised over IAO_0000310 "document". Alan made the point that there are other ontogies that consider "document" to be in their scope. The textual definition is vague.

What OBI really needs is "report", which is the output of a "documenting" process, which is a part of an investigation. Rather than fix "document", we decided that it was easier to change the parent of "report" to ICE and clean up "report" and "documenting". See OBI Core review notes for discussion: https://docs.google.com/document/d/1J3VjL6pbMY3q6GYZqsqqs4CbgEgIxnivMXcj_qcyznc/edit?usp=sharing

  • IAO_0000088 report

    • change parent: subclassof information content entity (not document)
    • change textual definition: An information content entity assembled by an author for the purpose of providing information for an audience, and that is meant to provide an accurate account of something that happened.
    • change example of use: journal article, patent application, grant progress report, case report (not patient record)
    • change status: ready for release
  • IAO_0000572 documenting

    • change textual definition: A planned process in which input information is used to create or add to a report.
    • change axiom: has_specified_output some report
    • example of usage: Recording the current temperature in a laboratory notebook. Writing a journal article. Updating a patient record in a database. Copying the readout from an instrument into a spreadsheet.
    • change status: ready for release

Comment #1

Posted on Mar 31, 2014 by Helpful Giraffe

Discussed on OBI/IAO call 2014-03-24 (last week). Alan disagreed with the proposed change of parent for report.

Comment #2

Posted on May 5, 2014 by Helpful Giraffe

Discussed on OBI/IAO call 2014-05-05. We will not make these changes to IAO.

Status: WontFix

Labels:
Type-Term Priority-Medium