A relationship between rational agents that influences the knowledge of one or more agents in the relationship. The relationship uses at least the two roles: agent-driven-role, and informationResource. There can be only one rational agent that is 'influenced' by some information produced at a different time by the same agent.
A knowledge creator role that is also an accountable performer role.
An enactment for an e-collaboration workflow. It is the setting for at least two rational agents, both accountable.
A situation with at least two objects participating in a same event.
An enactment for an e-usage workflow. It is the setting for at least two rational agents: one accountable, the other a non-accountable knowledge creator.
An e-interaction is a case of epistemological influence that prescribes the proactive involvement of two rational agents. One rational agent can also be a team, provided that the members perform actions expected by a shared e-interaction plan. Moreover, only some of the activated rational agents adopt the goal of the e-interaction (some are non-accountable). More details are contained in the corresponding class: e-interaction-situation.
A knowledge creator role that is not an accountable performer role.
A knowledge collective is a community that is characterized by some practices of knowledge communization. In this ontology, this is formalized as being a 'collective' that is 'unified by' some 'epistemic workflow'.
An enactment for an e-interaction workflow. It is the setting for at least two rational agents: one an accountable performer, the other a non-accountable performer.
A performer role that is not accountable within the plan that uses the role.
Any relationship between rational agents that influences the knowledge of one or more agents in the relationship, according to a workflow shared by one or more or even all the agents. An epistemic workflow is both an epistemic influence and a plan, whose main goal is knowledge production. At least one 'accountable performer role' is used by all epistemic workflow.
The C-ODO library currently contains 8 native ontologies, and imports or uses several others, either for design purposes (DOLCE, cDnS, etc.), or for extending their scope (owlodm, OMV, oQual, SKOS, NeOn networked ontology model). odWorkflows.owl is the module describing kinds of methods for the ontology lifecycle: construction, maintenance, ruse, mapping, etc. Those methods are said to involve 'epistemic activities', where the agents and parties participating to the lifecycle take decisions on an ontology. C-ODO is an ontology for ontology design, to be used as a set of social requirements for NeOn methodologies and tools. The key notion is 'ontology project', which is assumed to be made up of knowledge-level ('epistemic') workflows, which on their turn contain 'argumentation structures' and 'design rationales' that motivate 'design solutions' taken from a 'choice space' generated by 'design patterns' over 'ontology elements'. Appropriate roles (e.g. 'knowledge product', 'knowledge creator') and tasks (e.g. functionalities like 'selection', 'importing', etc.) are used by project, workflow, and rationale schemas. Situation classes ('ontology project execution', 'epistemic workflow enactment', 'argumentation situation', 'design making', 'design solution') are introduced in order to reason on the actual occurrences of those schemas. Moreover, ontology objects and other information objects used during the ontology lifecycle, together with the design operations and the designer agents, are framed by those situations if they comply to the roles and tasks used by the schemas. Types of projects, workflows, argumentation, rationales, patterns, etc. are also introduced in C-ODO. The schema-situation approach is an architectural design pattern that is wholly axiomatized in the cDnS ontology (http://www.loa-cnr.it/ontologies/cDnS.owl). It allows to talk of contexts (or methods, plans, etc.) in the same domain as the actual situations (executions, observations, etc.) that exemplify those contexts. More generally, the ontology design ontology uses the following patterns: - the DnS content pattern (http://www.loa-cnr.it/ontologies/ExtendedDnS.owl) has been used throughout, and the following sub-patterns have been used: a) descriptions and concepts depend on existential axioms only when they involve 'descriptive' entities b) descriptions are constrained wrt a given situation class SC c) concepts are constrained wrt a given entity class EC d) SC are defined by requiring that some entity from EC is in their setting. - the collections pattern (http://www.loa-cnr.it/ontologies/ExtendedDnS.owl), and the following sub-patterns have been used: a) collections have any entities as members b) collections are covered or characterized by concepts c) collections are unified by descriptions that use or define those concepts. -the plans pattern (http://www.loa-cnr.it/ontologies/Plans.owl): a) plans use tasks, roles, and parameters b) plans have a main goal as a proper part c) plans are 'executed' within plan executions by agents playing roles in order to perform the tasks used by the plan d) plan executions start from certain situations ('preconditions') and result in certain situations ('postconditions'). Postconditions can be compliant or not to the expected goal.
ontology design workflows ontology
An e-collaboration is a case of epistemic workflow that prescribes the proactive involvement of all rational agents, i.e. all the involved rational agents adopt the main goal of the e-collaboration. A rational agent can also be a team, provided that the members perform actions expected by a shared e-interaction plan. More details are contained in the corresponding class: e-collaboration-situation.
A performer role that is only played by rational agents that adopt the main goal of the plan using the role.
An e-usage is an epistemic workflow that uses two additional roles: accountable performer (for agents that adopt the main goal), and non-accountable information creator (for agents that have created the information resource to be used in the workflow, without being actively involved in the knowledge creation plan). More details are contained in the corresponding class: e-usage-situation.
A situation satisfying an epistemic influence description.