Community:AcademicRoles - Revision history

EnricoDaga at 15:55, 3 March 2010

2010-03-03T15:55:47Z

EnricoDaga at 13:45, 3 March 2010

2010-03-03T13:45:00Z

EnricoDaga: Text replace - 'Include Image' to 'Graphical representation'

2010-03-01T12:45:55Z

Text replace - 'Include Image' to 'Graphical representation'

EnricoDaga: Text replace - 'RelatedCP' to 'RelatedPattern'

2010-03-01T10:46:30Z

Text replace - 'RelatedCP' to 'RelatedPattern'

MichaelUschold at 19:15, 26 February 2010

2010-02-26T19:15:42Z

MichaelUschold at 06:56, 20 January 2010

2010-01-20T06:56:46Z

MichaelUschold at 06:31, 20 January 2010

2010-01-20T06:31:19Z

MichaelUschold at 06:21, 20 January 2010

2010-01-20T06:21:47Z

MichaelUschold at 04:50, 20 January 2010

2010-01-20T04:50:05Z

MichaelUschold at 23:25, 18 January 2010

2010-01-18T23:25:56Z

← Older revision		Revision as of 15:55, 3 March 2010
Line 83:		Line 83:
	</rdf:RDF>		</rdf:RDF>
	{{My references}}		{{My references}}
		+	{{Modeling Issue toolbar}}

@@ Line 2: / Line 2: @@
 |Title=Academic People and their Roles
 |Description=I need to represent people of the academic staff. Each person can play different roles in different contexts.
 }}
 {{Modeling Issue Template
@@ Line 10: / Line 13: @@
 |RelatedPattern=Objectrole
 }}
-{{Graphical representation
+{{Additional information header}}
-|ImageName=MI-AcademicRole.jpg
 }}
 This new pattern imports the objectrole pattern and adds a few things. We need to represent an '''agent''' that is '''playing a role''' in a given '''context'''. This would be most natural to represent as a ternary relation, but for OWL we reify this as a Class called RolePlay (RoleInContext would also be a good name).  RolePlay has three properties:
 # Context (e.g. the NEON project)
@@ Line 81: / Line 82: @@
    </AcademicRolePlay>
 </rdf:RDF>

@@ Line 10: / Line 10: @@
 |RelatedPattern=Objectrole
 }}
-{{Include Image
+{{Graphical representation
 |ImageName=MI-AcademicRole.jpg
 }}

@@ Line 8: / Line 8: @@
 |CompetencyQuestion=who plays a certain role within that project?
 |Scenario=Enrico Motta is the coordinator of the NeOn project
-|RelatedCP=Objectrole
+|RelatedPattern=Objectrole
 }}
 {{Include Image

@@ Line 9: / Line 9: @@
 |Scenario=Enrico Motta is the coordinator of the NeOn project
 |RelatedCP=Objectrole
 }}
 This new pattern imports the objectrole pattern and adds a few things. We need to represent an '''agent''' that is '''playing a role''' in a given '''context'''. This would be most natural to represent as a ternary relation, but for OWL we reify this as a Class called RolePlay (RoleInContext would also be a good name).  RolePlay has three properties:

@@ Line 10: / Line 10: @@
 |RelatedCP=Objectrole
 }}
 This new pattern imports the objectrole pattern and adds a few things. We need to represent an '''agent''' that is '''playing a role''' in a given '''context'''. This would be most natural to represent as a ternary relation, but for OWL we reify this as a Class called RolePlay (RoleInContext would also be a good name).  RolePlay has three properties:
 # Context (e.g. the NEON project)
@@ Line 30: / Line 27: @@
      xmlns="http://www.ontologydesignpatterns.org/cp/owl/academicrole.owl#"
      xmlns:objectrole="http://www.ontologydesignpatterns.org/cp/owl/objectrole.owl#"
      xmlns:owl="http://www.w3.org/2002/07/owl#"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
@@ Line 35: / Line 33: @@
    xml:base="http://www.ontologydesignpatterns.org/cp/owl/academicrole.owl">
    <owl:Ontology rdf:about="">
      <owl:versionInfo rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
      >Created with TopBraid Composer</owl:versionInfo>
    </owl:Ontology>
    <owl:Class rdf:ID="Person">
-     <rdfs:subClassOf>
+     <rdfs:subClassOf rdf:resource="http://www.ontologydesignpatterns.org/cp/owl/agentrole.owl#Agent"/>
-      <owl:Class rdf:ID="Agent"/>
-    </rdfs:subClassOf>
    </owl:Class>
    <owl:Class rdf:ID="AcademicRolePlay">
@@ Line 48: / Line 44: @@
        <owl:Class rdf:ID="RolePlay"/>
      </rdfs:subClassOf>
    </owl:Class>
    <owl:Class rdf:ID="AcademicRole">
@@ Line 62: / Line 55: @@
    </owl:Class>
    <owl:ObjectProperty rdf:ID="rolePlayAgent">
      <rdfs:domain rdf:resource="#RolePlay"/>
    </owl:ObjectProperty>
    <owl:ObjectProperty rdf:ID="rolePlayRole">
      <rdfs:domain rdf:resource="#RolePlay"/>
    </owl:ObjectProperty>
    <owl:ObjectProperty rdf:ID="rolePlayContext">
      <rdfs:domain rdf:resource="#RolePlay"/>
    </owl:ObjectProperty>
    <AcademicRole rdf:ID="Professor"/>
    <AcademicRolePlay rdf:ID="EnricoNEON">
      <rolePlayRole>
        <AcademicRole rdf:ID="Coordinator"/>
      </rolePlayRole>
    </AcademicRolePlay>
 </rdf:RDF>

@@ Line 4: / Line 4: @@
 }}
 {{Modeling Issue Template
-|Author=AldoGangemi
+|Author=AldoGangemi, MichaelUschold
 |Domain=Academy, University
 |CompetencyQuestion=who plays a certain role within that project?
@@ Line 11: / Line 11: @@
 }}
-We have a ternary relation here that can be reified into an object called: RolePlay which has three attributes:
 # Context (e.g. the NEON project)
 # Player - the Agent playing the role (e.g. Enrico)
 # Role  - the role being played) (e.g. Coordinator)
-Also adds classes and instances:
+We also add some new classes and instances:
-* Person with one instance, Enrico
+* Agent and  a subclase Person with one instance, Enrico
 * AcademicRole with two instances: Coordinator and Professor
 NB: probably this pattern should be renamed to be something like 'RoleInContext' and then specialized for academic roles in context.