Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add goal description and written name #729

Merged
merged 2 commits into from
Apr 16, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ Here is a template for new release sections
- thorium and plutonium (#708)
- has information input / output (#716)
- has typical computation time / hardware (#723)
- goal description (#729)

### Changed
- has physical output, has constraint (#716)
Expand Down
12 changes: 12 additions & 0 deletions src/ontology/edits/oeo-model.omn
Original file line number Diff line number Diff line change
Expand Up @@ -1398,6 +1398,18 @@ pull request: https://github.com/OpenEnergyPlatform/ontology/pull/610",
OEO_00000119


Class: OEO_00140099

Annotations:
<http://purl.obolibrary.org/obo/IAO_0000115> "A goal description is an information content entity that contains statements about a desired future state of a system that a person or organisation envisions or plans, or to which it commits.",
<http://purl.obolibrary.org/obo/IAO_0000233> "issue: https://github.com/OpenEnergyPlatform/ontology/issues/28
pull request: https://github.com/OpenEnergyPlatform/ontology/pull/729",
rdfs:label "goal description"@en

SubClassOf:
<http://purl.obolibrary.org/obo/IAO_0000030>


Individual: OEO_00000049

Annotations:
Expand Down
33 changes: 33 additions & 0 deletions src/ontology/imports/iao-module.owl
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,21 @@ Request that IAO either clarify these or change definitions not to use them</rdf
</owl:Class>


<!-- http://purl.obolibrary.org/obo/IAO_0000300 -->

<owl:Class rdf:about="http://purl.obolibrary.org/obo/IAO_0000300">
<rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/IAO_0000030"/>
<obo:IAO_0000111 xml:lang="en">textual entity</obo:IAO_0000111>
<obo:IAO_0000112 xml:lang="en">Words, sentences, paragraphs, and the written (non-figure) parts of publications are all textual entities</obo:IAO_0000112>
<obo:IAO_0000114 rdf:resource="http://purl.obolibrary.org/obo/IAO_0000123"/>
<obo:IAO_0000115 xml:lang="en">A textual entity is a part of a manifestation (FRBR sense), a generically dependent continuant whose concretizations are patterns of glyphs intended to be interpreted as words, formulas, etc.</obo:IAO_0000115>
<obo:IAO_0000116 xml:lang="en">AR, (IAO call 2009-09-01): a document as a whole is not typically a textual entity, because it has pictures in it - rather there are parts of it that are textual entities. Examples: The title, paragraph 2 sentence 7, etc.</obo:IAO_0000116>
<obo:IAO_0000116 xml:lang="en">MC, 2009-09-14 (following IAO call 2009-09-01): textual entities live at the FRBR (http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records) manifestation level. Everything is significant: line break, pdf and html versions of same document are different textual entities.</obo:IAO_0000116>
<obo:IAO_0000117 xml:lang="en">PERSON: Lawrence Hunter</obo:IAO_0000117>
<obo:IAO_0000118 xml:lang="en">text</obo:IAO_0000118>
<rdfs:label xml:lang="en">textual entity</rdfs:label>
</owl:Class>



<!-- http://purl.obolibrary.org/obo/IAO_0000310 -->
Expand Down Expand Up @@ -225,6 +240,24 @@ Request that IAO either clarify these or change definitions not to use them</rdf
<obo:IAO_0000119 xml:lang="en">adapted from discussion on OBI list (Matthew Pocock, Christian Cocos, Alan Ruttenberg)</obo:IAO_0000119>
<rdfs:label xml:lang="en">algorithm</rdfs:label>
</owl:Class>



<!-- http://purl.obolibrary.org/obo/IAO_0000590 -->

<owl:Class rdf:about="http://purl.obolibrary.org/obo/IAO_0000590">
<rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/IAO_0000300"/>
<obo:IAO_0000111 xml:lang="en">written name</obo:IAO_0000111>
<obo:IAO_0000112 xml:lang="en">&quot;Bill Clinton&quot;</obo:IAO_0000112>
<obo:IAO_0000112 xml:lang="en">&quot;The Eiffel Tower&quot;</obo:IAO_0000112>
<obo:IAO_0000112 xml:lang="en">&quot;United States of America&quot;</obo:IAO_0000112>
<obo:IAO_0000114 rdf:resource="http://purl.obolibrary.org/obo/IAO_0000125"/>
<obo:IAO_0000115 xml:lang="en">A textual entity that denotes a particular in reality.</obo:IAO_0000115>
<obo:IAO_0000117 xml:lang="en">PERSON: Bill Hogan</obo:IAO_0000117>
<obo:IAO_0000119 xml:lang="en">https://github.com/information-artifact-ontology/IAO/issues/114</obo:IAO_0000119>
<obo:IAO_0000232 xml:lang="en">The qualifier &quot;written&quot; is to set it apart from spoken names. Also, note the restrictions to particulars. We are not naming universals. We could however, be naming, attributive collections which are particulars, so &quot;All people located in the boundaries of the city of Little Rock, AR on June 18, 2011 at 9:50a CDT&quot; would be a name.</obo:IAO_0000232>
<rdfs:label xml:lang="en">written name</rdfs:label>
</owl:Class>

</rdf:RDF>

Expand Down