{"id":16899341,"url":"https://github.com/nicholascar/do-ont","last_synced_at":"2026-01-03T17:49:11.928Z","repository":{"id":88145631,"uuid":"81558284","full_name":"nicholascar/do-ont","owner":"nicholascar","description":"A Web Ontology Language (OWL) ontology providing means for describing decisions and decision making","archived":false,"fork":false,"pushed_at":"2018-04-07T03:27:33.000Z","size":1628,"stargazers_count":2,"open_issues_count":0,"forks_count":2,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-01-25T12:27:02.230Z","etag":null,"topics":["decision-modelling","owl","w3c"],"latest_commit_sha":null,"homepage":"https://promsns.org/def/do ","language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc-by-4.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nicholascar.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-02-10T11:17:26.000Z","updated_at":"2024-07-18T03:43:17.000Z","dependencies_parsed_at":"2023-03-06T07:31:07.129Z","dependency_job_id":null,"html_url":"https://github.com/nicholascar/do-ont","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicholascar%2Fdo-ont","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicholascar%2Fdo-ont/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicholascar%2Fdo-ont/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicholascar%2Fdo-ont/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nicholascar","download_url":"https://codeload.github.com/nicholascar/do-ont/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":244609597,"owners_count":20480811,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["decision-modelling","owl","w3c"],"created_at":"2024-10-13T17:48:24.883Z","updated_at":"2026-01-03T17:49:11.900Z","avatar_url":"https://github.com/nicholascar.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Decision-O\nThe Decision ontology\n\n## Introduction\nThe Decision Ontology (DO) provides basic means for describing decision and decisionmaking. It is formalized in the Web \nOntology Language (OWL) and can be accessed here. The current DO prototype is intended to be extended with additional \nfeatures as the work on the decision format progresses.\n\n## Background\nThis DO was published as an output of the [W3C Decisions and Decision-Making Incubator Group](https://www.w3.org/2005/Incubator/decision/) \nin 2012 as the [Sample Decision Ontology ](https://www.w3.org/2005/Incubator/decision/XGR-decision-20120417/Sample_Decision_Ontology.html). \nSince then the DO has been re-published here in order to position it for continued development. \n\nThis version of the DO published by the Incubator group will be referred to as the Sample DO and this version, \npublished here, referred to as the DO, v1.0.\n \nThe differences between the Sample DO and DO v1.0 ontologies themselves are minimal: only updates to a few OWL \nproperties with broken syntax where made. Additional comments and change notes have also been added to the to DO v1.0 \nontology document. DO v1.0 also includes all of the documentation from the Sample DO's original web pages and PDF \ndocuments given on a now-defunct CodeProject website and minor documentation updates have been included: formatting, \ngrammar and spelling, no substantial updates.\n\nDO v1.0 has also, for the first time, been rendered into HTML for browsing. See next section.\n\n## Ontology document\nTurtle format: [decision.ttl](decision.ttl)  \nRDF XML format: [decision.owl](decision.owl)  \nHTML (using a renderer): [decision.html](http://htmlpreview.github.io/?https://github.com/nicholascar/decision-o/blob/master/decision.html)\n* to see the HTML document source click here: [HTML source](decision.html).\n\n## Use\n### What it can be used for?\nSome of the questions that can be answered using DO:\n* What problem/question initiated the decision-making process? \n* What options are being considered? \n* What criteria are being used for respective options? \n* What requirements, recommendation or other possible norms are associated with proposed criteria? \n* What is involved in choosing the respective options? \n* What is the result of a decision-making process? \n* What is affected by a given norm/requirement? \n* What satisfies a criterion? \n* What does not satisfy a criterion? \n* What kind of exceptions are defined? \n* What options should be/must not be considered? \n* What are the recommended criteria? \n* What are the required criteria?\n\n### Usage scenarios\nIn general, there are two main use scenarios for DO:\n* archiving current or historical decision-making processes and their outputs (data-driven use)\n* outlining decision-making scenarios (patterns, templates) in order to provide guidelines for the decision-makers \n (normative use)\n \nCombining these two approaches would enable confronting the normative descriptions with actual decision-making data and \nthus giving sophisticated means for analyzing archived decisions which could be particularly useful for validation \npurposes.\n\n##### Data-driven use\nRecording facts by using OWL individuals. DO provides a conceptual framework and semantic foundation for analyzing \ndecision-making data. The OWL file can be filled with data that can be used in many ways.\n\n##### Normative use\nModeling decision-making patterns by defining OWL classes containing an outline of a generic decision. This could be \nuseful for representing knowledge derived from some legal regulations, requirements, industry standards or obtained \nfrom domain experts. What can be achieved here is a description of the domain decisions enabling new ways of sharing, \nunderstanding, reusing this knowledge (for example by users of common standards, clients seeking information etc.).\n\n#### Decision-making process\nA complex process that starts with a question and may result in indication of a an answer being solution to the initial problem. It is important to note that a decision-making is something substantially different than decision, which is an output of the process of deciding. Usually it can be represented by the following pattern:\n\n1. Decision-making starts with a question.\n2. The decider gathers and analyzes some information\n3. The decider evaluates possible options.\n4. One of the options may get recognized as the right/appropriate/best possible solution\nto the initial question/problem or the decider may choose to restrain from choice. What\njustifies this act could be an objective evaluation of clearly defined criteria but also an\nintuition, emotion or other subjective factor.\n\nIn most cases stages 2-3 consist of many (concurrent or sequential) actions, events, processes related to information \ngathering, processing, verifying etc. In some cases a decision-making can be viewed as a complex process involving many \n“sub-decisions” preceding the recognition of the initial problem solution. In our current work we have focused on the \nbasic elements of the above pattern (the question, gathering information, considering options, choosing solution). It \nshould be considered to what extent the DO should support the modeling of correlated issues such as: information verification and retrieval etc.\n\n#### Allowing different criteria for identity (or continuity) of the decision-making\nSometimes it may be hard to tell when one decision-making ends and the other begins. Even in the mentioned example: is \nit a single decision-making process or two distinct ones connected with each other by the same issue they both concern? \nThe case could become even more complicated when dealing with subdecisions and decision-processes with changing \nparticipants. It seems appropriate to leave that issue open enabling the core decision ontology to be extended with \nmodules containing various solutions of that particular problem. \n\n#### Decision as an outcome of decision-making process\nThere is a fundamental ontological difference between the process of deciding and its outcome - a decision. Moreover, \nallowing more elastic boundaries of decision-making (see above) can result in single decision-making having more than \none decision as its outcome.\n\n#### Allowing incomplete decision-making stages\nIn some cases it may be useful to record a decision-making stage even if it doesn’t have any decision as its outcome. \nFor example a patient may be ordered some further tests which may last a couple of days in which some other crucial \nparameters of decision-making can change resulting in a new stage of the deciding process (the newly recognized facts \nmay encourage to continue modelling with a new stage of decision-making).\n\n#### Representing temporal context\nThis is a general methodological issue, that still implies many discussions. Some of these discussion involve well-\nknown ontology experts unable to find a reasonable consensus. The main problem is: how to represent the mutable \nentities or the change of their properties in an ontology? What I did in my example is using OWL individuals to \nrepresent the same person in different stages of the decision-making process. What would be needed in a real-life \napplication is to add some property which could allow the unambiguous reference to a person (for example insurance \nnumber). This is necessary because during decision-making one would often ascribe different or even contradict \nattributes at different stages of the process. Additional benefit: using different instances to provide “snapshot” view \nof reality allows developing fine-grained view of the reality - consider an example from my scenario: the throat \ninfection diagnosed at t1 is represented by different OWL individual than the same kind of infection diagnosed at t2 \n(after the allergic reaction), which illustrates that the medical disorder has probably undergone some change and may \nrequire a different treatment. This approach is one of the possible choices and the users of DO will have to decide \nwhether or not it satisfies their needs.\n\n#### Scalability issues\nThe decision ontology should provide a foundation for modelling decision-making on different granularity level. Ideally,\nthe decision ontology would consist of basic decision ontology and a set of modular extensions enabling more detailed \nmodelling for more advanced use scenarios. When possible the core classes should be general enough to enable using them \nin different ontological and methodological contexts (for example we should not make assumptions about the definition of\na “process” because existing ontologies use different definitions of a process). So in order to enable scalability and \nwide adoption we should try to avoid or at least minimize making ontological assumptions about concepts originated from \nother domains. It seems that the successful adoption of decision ontology will probably significantly rely on the \ncapability to be used as basis for community-based extensions.\n\n#### Future work\n1. develop extensions of the core DO for modeling of:  \n    a. information gathering, processing and verification  \n    b. decision metrics  \n    c. decision-making criteria\n2. implementing a use case\n3. develop detailed documentation.\n\n\n## How-to\n#### How do I describe a decision making event?\n* Add a subclass of **Decision_making** class.\n* Consider adding the question representing the problem initiating the given decision-making process. Use **is_initiated_by** property to indicate a subclass (or member) of the **Question** class.\n* Add options by using **is_consideration_of** property to indicate a subclass (or member) of **Option** class. See below for a details on describing options and their associated criteria.\n* Add additional questions that have to be answered during the decision-making process. Use **initiates** property to indicate a subclass (or member) of the **Question** class.\n* Add the outcome of the given decision-making process (this step can be omitted when describing decision-making patterns on TBox level). Use **has_result** property to indicate decisions that may result from considered options of a given decision-making process or to indicate a member of a **Decision** class in the case of describing a concrete process.\n\n#### How do I describe an Option?\n* Describe what exactly does a given option represent. Use **involves_choosing** property to indicate appropriate class or individual.\n* Add options criteria. Use **has_criterion** property to indicate appropriate requirement, recommendation or other subclass or member of **Normative_value** class.\n\n#### How do I describe option criteria?\n* Describe what given criterion applies to. Use **has_validity_for** property to indicate appropriate class or individual.\n* Describe how a criterion can be satisfied (or not satisfied). Use **is_satisfied_by** and/or **is_violated_by** to indicate appropriate class or individual.\n\n#### How do I describe a norm (requirement, recommendation, etc.) related to a decision making event?\n* Indicate what kind of decision-making does a given norm apply to. Use **has_validity_for** to indicate appropriate subclass or member of **Decision_making** class. \n* Describe how a given decision-making type should be conducted (create a decision-making pattern). Use **is_satisfied_by** and/or **is_violated_by** to indicate appropriate subclass or member of **Decision_making** class.\n\n#### How do I describe a decision?\n* Add option which represents the chosen solution. Use **indicates** property to specify a subclass or member of **Option** class \n* Indicate decision making process which a given decision is result of. Use **is_result_of** property to indicate appropriate subclass or member of **Decision_making** class.\n\n\n## Examples\n* [Bacterial throat infection](examples/03-bacterial-throat-infection.md)\n    * illustrates the normative usage scenario\n\n## References\n*Coming...*\n\nYouTube video: https://www.youtube.com/watch?v=dbpQodni7F4\n\n\n## License\nThis ontology and all other content in this repository are licensed under the [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/) (also [LICENSE](LICENSE)).\n\n\n## Authors and Contact\n**Piotr Nowara**   \nPrimary Author  \n\u003cpiotrnowara@gmail.com\u003e  \n\n**Nicholas Car**  \nGeoscience Australia  \n\u003cnicholas.car@ga.gov.au\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnicholascar%2Fdo-ont","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnicholascar%2Fdo-ont","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnicholascar%2Fdo-ont/lists"}