1 / 23

Context and user sensitivity

Context and user sensitivity. Patrick De Causmaecker. ‘Hard’ properties. Interfaces, bandwidths Power consumption Screen size Interfaces Computing power, memory size Operating system Agent platform …. Standards. FIPA Device Ontology Specification

barb
Download Presentation

Context and user sensitivity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Context and user sensitivity Patrick De Causmaecker

  2. ‘Hard’ properties • Interfaces, bandwidths • Power consumption • Screen size • Interfaces • Computing power, memory size • Operating system • Agent platform • …

  3. Standards • FIPA Device Ontology Specification • http://www.fipa.org/specs/fipa00091/XC00091C.pdf • Composite Capability/Preference Profiles • http://www.w3.org/TR/CCPP-struct-vocab/

  4. FIPA Device Ontology Specification device hw-description sw-description connection-dn ui-description memory-dn info-dn screen-dn ap-description qos resolution-dn memory-type-dn

  5. FIPA Device Ontology Specification : use case Agent A1 sends its device profile to DF and registers to the system. Agent B1 interacts with agent A1 residing on device A. Agent B1 queries A’s device profile either from the DF or directly from device A. Agent B1, which aims to send an image (640x480x24bits) to the user, analyses the device profile user interface capabilities.

  6. FIPA Device Ontology Specification : use case A new client logs in to an agent service domain providing tourism services. The service provision agent receives the device profile from the device software system accessing the agent-based services using ACL. The provision agent first stores the profile into a local cache (for example, CC/PP caching) and then checks the services available for this particular type of client. The device profile indicates that the device is part of an agent platform, which makes it eligible to access directly all of the agent based services, depending on whether or not it hosts or is capable of hosting the correct interface agents or layers. The agent on the device may contact the service agents directly and send the device profile for adaptation.

  7. FIPA Device Ontology Specification : use case Another client is not capable of hosting an agent platform or being a part of an existing platform, but hosts browser software that supports html content with streaming audio. The specific output capabilities of the browser are extracted from the sw-description extension fields. The client contacts the provision agent through a proxy that, using some proprietary format, accepts the device profile. Now, the provision agent has to exclude those services that cannot be accessed using proxies that mediate between non-agent and agent based resources.

  8. FIPA DOS and W3C CC/PP CC/PP • Terminal Hardware, Terminal Software, Terminal Browser. • RDF/XML FIPA DO • Terminal Hardware, Terminal Software • Agents Platform • FIPA ACL • Can work together • May be extended

  9. The way Graham Bell imagined his telephone (patented in 1876, without a working version, disputed by Elisha Gray, inventor of a.o. the telautograph in 1888) Alexander Graham Bell's design sketch of the telephone CREDIT: Bell, Alexander Graham. "Alexander Graham Bell's design sketch of the telephone, ca. 1876. " Ca 1876. Alexander Graham Bell Family Papers, Manuscript Division, Library of Congress.

  10. Taking the idea one step furtherA variety of customers…

  11. and the even more contempory …want to meet in ‘telephone space’ whenever most of them feel as easy as possible

  12. Presence and availability • Presence informs about whether or not a user is connected, logged in (instant messaging) • Availability informs about user status once presence is confirmed. This may be available/unavailable, in meeting, on a call. Availability may be differentiated…

  13. Presence and availability • A presence server may know about the devices you have, and decide to reroute a message to your phone if you are logged off, it may handle ‘on a call’ and even ‘in a meeting’ or ‘differentiated availability’ situations. • See http://www.parlay.org/specs/

  14. What when we have to look into the future? • Planning, scheduling, timetabling systems need information about future ‘presence and availability’. • Furthermore, preferences should be taken into account when fixing meetings on behalf of a user. • E.g. an agenda system. • When asked for a slot the system has to take into account expectations of availability. • It can e.g. do so

  15. The problem

  16. See • Our HOBU projects • http://allserv.kahosl.be/~ocapi/ • http://ingenieur.kahosl.be/projecten/coala/ • RADAR (Carnegie Mellon) • http://www-2.cs.cmu.edu/~cmradar/

  17. Pending Commited Infeasible 11:00 - 12:30 2:00 - 3:00 4:00 - The problemhttp://www-2.cs.cmu.edu/~cmradar/CMRadarMay03.ppt Request: Template, T • When: Thursday 15th • Duration: 1 hour • Who: Visiting Researcher (Priority: “medium”) • Where: 1502E NSH Response, R: • 4:00 - 6:00 … but would 1/2 hour be sufficient? Policy preference: Avoid lunch hour Pending reservation but lower priority … Preference Order: 4:00 - 6:00 2:00 - 3:00 11:00- 12:00 Evaluate Options Threshold Generate Options

  18. The problemhttp://www-2.cs.cmu.edu/~cmradar/CMRadarMay03.ppt Editor Calendar Display Preferences and Profiles Learning Processes Email Stream Knowledge Base Extractor Message Stream Manager Scheduler Email Stream

  19. Remarks • Learning systems are slow • Need for a more dynamical approach, with triggers indicating a change in the user behaviour • The system should know/take into account the global plan of the user • Resources, devices, interfaces may be treated analogously

  20. What is it that I wanted to say • Mobile devices create new challenges for planning software • The applications need/get more accessible information on hardware characteristics • Services at the lower levels may be suggested from the application development level • We are experienced • We will supply advice on these points • We want to define research projects to delve deeper into these subjects

  21. On June 3, 1880, Alexander Graham Bell transmitted the first wireless telephone message on his newly-invented "photophone" The telephone needs a wire, that is a disadvantage, let us invent the ‘photophone’

  22. Alexander Graham Bell speaking on the telephone in 1892 CREDIT: "Alexander Graham Bell Speaking on the Phone, 1892." 1892. Gilbert H. Grosvenor Collection, Prints and Photographs Division, Library of Congress.

  23. Credit: Christine Ciesiel at http://jefferson.village.virginia.edu/~meg3c/id/id_home.html

More Related