Difference between revisions of "User:WikiSysop/Information Model"
| Line 20: | Line 20: | ||
<hr style='clear:both;width:80%; height:8px; margin-top:2em; background-color:teal;'/> | <hr style='clear:both;width:80%; height:8px; margin-top:2em; background-color:teal;'/> | ||
==Metaclass Model== | |||
{{Hierarchy|Start|0|rdfs:Class}} | |||
{{Hierarchy||1|nlp:Noun}} | |||
{{Hierarchy||1|nlp:Verb}} | |||
{{Hierarchy||1|nlp:Adjective}} | |||
{{Hierarchy||1|nlp:Participle}} | |||
{{Hierarchy||1|nlp:Gerund}} | |||
{{Hierarchy|End|0|rdfs:Class}} | |||
==Class Hierarchy== | ==Class Hierarchy== | ||
{{Hierarchy|Start|0|Context | {{Hierarchy|Start|0|Context}} | ||
{{Hierarchy|Start|1|Process skos:Concept}} | {{Hierarchy|Start|1|Process skos:Concept}} | ||
{{Hierarchy|Start|2|Function}} | {{Hierarchy|Start|2|Function}} | ||
{{Hierarchy||3|Algorithm}} | {{Hierarchy||3|Algorithm}} | ||
| Line 35: | Line 42: | ||
{{Hierarchy|End|2|Method}} | {{Hierarchy|End|2|Method}} | ||
{{Hierarchy||2|Recipe}} | {{Hierarchy||2|Recipe}} | ||
{{Hierarchy||2|Machine}} | |||
{{Hierarchy|End|1|Process}} | {{Hierarchy|End|1|Process}} | ||
{{Hierarchy|Start|1|Sink skos:Concept}} | {{Hierarchy|Start|1|Sink skos:Concept}} | ||
| Line 54: | Line 62: | ||
{{Hierarchy|Start|3|Address}} | {{Hierarchy|Start|3|Address}} | ||
{{Hierarchy||4|Email address}} | {{Hierarchy||4|Email address}} | ||
{{Hierarchy||4|Legal address}} | {{Hierarchy|Start|4|Postal address}} | ||
{{Hierarchy||4|Postal address}} | {{Hierarchy||5|Legal address}} | ||
{{Hierarchy||4| | {{Hierarchy|End|4|Postal address}} | ||
{{Hierarchy|Start|4|Internet address}} | |||
{{Hierarchy||5| | {{Hierarchy||5|WWW address}} | ||
{{Hierarchy||5| | {{Hierarchy||5|WWW domain}} | ||
{{Hierarchy|End|4|Node}} | {{Hierarchy||5|WWW top level domain}} | ||
{{Hierarchy|End|4|Node address}} | |||
{{Hierarchy|End|3|Address}} | {{Hierarchy|End|3|Address}} | ||
{{Hierarchy||3|Airspace}} | {{Hierarchy||3|Airspace}} | ||
| Line 71: | Line 80: | ||
{{Hierarchy||4|Roadway}} | {{Hierarchy||4|Roadway}} | ||
{{Hierarchy|End|3|Path}} | {{Hierarchy|End|3|Path}} | ||
{{Hierarchy|Start|3|Spot}} | |||
{{Hierarchy||4|Intersection}} | |||
{{Hierarchy||4|Junction}} | |||
{{Hierarchy|End|3|Spot}} | |||
{{Hierarchy|Start|3|Structure}} | |||
{{Hierarchy||4|Building}} | |||
{{Hierarchy|End|3|Structure}} | |||
{{Hierarchy|Start|3|Waterbody}} | {{Hierarchy|Start|3|Waterbody}} | ||
{{Hierarchy||4|Ocean}} | {{Hierarchy||4|Ocean}} | ||
| Line 164: | Line 180: | ||
{{Hierarchy|End|4|nlp:Text}} | {{Hierarchy|End|4|nlp:Text}} | ||
{{Hierarchy||4|nlp:Video}} | {{Hierarchy||4|nlp:Video}} | ||
{{Hierarchy|End | {{Hierarchy|End|3|rdf:Property}} | ||
{{Hierarchy||3|Reason}} | {{Hierarchy||3|Reason}} | ||
{{Hierarchy||3|Risk}} | {{Hierarchy||3|Risk}} | ||
| Line 176: | Line 192: | ||
{{Hierarchy||3|Policy}} | {{Hierarchy||3|Policy}} | ||
{{Hierarchy||3|Procedure}} | {{Hierarchy||3|Procedure}} | ||
{{Hierarchy||3|Task}} | |||
{{Hierarchy||3|Use Case}} | {{Hierarchy||3|Use Case}} | ||
{{Hierarchy|End|2|Statement}} | {{Hierarchy|End|2|Statement}} | ||
Revision as of 08:35, 30 November 2022
The Best Practices Wiki Information Model
The Best Practices Wiki Information Model is fundamental to identify (a) semantic tags to markup Best Practices essays (b) semantic classes for Practice, Policy, Procedure and Process models, of prime interest (c) classes for Act, Action, Activity and Task that are the detailed enumerated steps for a "method" that achieves a particularly useful objective.
Semantic Models in Context
mw:Extension:SemanticTasks: provides email task notifications and reminders. This application concerns assignment of People to tasks, not a focus here though BestPracticesWiki.net can provide the task descriptions to such an application.
 | Amina Annane, Nathalie Aussenac-Gilles, Mouna Kamel. BBO: BPMN 2.0 Based Ontology for Business Process Representation. 20th European Conference on Knowledge Management (ECKM 2019), Sep 2019, Lisbonne, Portugal.  |
Glossary of Key Terms
| Act | a thing done; a deed. |
| Action | the (fact or) process of doing something, typically to achieve an aim. |
| Activity | the condition in which things are happening or being done. A thing that a person or group does or has done. |
| Actor | anyone or anything that performs a behavior (who is using the system). |
| Category:Agent/Intro | |
| Category:Belief/Intro | |
| Category:Benefit/Intro | |
| Context | the circumstances that form the setting for an event, statement, or idea, and in terms of which it can be fully understood and assessed. |
| Essay | a short piece of writing on a particular subject. |
| Event | a thing that happens, especially one of importance. |
| Formula | a method, statement, or procedure for achieving something, especially reconciling different aims or positions.> |
| Category:Heading/Intro | |
| Category:Inflow/Intro | |
| Category:Institution/Intro | |
| Method | a particular form of procedure for accomplishing or approaching something, especially a systematic or established one. |
| Category:Operation/Intro | |
| Category:Outflow/Intro | |
| Category:Parameter/Intro | |
| Category:Place/Intro | |
| Category:Person/Intro | |
| Practice | the customary, habitual, or expected procedure or way of doing of something. |
| Policy | a course or principle of action adopted or proposed by a government, party, business, or individual. |
| Category:Procedure/Intro | |
| Process | a series of actions or steps taken in order to achieve a particular end. |
| Category:Reason/Intro | |
| Recipe | a set of instructions (such as) for preparing a particular dish, including a list of ingredients required. |
| Category:Result/Intro | |
| Category:Risk/Intro | |
| Category:Role/Intro | |
| Category:Sink/Intro | |
| Category:State/Intro | |
| Category:Statement/Intro | |
| Task | a piece of work to be done or undertaken. |
| Category:Trigger/Intro | |
| Use Case | a written description of how users will perform tasks. It outlines, from a user's point of view, a system's behavior as it responds to a request. Each use case is represented as a sequence of simple steps, beginning with a user's goal and ending when that goal is fulfilled. www.usability.gov |
References
- [https:\\kissflow.com/workflow/bpm/business-process/ The Extensive Guide to Business Processes]
- ERP Readiness Series: The Four Core Processes Every Business Should Document