Taskoriented Information Modelling (TIM) ProposalThe aim of this proposal is to standardize such a formal language using TaskorientedInformation Modelling (TIM) as a starting point. TIM has been usedfor 10 years to produce task models in various fields (machine, process andsoftware modelling). It proves easy to learn, its expressions translatestraightforwardly into natural language, and its syntax is defined by a shortset of XML-compliant rules and patterns.TIM builds on an incremental ontology, where a reduced set of categories[objects, operations and facets] generate descriptions [states, properties] andactions. These, in turn, populate the categories describing tasks (preconditions,input, output and side-effects). Tasks are organized in a hierarchy.Tasks exhibit types (standard, alternative, critical, conditional, optional,cyclic, generic), which may constrain their position in the hierarchy (criticaltasks are always first-level tasks, alternative and optional ones are alwayssub-tasks), or their structure (generic tasks are always split into alternativeor optional sub-tasks), or their content (only last-level tasks are enhancedwith a list of actions, termed "procedure"). Conditional tasks host preconditions,critical tasks a "trigger", cyclic tasks a cycle-stop condition. Sometype-combinations are allowed (conditional + optional, for example), whileother ones are not (for instance, conditional + critical).The formal language expressing this ontology is a predicate-argument typesyntax. Every entity in the model has a numerical identifier allowing reuse. Areduced set of symbols (O: object, S: state, P: property, A: action, T: task)combined with the relative position of an element in the model (which is aframe-based structure), define which descriptions act as the Input, the Output,the Side-effect, etc.OASIS Task-oriented Information Modelling (TIM) Technical CommitteeTIMTC_4a933abc-946d-11e1-b3fe-79e3222d735fThe TC will develop a formal language standard for task-oriented modelingusing TIM as a starting point along with any other inputs provided. The TCwill review and comment on the actual state of the categories, syntax andscope of the TIM meta-model. The TC will examine the completeness of thelanguage with regard to the situations intended to be specified, as well as thewell-formedness of the generic expressions allowed by the rules and thepatterns they implement. By "situations", we here mean working contextswhere prescribed goals should be obtained by ways of a deterministicworkflow, which is typical when using devices or software, or when designingthe thread of processes.Daniel GueyssetProposer of the TC, dgueysset@proximit.fr (Proximit)Guillaume TessierProposer of the TC, gtessier@timgroup.fr (TimGroup)Tanguy WettengelTC Convener, tanguy@teamtim.com (University of Limoges)OASISKnowledge Management PractitionersKnowledge Management practitioners engaged in work-analysis and designSoftware ArchitectsSoftware architects defining functional specifications and interfaces.Hardware DesignersHardware designers defining functional specifications and interfaces.Process AnalystsProcess Analysts DesignersTask Analysts Anyone performing what is currently termed “Task analysis” or “Taskmodelling”.Task ModellersErgonomistsTools adapt to human agents rather than the agents adapting to tools._4a933cf6-946d-11e1-b3fe-79e3222d735fTo standardize a formal language using Taskoriented Information Modelling (TIM)._4a933de6-946d-11e1-b3fe-79e3222d735fDeliverablesIssue several deliverables in both the Standards and Non-Standards Tracks._4a933e9a-946d-11e1-b3fe-79e3222d735fThe TIM TC plans to issue several deliverables in both the Standards and Non-Standards Tracks.Standards Track Deliverables_4a933f58-946d-11e1-b3fe-79e3222d735f1OntologyDeliver an ontology of work-analysis categories._4a934016-946d-11e1-b3fe-79e3222d735f1.1An ontology of work-analysis categories, both in graphical and .xtm formats,building on the Topic Map paradigm [WAO, short for “Work-analysisOntology”]. The rôle of this ontology is to allow understanding of the domainand to record the results of the debate about the work-analysis paradigm to beencoded in XML format alongside with the discussions within the TC.SchemaDeliver an XML Schema allowing validation for WorkML structures._4a9340de-946d-11e1-b3fe-79e3222d735f1.2An XML Schema allowing validation for WorkML structures [WorkMLSchema], containing the categories of this specific XML dialect and theirpossible combinations.Non-Standards Track Deliverables_4a9341b0-946d-11e1-b3fe-79e3222d735f2OverviewDeliver an overview of the state-of-the-art in work modelling._4a93426e-946d-11e1-b3fe-79e3222d735f2.1White PaperDeliver a White Paper concerning the clear-cut distinction between work modelling and task-driven documentation design and possible knowledge transfer to the latter._4a934340-946d-11e1-b3fe-79e3222d735f2.2Case StudiesDeliver case studies applying WorkML to model work in contexts such as air-traffic control, engine maintenance and software engineering._4a934426-946d-11e1-b3fe-79e3222d735f2.32012-05-02http://item-consortium.boonzai.com/document/document/599/draftcharterTIM.pdfOwenAmburOwen.Ambur@verizon.net