1 / 14

Review of Paper:

Review of Paper:. Johan Hjelm “Position dependent services using metadata profile matching” Youyong Zou Apr.15,2001. User Position and Information. User position can change between requests for information. Different information sets can be generated for different positions

nelia
Télécharger la présentation

Review of Paper:

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. Review of Paper: Johan Hjelm“Position dependent services using metadata profile matching” Youyong Zou Apr.15,2001

  2. User Position and Information • User position can change between requests for information. Different information sets can be generated for different positions • The location can be declared, and a rule-based system can determine the relevance of the location for the user, based on the users input and the metadata declaration of the information object for the location. • 80 % of all information has a relation to a location - in other words, is position-dependent, according to the British National Geographical Data Framework

  3. So, what is problem with Position? • We defined a mechanism which includes the position as a property of the client in the content negotiation. • The content negotiation can take place over a number of different protocols, using the W3C standardized Composite Capabilities/Preference Profile format [CC/PP]. • However, a number of problems are unresolved, most urgently the number of location metadata standards that exist in the world – more than 30 !  

  4. Determine the User Position • A number of methods exist to determine the position: • GPS • Differential GPS • Network-based positioning • User input • The position of the user can either be retrieved into the user device, or into a proxy in the network, depending on the method of positioning. • The easiest way download the position information from a device into an origin server is to handle the information in the TerminalLocation attribute of the CC/PP profile.

  5. Metadata and context encoding • Use RDF to for Metadata • Determinate the relevant in the current context of the user : The device reports its position to a server, which identifies documents relevant in that position, and forwards them to the user. • Traditional full-text indexing cannot solve the problem of providing the information that is relevant in the user context.

  6. Position-relevance in metadata • Information is location relevant if it can provide the user or an agent acting on his behalf with information that can affect the situation of the user. • Define some elements: map, FieldNote, person, dataitem, data, temporal, spatial and comment.

  7. Relevances • A location may not be relevant to a user at all times, but take on a relevance at a certain time • Users may also make requests for information that is not currently relevant, but will be at the time of the validity of the request. • Relevance may also depend on the role of the user.

  8. The position layer: GML • Geographical Markup Language (GML) by the Open GIS Consortium , based on XML, and can be expressed as RDF. • GML represents the OGC Abstract Specification Simple Features as XML, which describe an object model for geometry, as curves, surfaces, and geometry collections.

  9. Event markup: SKi • SKiCal format, by Svenska Kalenderinitiativet , in RDF. • An example SKiCAL event description in RDF : … <xmlns:ICAL="http://www.w3.org/TR/WD-ical-RDF#" xmlns:SKI="http://www.w3.org/TR/WD-skical-RDF#"> <RDF:Description about="VCALENDAR"> <ICAL:vevent> <ICAL:dtstamp>200002012T120000Z</ICAL:dtstamp> <ICAL:uid>uid1@decaturapostlechurch.com</ICAL:uid> <ICAL:organizer_cn>Dean Walt Wittman</ICAL:organizer_cn> <ICAL:organizer_mailto>wittman@decaturapostlechurch.com </ICAL:organizer_mailto> <SKI:otheragents>Christian Concerts of America" Inc. </SKI:otheragents> <SKI:association>Catholic Church of North America, Diocese of Chicago</SKI:association> <SKI:title>Universal Salvation Tour</SKI:title> <SKI:performer>Cross Brothers</SKI:performer> <SKI:part_of>Decatur For Christ Week</SKI:part_of> …

  10. Matching metadata and profile • Different parameters will require different matching algorithms, depending on the data type. • The matching can be integrated with the web server. • The CC/PP profile can be cached in the server and re-used as long as it is valid. • SKi format can easily be matched with the position and temporal preferences of the user.

  11. Composite Capability/Preference Profile • CC/PP profile is a collection of the capabilities and preferences associated with user and the agents used by the user to access the World Wide Web. • The basic data model for a CC/PP is a collection of tables. • The profile is associated with the current network session or transaction • A collection of "default" properties , update of a profile to the profile repository

  12. WAP Forum UAPROF • The Wireless Application Protocol system : bringing information to mobile telephones. • The User Agent Profile (UAProf) specification extends WAP 1.1 to enable the end-to-end flow of a User Agent Profile, also referred to as Capability and Preference Information (CPI)

  13. CPI • CPI is based on CC/PP , seeks to minimize wireless bandwidth consumption • Each network element may add additional profile information to the transmitted CPI. • Origin servers, gateways, and proxies can use the CPI to ensure that the user receives content that is particularly tailored for the environment • CPI permits the origin server to select and deliver services that are appropriate to the capabilities of the requesting client

  14. Conclusion • This paper demonstrate the concept: A meta-description of the information object can be matched with the users preferences and device capabilities. • Hope to will find wide acceptance, as it enables totally new classes of services.

More Related