FIDIS
Future of Identity in the Information Society (No. 507512)
D2.3
[Final], Version: 2.0
File: fidis-wp2-del2.3.models.doc
Page 63
person.
Attributes: (29)
DigitalImage, DigitizedSignatureImage, XRayImage,
BodyXRaysAvailableText, BodyXRaysAvailableCode, BloodTypeText,
BloodTypeCode, Saliva, Semen, Urine, …
PersonInjury
14
Details about an injury a person has received.
Attributes: (14)
TypeText, TypeCode, DescriptionText, Date, Time, LocationText,
SeverityText, TreatmentText, TreatmentStartDate, TreatmentEndDate,
Treater.Organization, Treater.Person, Causer.Force, Causer.Person,
PersonMedicalDetails
10
A set of details about the medical condition of a person.
Attributes: (10)
MedicalDescriptionText, MedicalCondition, MedicationRequiredText,
LearningDisabilityText, PhysicalDisabilityText, VisionPrescriptionText,
MentalStateText, Injury, Intoxication, MedicalFileIndicator
PersonPhysicalDetails
34
A set of details about the physical appearance of a person.
Attributes: (34)
HeightMeasure, HeightMeasure.Range, HeightDescriptionText,
WeightMeasure, WeightMeasure.Range, WeightDescriptionText,
EyeColorText, EyeColorCode, HairColorText, HairColorCode, …
PersonSocialDetails
32
A set of details about the social characteristics of a person.
Attributes: (32)
EthnicityText, EthnicityCode, PrimaryLanguageText,
PrimaryLanguageCode.iso639-2b, PrimaryLanguageCode.iso639-2t,
SecondaryLanguageText, SecondaryLanguageCode.iso639-2b, …
6.4.1.1
Reference
JXDM; “Microsoft Excel spreadsheet of types and properties”; jxdm-3.0.2.xls;
Documentation of Release 3.0.2 of Global JXDM;
http://it.ojp.gov/jxdm/3.0.2/
6.5 Mobile user (CC/PP & UAProf)
6.5.1 CC/PP
CC/PP (Composite Capabilities/Preferences Profile,
www.w3.org/Mobile/CCPP/
) is a
standard based on Resource Description Framework (RDF). A CC/PP profile is a description
of device capabilities and user preferences. For a lot of devices such as a PC, but also a
mobile phone or a PDA, CC/PP provides a standard format of information description
enabling then any Web terminal to communicate these capacities with a given server in a
detailed way.
CC/PP is already used; the toolkit CC/PP intel contains, CC/PP Client Proxy, Client Profile
Manager API, Server Profile Repository, Server Content Customization Module. Another
interesting example of integration is the UPS (universal profiling schemata) profile package;
FIDIS
Future of Identity in the Information Society (No. 507512)
D2.3
[Final], Version: 2.0
File: fidis-wp2-del2.3.models.doc
Page 64
it is a Java package for the creation of valid CC/PP profiles (examples of profiles using the
specific fr.inrialpes.opera.upsprofiles package are available on the web
14
).
The following list (drawn up from the above mentioned examples) shows some attributes
useful for the categorisation of the users:
•
HardwarePlatform:
DeviceType, DeviceName, DeviceConstructor, screen, screenColor, RAMSize,
ROMSize, etc.
•
SoftwarePlatform:
PlatformName, PlatformVersion, etc.
•
BrowserUA:
UsedPlayerName, UsedPlayerVersion, etc.
•
Resource:
OnlySupportedResources, NonSupportedResources, AdaptableResources,
PrederredSupportedResources; in a sub-level of description, type, dimension,
resolution, version, format, functionality, kind, adaptabilityValue, priorityLevel,
requirement, etc.
6.5.2 UAProf
The User Agent Profile specification is concerned with capturing classes of mobile device
capabilities and preference information. These classes include (but are not restricted to) the
hardware and software characteristics of the device as well as information about the network
to which the device is connected. The user agent profile contains information used for content
formatting purposes. A user agent profile is distinct from a user preference profile that would
contain application-specific information about the user for content selection purposes. For
example, a user preference profile might designate whether the user is interested in receiving
sports scores and, if so, the particular teams.
UAProf (User Agent Profile) is a specification elaborated by the Open Mobile Alliance
(
http://www.openmobilealliance.org/
) and is based on the CC/PP specification.
Like CC/PP, an UAProf profile is a two level hierarchy composed of components and
attributes. Unlike CC/PP, the UAProf specification also proposes a vocabulary – a specific set
of components and attributes – to describe the next generation of WAP phones.
Information related to CPI is communicated in an XML document and covers the following attributes
of the device
15
:
•
Hardware Platform; screen size, audio, images, colour capabilities, manufacturer, etc.
•
Software Platform; operating system, content types, etc.
•
Applications/User preferences; mark-up languages and versions supported, scripting
languages supported
14
http://opera.inrialpes.fr/people/Tayeb.Lemlouma/MULTIMEDIA/CCPP/UPS-Package/UPSProfiles.html
15
from both sources:
http://www.w3.org/Mobile/posdep/ericsson-position-paper.htm
and
http://www.sourceo2.com/O2_Developers/O2_technologies/O2Guide_to_WAP/UAProf/How_UAProf_works.ht
m