Device Descriptions and User Profiles

Device Descriptions and User Profiles 인공지능연구실 정홍석

Overview • 정보를 특정 장치에서 표현할 수 있도록 적합하게 변환하거나, 컴퓨터 기반 장치에서 다른 여러 장치(mobile phone,PDA, … )로 호환되게 변환하기 위해 참고하는 Device와 User에 대한 설명. CC/PP

CC/PP Concept • Problem • Capabilities of individual devices. • Preferences of its user. • Issues • Flexibility • Extensibility • Distribution • Conclusion • Device Profile with RDF • Feature : Reference Profile Information via URI. • Benefit : Decrease of Network Transaction • DB Concept in the Web Server. CC/PP

CC/PP Definition • Composite Capabilities/Preferences Profiles • A user side framework for content negotiation. • Collection of capabilities and preferences associated with the user and user agents. • e.g. Hardware, Software, OS, etc. • Using RDF - Resource Description Framework, an XML application. CC/PP

CC/PP Data Model • Components • CC/PP profiles are structured into named components, each containing a collection of attribute-value pairs, or properties. • Components – specified by aW3C. • The hardware characteristics • The software characteristics • The application and user preferences • etc. • A profile have at least one or more components. • Each component have at least one or more attributes. • Requirements • Compatible, Flexibility • So, RDF • [Subject-resource] – propertyName  [Object-resource] • The data model for CC/PP profiles is similar to a table of tables. CC/PP

CC/PP profile Structure <?xml version="1.0"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ccpp="http://www.w3.org/2002/ 11/08-ccpp-schema#" xmlns:example="http://www.ex-ample.com/schema#"> <rdf:Description rdf:about="http://www.example.com/profile#MyProfile"> <ccpp:component> <rdf:Description rdf:about="http://www.example.com/profile#TerminalHardware">  </rdf:Description> </ccpp:component> <ccpp:component> <rdf:Description rdf:about="http://www.example.com/profile#TerminalSoftware">  </rdf:Description> </ccpp:component> </rdf:Description> </rdf:RDF> • Example • the hardware platform upon which software is executing, • the software platform upon which all applications are hosted, or • an individual application, such as a browser. • [example:MyProfile] – ccpp:component  [example:TerminalHardware] or [example:TerminalSoftware] CC/PP

Defaults • Predefined the attributes of a component by vendor • Similar to the idea of dynamic inheritance • [ex:MyProfile] • | • +--ccpp:component--> [ex:TerminalHardware] • | • +--rdf:type--------> [ex:HardwarePlatform] • +--ccpp:defaults---> [ex:HWDefault] • +--ex:memoryMb-------> "32" • [ex:HWDefault] • | • +--rdf:type----> [ex:HardwarePlatform] • +--ex:displayWidth--> "320" • +--ex:displayHeight--> "200" • +--ex:memoryMb---> "16" CC/PP

CC/PP Schema • a CC/PP schema is governed by the following rules • The schema must be associated with a well-defined vocabulary • The schema must consist of one or more components. • All components have the same schema structure. • Each comoponent must be an object of type Class and may contain a subordinate description block for default attributes. • Attributes considered to be default capabilities or characteristics must be described within the Default description block. • Descriptions to override the default values must also be included in the component description but outside the Default description block CC/PP

Defined Basic Components • By CC/PP working group • HardwarePlatform – hardware chracteristics of the terminal device • SoftwarePlatform – operating environment of the device • By WAP Forum UAProf • BrowserUA – A set of attributes to describe the browser application • NetworkCharacteristics – network-related environment • WapCharacteristics – WAP capabilities • … CC/PP

Modification of Properties • Adding and modifying attributes associated with the current CC/PP information. • ex) • turning sound on and off. • memory upgrade. • Defaults will need to be overriden. • ex) If Sound were to be changed from Off to On. <?xml version=“1.0”?> <RDF xmlns:RDF=http://www.w3c.org/TR/WD-rdf-syntax# xmlns:PRF=http://www.w3c.org/TR/WD-profile-vocabulary#> <Description ID=“SoftwarePlatform” PRF:Sound=“On” /> </RDF> CC/PP

Remote Referencing • Instead of enumerating each set of attributes, a remote reference can be used to name a collection of attributes such as the hardware platform defaults. • This has the advantage of enabling the separate fetching and caching of functional subsets. • If an application in the server/gateway/proxy uses RDF to process the CC/PP, it may encounter attributes with default values and user-specified values. • RDF does not provied a convenient mechanism for inplementing the override rule • ex) • If user upgraded Memory to 32mb, then there is no reason to send the hardware platform’s default setting of “memory=16mb” CC/PP

Bandwidth and Caching • Transporting Client Profiles • Transporting is needed between different protocols. • WAP  HTTP • Wireless networks is slow, compared wireline networks. • WSP – Wireless Session Protocol • WDP – Wireless Datagram Protocol CC/PP

Towards the Semantic Web • Transformation is the same thing as filtering • The user does not have to be human • Web services can be more efficient using contextualization • For a user, you can make a totally personal presentation • Location dependent services are just one aspect of environmental adoption of content CC/PP

Other Formats • CONNEG Format: • Format using feature-tags from a registry. The feature set predicates as “mathematical relations” which defined constraints on feature-handling capabilities. • Resource Capability Protocol (RESCAP): • Protocol for the purpose of extremely lightweight (only a few bytes per transaction). • Session Description Protocol (SDP): • This is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. CC/PP

Profile Problems • Matching algorithms • Database matching works well in a single-node environment, but maybe not in multi-node environments • Communicating and exchanging profiles • Which protocol: SOAP, BEEP, i-CAP, HTTP? And how? • In a trusted way? • Formats (frameworks) and vocabularies • Not only do we need to define them, we also need to publish them, preferrably as standards • Security • 데이타 전송 시 문제점 • privacy and trust CC/PP

Platform for Privacy Preferences(P3P) • P3P clients automatically fetch and read P3P privacy policies on Web sites. • A user's browser equipped for P3P can check a Web site's privacy policy and inform the user of that site's information practices. • The browser could then automatically compare the statement to the privacy preferences of the user, self-regulatory guidelines, or a variety of legal standards from around the world. • P3P client software can be built into a Web browser, plug-ins, or other software. CC/PP

P3P Mechanism CC/PP

Platform for Privacy Preferences • P3P enables Web sites to translate their privacy practices into a standardized, machine-readable format (XML) that can be retrieved automatically and easily interpreted by a user's browser. • Translation can be performed manually or with automated tools. • Once completed, simple server configurations enable the Web site to automatically inform visitors that it supports P3P. CC/PP

Device Descriptions and User Profiles