Ontology Class Hierarchy Sample Clauses

Ontology Class Hierarchy. ‌ The class hierarchy of the ontology is shown in Figure 3.1. Anything entered in the ontology (any owl:Thing) is a Concept. Instances of class Concept are further divided in the types of Project, ActivityDiagram, AnyActivity, Actor, Action, Object, Condition, Transition and Property. Project refers to the project analyzed while ActivityDiagram stores each diagram of the system. Note that ActivityDiagram covers all dynamic view diagrams of the system, i.e. it is not limited to activity diagrams, but also storyboards and generally any diagrams with dynamic flows of action. When instantiating the ontology, Project and ActivityDiagram can be used to keep its structure reversible. Since each project has several diagrams and each diagram has several other concepts (see next subsection for relations), one can reconstruct the diagrams of the project with their respective concepts. AnyActivity is one of the most central OWL classes of the ontology. It involves all activities shown in a diagram. This class is further distinguished in the following OWL subclasses: 6 Note that in the context of S-CASE, we use OWL since it is a well-known established standard of current research and industry communities. For an extensive review of OWL languages and tools, the reader is referred to the deliverable 4.1. FP7-ICT-610717
Sample 1
AutoNDA by SimpleDocs
Ontology Class Hierarchy. ‌ The class hierarchy of the aggregated ontology is shown in Figure 5.1. Anything entered in the ontology is a Concept. Instances of Concept are further divided in four main classes: Project, Requirement, ActivityDiagram, and Element. Project refers to the software project instantiated in the ontology. Classes Requirement and ActivityDiagram are used to hold the corresponding requirements and diagrams of the static and the dynamic ontology respectively. Note that the instances of these two classes are also used in order to keep track of the source of each element in the ontology. In other words, they can be used as connectors of the aggregated ontology to the static and dynamic ontologies. Any other Concept of the ontology is an Element of the software project. Instances of type Element are further divided into the following subclasses:
Sample 1
Ontology Class Hierarchy. The class hierarchy of the ontology is shown in Figure 1. As shown in that Figure, anything entered in the ontology (any owl:Thing) is actually a Concept. Instances of class Concept are further divided in the types of Project, Requirement, ThingType, and OperationType. Project refers to the project analyzed while Requirement stores each functional requirement of the system. These two types are useful for instantiating the ontology while keeping the structure reversible. Since each project has several requirements and each requirement has several other concepts (see next subsection for relations), one can reconstruct the main structure of each project including each one of the requirements with the respective concepts. ThingType and OperationType are the main types of objects found in any functional requirement. The former refers to acting units and units acted upon, while the latter involves all types of actions performed by the acting units on other objects. In specific, a ThingType instance can be one of the following classes: • actor: refers to the actors of the project. It includes three types of subclasses: o useractor: the users of the system o external_system: any external systems interacting with the systemc o system: the system itself is also an actor • object: involves any object or resource of the system that receives some action. Since the nature of some objects can be composite (or generally have some notion of transitiveness), the concept of receiving an object from a composite object or sending some object to a composite object has to be modeled. Thus, three subclasses of object are defined: o theme: the main subclass of object, involving any generic object or resource of the system o source: involves objects that are sources of other objects. For example, for the phrase “get tag from bookmark”, “tag” would be mapped as theme and bookmark as source.
Sample 1

Related to Ontology Class Hierarchy

  • Job Classification When a new classification (which is covered by the terms of this Collective Agreement) is established by the Hospital, the Hospital shall determine the rate of pay for such new classification and notify the local Union of the same. If the local Union challenges the rate, it shall have the right to request a meeting with the Hospital to endeavour to negotiate a mutually satisfactory rate. Such request will be made within ten (10) days after the receipt of notice from the Hospital of such new occupational classification and rate. Any change mutually agreed to resulting from such meeting shall be retroactive to the date that notice of the new rate was given by the Hospital. If the parties are unable to agree, the dispute concerning the new rate may be submitted to arbitration as provided in the Agreement within fifteen (15) days of such meeting. The decision of the Board of Arbitration (or arbitrator as the case may be) shall be based on the relationship established by comparison with the rates for other classifications in the bargaining unit having regard to the requirements of such classification. When the Hospital makes a substantial change in the job content of an existing classification which in reality causes such classification to become a new classification, the Hospital agrees to meet with the Union if requested to permit the Union to make representation with respect to the appropriate rate of pay. If the matter is not resolved following the meeting with the Union the matter may be referred to Arbitration as provided in the Agreement within fifteen (15) days of such meeting. The decision of the Board of Arbitration (or arbitrator as the case may be) shall be based on the relationship established by comparison with the rates for other classifications in the bargaining unit having regard to the requirements of such classifications. The parties further agree that any change mutually agreed to or awarded as a result of arbitration shall be retroactive only to the date that the Union raised the issue with the Hospital. Notwithstanding the foregoing, if as a result of compensable illness or injury covered by WSIB an employee is unable to carry out the regular functions of her position, the Hospital may, subject to its operational requirements, establish a special classification and salary in an endeavour to provide the employee with an opportunity of continued employment. This provision shall not be construed as a guarantee that such special classification(s) will be made available or continued.

  • SPECIALIZED JOB CLASSES Where there is a particular specialized job class in which the pay rate is below the local market value assessment of that job class, the parties may use existing means under the collective agreement to adjust compensation for that job class.

  • New Classification Should a new position or new classification be created within the Bargaining Unit during the term of this Agreement, the Employer and the Union will decide the rate of pay. Nothing herein prevents the Employer from filling such positions and having Nurses working in such positions during such negotiations. The salary when determined will be retroactive to the date on which the successful candidate commenced work in that classification.

  • Hierarchy In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. Clause 6 Description of the transfer(s) The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. Clause 7 Docking clause

  • Client Classification 7.1. We shall not have an obligation to treat our clients in different classes depending on their knowledge and expertise.

  • New Job Classifications 11.1 Whenever the Company determines it appropriate to create a new job classification in the bargaining unit, it shall proceed as follows.

  • Position Classification 1. The requirements of each position will be documented by a Position Description developed by reference to the Position Description Questionnaire (PDQ), and classified into a salary grade consistent with the Position Description and classifications for corresponding job duties found throughout the USNH System and according to USNH policy and processed by the KSC Office of Human Resources.

  • Work in Higher Classification Employees working in a higher classification for more than four (4) hours in duration shall be paid at the higher rate of pay for the entire shift.

  • JOB CLASSIFICATIONS For the purpose of this Agreement the following classifications will be applicable:

  • New Classifications If a new classification is created within the bargaining unit, the Employer agrees to meet with the Union and negotiate a rate of pay for this new classification. If the parties cannot reach agreement, at the request of either party, the matter shall be submitted to the arbitration procedure in Article 26 of this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.