Mobile ontology core vocabulary is a machine readable schema intended for sharing knowledge and exchanging information both across people and across services/applications, it covers domains related to mobile communications, such as persons, terminals, services, networks. Alignment with relevant standards makes SPICE outcomes interoperable with other efforts in the field. Supporting mechanisms and techniques facilitate usage of the vocabulary and other ontological standards. The UserGroup class represents a group of SPICE users. Since a SPICE user does not have to be a human being, a SPICE UserGroup does not have to be a group of human beings. Introduced by: Michael Sutterer The Location class represents where any resource is located. It can be either an absolute location, such as geographical coordinates, or a relative location, such as in relation to some object (e.g. near a specific restaurant or a specific person), or a virtual location (e.g. in a meeting room). The User class represents a SPICE user. A SPICE user does not have to be a human being. Introduced by: Michael Sutterer The Device class represents devices. This device that can be part of a DCS of a user. The Device class is a subclass of the class dcs:DcsResource in the DCS ontology. Introduced by: Claudia Villalonga The Service class represents a SPICE service which can be deployed in the Service Execution Environment and that can be described in SPATEL. Responsible: Mariano Belaunde The Time represents time. The time can be expressed either in an absolute way (i.e., using GMT scale) or in a relative way (e.g., “half an hour after taking off on the plane”). This generic class allows alignment with existing ontologies covering the topic of time, e.g. “Time Ontology in OWL”. TODO: to figure out how such an identifier would look like and where would it be used. Anything that may have an (internal) identifier in the mobile platform. Introduced by: Martin Strohbach The PersonGroup class represents a group of Persons, i.e. a group of human beings. This PersonGroup does not have to be a SPICE UserGroup. Introduced by: Michael Sutterer An entity that has a location and or physical extent. Introduced by: Martin Strohbach A physical area. Introduced by: Martin Strohbach The Person class represents a human being. This human being does not have to be a SPICE User, but it can also be a SPICE User and hence can have a SPICE User representation. Introduced by: Michael Sutterer An entity that is idenitifiable in the system, but does not have a physical representation, e.g. policies. Introduced by: Martin Strohbach The consistsOfUser property describes the relation between the UserGroup and User class. A UserGroup can consist of multiple Users. Introduced by: Michael Sutterer The consistsOfPerson property describes the relation between the PersonGroup and Person class. A PersonGroup can consist of multiple Persons. Introduced by: Michael Sutterer The hasUserGroupRepresentation property describes the relation between the PersonGroup and the UserGroup class. A group of persons can have a representation as a group of SPICE Users. Introduced by: Claudia Villalonga Links the user to a Person. Introduced by: Martin Strohbach the location of the Entity Introduced by: Martin Strohbach TODO: decide on the format of identifiers Uniquely identifies this entity within the SPICE platform. Introduced by: Martin Strohbach The hasUserRepresentation property describes the relation between the Person and User class. A Person can have a SPICE User representation. Introduced by: Michael Sutterer