Skip to content

Profile

Jump to bottom
Alejandro M. Medrano Gil edited this page May 4, 2017 · 5 revisions

The profiling ontology covers the concepts needed originally by the User Model building block, but adds a twist to its final purpose. Not only it models users and their characteristics, but also any other basic concept which characteristics are of interest to the universAAL platform: The AAL Services and the uSpace themselves. This way the ontology is dedicated to model profiles of entities that can be further described through these profiles and further sub-profiles.

Observations

User model depends greatly on the implemented platform and thus must be completely developed to match 100% the needs of universAAL. There have been 3 different kind of profiles identified, the user profile (defining the users of the system), the uSpace profile (defining the appliances, capabilities and software in the environment) and the AAL Service profile (describing an AAL Service details). These profiles must be harmonised and be fully compatible, as they are a key feature to be used for the proper configuration and operation of the platform.

A hierarchy of profiles and sub-profiles was determined as well. However the appearance of the new implementation of the data representation required a revised design of this initial proposal. Finally it was simplified to represent the basic concepts that can have a profile, and the basic abstract representation of the associated profiles.

These profiles and sub-profiles are mostly empty, with only basic characteristic or parameter to define the profilable entities that can have them. Extra parameters will have to be defined later and added via the extension capability of the new data representation. If some of these parameters come to be considered thoroughly used and stable, it can be decided to include them by default in the profiling ontology itself.

Profile information can be handled in the system by using the Profiling and uSpace Servers, which make extensive use of this ontology.

Diagram

After designing an initial proposal for profiling ontology in WP3, this was discussed with WP2 and repurposed to match the capabilities of the new Data Representation. Then it was discussed again from WP3. As a result, the ontology design resulted in the following diagram:

Take into account that in the implementation:

  1. User is backwards compatible with previous implementations, but only if used as standalone concept. Methods and properties are not backwarts compatible.
  2. Profiles have no parameters (no properties). These will have to be either added later by related taskforces or extended from an external additional ontology artifact.
  3. SubProfile is a single concept without properties. Application developers should create their own subprofiles with their own parameters, inheriting from SubProfile.
  4. Service ontology is included in the implementation (not shown in diagram). Currently there are 2 srvices until they are refined: ProfilingEditorService and ProfilingService. Right now they are identical, and have a "controls" property over the most "rooted" concept: Profilable.
  5. Personal information subprofile implements ETSI ES 202 746 and part of ES 202 642. It uses plenty (but not all) of VCard concepts. Used VCard ontology elements are also implemented in this ontology artifact.
  6. Profilable, Profile and SubProfile return false to isClosedCollection (as of version 1.3.4-S). This means that subclasses can store any number of values into their multi-value properties without overwriting previous ones. This was set this way in order to work better with the CHE where Profiling Server stores this information.

Elements

ProfilableEntity
Any concept that can have a an associated profile. It is an abstract element and cannot have individuals. Services have a handle over this element, so it works as entry point.
AALSpace
Ontological representation of the uSpace where the system runs. It refers to its abstract/logical idea (a space were a user is served with AAL services) not its physical distribution (although it an be related). To be refined by uSpace taskforce.
AALService
Embodiment of a specific value addressing a need provided by one party (service provider entity) to another (service requester entity). As a result of consuming a service, the requester entity perceives value such as being relieved of a certain task. In the process of providing a service, several (hardware / software / human) resources might be involved; in particular, other subordinate services might be utilized, as well. To be refined by WP3.
User
A human being that interacts with the system in some way.
AssistedPerson
The end user that is the focus of the AAL services.
Caregiver
The user that can aid the AssistedPerson.
Profile
A collection of parameters that describe some characteristics related to a ProfilableEntity.
UserProfile
A collection of parameters that describe some characteristics related to a User.
AssistedPersonProfile
A collection of parameters that describe some characteristics related to an AssistedPerson.
CaregiverProfile
A collection of parameters that describe some characteristics related to a Care giver.
SubProfile
A subset of parameters that describe some concrete characteristics related to a ProfilableEntity, restricted to an specific domain. For each domain a subelement of SubProfile has to be implemented.
PersonalInformationSubprofile
Personal information subprofile as described (mainly) in ETSI ES 202 746 and 642
Gender
Gender of the user as described in ETSI ES 202 746 and 642
VCard
VCard: Resources that are vCards and the URIs that denote these vCards can also be the same URIs that denote people/orgs. This element is included only to more fully implement the VCard ontology, but is not used in the Profile Ontology of uAAL.
Tel
VCard: Resources that are vCard Telephony communication mechanisms.
Voice / Cell / Fax / Car / Video / Modem / PCS (Personal Comm.) / Msg (Voice Msg.) / Pager / ISDN / BBS (Bulletin Board Sys.)
VCard: Different subclasses of Tel, depending on each different technology.
Email
VCard: Resources that are vCard Email Addresses.
Internet / X400
VCard: Different subclasses of Email Addresses.
Name
VCard: Resources that are vCard personal names.
Organization
VCard: Resources that are vCard organizations.
AALServiceProfile
A collection of parameters that describe some characteristics related to a AALService.
HRSubProfile
A SubProfile representing any arbitrary Human Resource as part of a AAL Service.
AALAppSubProfile
A SubProfile representing the (or one of the) software (application) part of a AAL Service.
HWSubProfile
A SubProfile representing any arbitrary Hardware Resource that is part of a AAL Service.
Property
A value-property pair for AAL Service Resources (Human, HW and App). Do not confuse with native RDF Property. Shown in the diagram as "ProfileProperty".
Requirement
A Hardware or Software requirement for an AAL Application
AALSpaceProfile
A collection of parameters that describe some characteristics related to a uSpace.
ConnectionDetails
Network connection details for an arbitrary host.
OntologyEntry
Ontology entry available in the space provided by an app.
Clone this wiki locally