Changes between Initial Version and Version 1 of UserContextOntology


Ignore:
Timestamp:
Jul 30, 2006, 12:57:00 PM (20 years ago)
Author:
schwarz
Comment:

First few words about the UserContextOntology

Legend:

Unmodified
Added
Removed
Modified
  • UserContextOntology

    v1 v1  
     1= User Context Ontology =
     2
     3A top-level RDF Schema for modeling and processing user context. Besides mere user context *data* the UserContextOntology will also provide operators and comparators for that data. Hence, two parties can share their user context data and will be able to understand and process the user context information at least on the upper level we define here.
     4
     5----
     6
     7== Phil's short memo about it ==
     8
     9
     10Context ontology
     11
     12What is the purpose:
     13
     14The goal is to create a context ontology describing a wide range of user context attributes and the relation ships between them.
     15The top level ontology needs to be abstract enough in order to hold for a wide range of different context "models" and to describe more detailed ones it needs to be extendable through well defined interfaces.
     16
     17Generic reasoning is performed on the high level context ontology and through the extensions more specific reasoning is made possible.
     18How much "domain knowledge" needs to be present in the higher level?
     19
     20
     21INTERFACES:
     22The extension interface needs to be well defined.
     23
     24We could take the analogy of microformats which are small semantic descriptions of components, they are mainly used for semantically linking blogs. They are often used stand alone, but for our
     25purpose a strict extension policy is required.
     26A context microformat should be written in the same language as the high-level description, e.g. RDF. A well defined blueprint should be provided to the creator of the
     27framework extensions, as well as a syntax checker making sure the extensions can be integrated into the high level structure.
     28
     29For Bluetooth the RDF extension would look something like the following:
     30
     31<rdfs:Class rdf:about="&kb;Bluetooth"
     32         rdfs:label="Bluetooth">
     33        <rdfs:comment>Bluetooth is a short range communicaiton device which can also be used to detect other Bluetooth devices in short proximity</rdfs:comment>
     34        <rdfs:subClassOf rdf:resource="&kb;Communication_Device"/>
     35        <rdfs:subClassOf rdf:resource="&kb;Sensor_Device"/>
     36</rdfs:Class>
     37
     38Stating that Bluetooth is a Communication_Device and a Sensor_Device, as well as optional comments aimed at the human user. This field could contain
     39a small xml description of e.g. sensing frequency and power consumption. Enabling the application builder or other reasoning engines to understand device specific
     40capabilities which do not affect the general use of the extension.
     41
     42<rdfs:Class rdf:about="&kb;Bluetooth_Scanner"
     43         rdfs:label="Bluetooth_Scanner">
     44        <rdfs:subClassOf rdf:resource="&kb;Bluetooth"/>
     45        <rdfs:subClassOf rdf:resource="&kb;Proximity_Location"/>
     46        <rdfs:subClassOf rdf:resource="&kb;Software"/>
     47</rdfs:Class>
     48
     49Bluetooth_Scanner is the software which needs to be invoked to get a proximity location. The RDF description shows that it "depends" on Bluetooth hardware??? ask Sven if there is a way
     50to show dependencies or is this just done through subclasses?
     51
     52
     53Reasoning engines:
     54
     55We need at least two types: one for queries and one for the application builder.
     56
     57What are good existing engines?
     58
     59How can a reasoning engine adopt dynamically to the extensions?
     60It could for example just use a Bluetooth device to find close entities. Is this good enough or does it need to know more?
     61
     62Possible queries:
     63
     64Who is near me?
     65Through proximity sensors and reasoning about the location of other entities.
     66
     67Where am I?
     68Through location sensors and through devices in close proximity which know their location.
     69
     70Problems:
     71Proximity: how to define proximity? Should entities performing a query be able to specify what it means to them?
     72Chain of reasoning: When for example a device in close proximity cannot provide a location but it is close to another one which can --- is that too far?
     73This requires to be able to associate confidence values with query results.
     74Also the time to live indicators need to be handled correctly in order to place any confidence on them.
     75
     76
     77
     78
     79A list with the different terms and definitions would be very useful.
     80
     81
     82Definition of context. Anind.... Richard had another one which is very similar but coming from another direction.
     83
     84context-aware
     85
     86context memory / history
     87
     88
     89
     90Context attribute
     91
     92Context listener: can register to or poll new context attributes and passes them on to an application
     93
     94Context tracker: takes a context attribute from a sensor or application and places it into the context store.
     95
     96Context aggregator: takes n number of context attributes as input and outputs n number of new context attributes. It can be viewed as a combination of
     97a context tracker and listener.
     98
     99
     100
     101
     102
     103
     104
     105
     106
     107
     108
     109
     110
     111
     112
     113
     114
     115
     116
     117
     118
     119
     120
     121
     122
     123
     124
     125
     126
     127