Skip to main content
Jump to: navigation, search

Difference between revisions of "Context Types"

m (ContextTypes moved to Context Types: Avoid CamelCase page names)
m (Added tag for left menu)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
This page defined context types (simple strings) to be used to establish the association between context IDs and context factories. This process is handled by the IdASRegistry. See [[ContextDiscoveryComponents]] for more information about the involved Higgins components.
+
{{#eclipseproject:technology.higgins}}
 +
This page defined context types (simple strings) to be used to establish the association between context IDs and context factories. This process is handled by the IdASRegistry. See [[Context Discovery Components]] for more information about the involved Higgins components.
  
 
A context type should be assigned for every "underlying technology" we can open as a context. Typically, each context factory can open contexts of a single context type.
 
A context type should be assigned for every "underlying technology" we can open as a context. Typically, each context factory can open contexts of a single context type.

Latest revision as of 08:43, 15 March 2008

{{#eclipseproject:technology.higgins}} This page defined context types (simple strings) to be used to establish the association between context IDs and context factories. This process is handled by the IdASRegistry. See Context Discovery Components for more information about the involved Higgins components.

A context type should be assigned for every "underlying technology" we can open as a context. Typically, each context factory can open contexts of a single context type.

The following is a list of "underlying technologies" for which we have context factories.

InMemory

Context Type: (to be determined)

Jena

Context Type: (to be determined)

LDAP

Context Type: (to be determined)

OpenID

Context Type: (to be determined)

XML File

Context Type: (to be determined)

Back to the top