Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "App-data vocabulary"
(→Example AppData) |
(→Attributes of a Person node within the context) |
||
| Line 100: | Line 100: | ||
* value: string | * value: string | ||
| − | == | + | == Related Person attributes == |
| − | + | As we've mentioned, an AppData instance is the value of an appData attribute of a TemplateContext. For example we might have AppData1 as the value of appData on TemplateContext TC1. A context, C1, might be based on TC1. Within C1 usually exists a Person node. The following attribute are optional attributes of this Person node. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | === | + | === enabledSites === |
| − | The URLs of sites that the user has | + | The URLs of sites that the user has enabled the app to run on. Note that this augments the appSites value provided by the app developer which indicates the set of sites the app was designed to run on. |
| − | + | * value: boolean | |
| − | *value: | + | |
| − | === | + | === disabledSites === |
| − | If true | + | The URLs of sites that the user has disabled the app from running on. |
| + | * value: xsd:anyURI | ||
| + | |||
| + | === appEnabled === | ||
| + | If true run this app | ||
| − | |||
* value: xsd:anyURI | * value: xsd:anyURI | ||
Revision as of 09:07, 7 August 2011
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Vocabulary for describing an AppData object. An AppData is the value of an appData attribute of a TemplateContext. An AppData and its sub-objects represent the (i) app-related attributes of the person entity and (ii) the metadata and parameters needed for the app itself. Part of the Persona Data Model 2.0
Contents
Files
- Most recently published
- SVN source: app-data.owl
UML Overview
Classes
AppData
Description of an app
- 1..1 description
- 1..1 version
- 1..1 eventHandlerURL
- 1..1 adminURL
- 1..1 serviceType
- 1..1 serviceURL
- 0..1 params
- 0..N hbxFunctionsEnabled
- 0..N sites
- 0..N entityParam
AppParams
An AppParams instance is the value of an AppData's params attribute. It is a set of attributes and values used to initialize the app. Note: these attribute/values are combined with those derived from the AppData's entityParam.
AppData Attributes
adminURL
The URL of a admin page to load into PDS portal.
- domain: AppData
- value: xsd:anyURI
appId
Uniquely identifies the app within the "developerId" namespace. In other words the combination of the devID and the appId is globally unique. When using Kynetx KNS this is the ruleID with special constraint that this ruleID is globally unique.
- domain: AppData
- value: string
description
A human readable description of the app. Note: If appServer == http(s)://init.kobj.net, then the KNS "describe" API can be used by a context provider implementation to provide this attribute value.
- domain: AppData
- value: string
entityParam
The name of an attribute (e.g. p:postal-code) of a Person within a context associated with this App-data object. The value of this named attribute of the person is used as a parameter to the app-card's app.
- domain: AppData
- value: URI
eventHandlerURL
The URL of JS that provides specific handlers for certain events in a context’s lifecycle including: onImport, onDelete, onEnable, onDisable, onExport
- domain: AppData
- value: URI
hbxFunctionsEnabled
The list of HBX functions that the JS functions associated with this app-data are allowed to call.
- domain: AppData
- value: string one of: {"delExAttrbutes" , "getExAttributes" , "getSuggestions" , "setExAttributes"}
params
A set of attributes used to initialize the app.
- domain: AppData
- value: AppParams
serviceURL
The URL of the JS to fetch and execute.
- domain: AppData
- value: URI
serviceType
If value is "kynetx" then the browser extension that will inject the Javascript for this app-card should construct a Kynetx-compatible <script> block and call an initialization URL based on the value of the appService attribute.
- domain: AppData
- value: string whose value is one of ("kynetx", "higgins").
sites
This is not a list of specific URIs, it is a list of strings to match in the domain name part of a URI. So urn:google would fire on maps.google.com, www.google.com, www.googleismyfavoritesite.com. For Kynetx-powered cards (i.e. if appServer = http[s]://init.kobj.net"), the values of this attribute should be dynamically fetched using the 'dispatch' method at URL: [1]<appId>.
- domain: AppData
- value: string
version
A human readable version of the app. Note: If appServer == http(s)://init.kobj.net, then the Kynetx KNS "describe" API can be used by a context Provider implementation to provide this attribute value.
- domain: AppData
- value: string
Related Person attributes
As we've mentioned, an AppData instance is the value of an appData attribute of a TemplateContext. For example we might have AppData1 as the value of appData on TemplateContext TC1. A context, C1, might be based on TC1. Within C1 usually exists a Person node. The following attribute are optional attributes of this Person node.
enabledSites
The URLs of sites that the user has enabled the app to run on. Note that this augments the appSites value provided by the app developer which indicates the set of sites the app was designed to run on.
- value: boolean
disabledSites
The URLs of sites that the user has disabled the app from running on.
- value: xsd:anyURI
appEnabled
If true run this app
- value: xsd:anyURI
Example AppData
Example of an AppData context:
Shown above is an example TemplateContext with an associated AppData object. Also within this context is an entity, 'me'.
Notes:
- Of particular interest is the app-card:params attribute whose value is the AppParams_1 object. The AppParams_1 in turn has two app initialization attributes, randomAttribute1 and 2.
- Since "appEnabled" = true attribute/value is not present on 'me' its value is assumed to be false and the card is thus disabled at present.
Processing Model
Invoking Javascript
The Higgins browser extension is responsible for invoking the app/Javascript for all app-data contexts. This is done three ways. If appJS is not nil, then its value IS the app to invoke. If the appJS is nil, then the appServiceType indicates whether a Kynetx-style KNS invocation should be done or an (as yet undefined) Azigo-style invocation from some Azigo-hosted web service should be done. In the above example the appServiceType = kynetx so a KNS invocation will be done.
App/rule Id parameter
In the non-appJS (i.e. kynetx and/or azigo cases) the appId is required to specify which app (Javascript program) should be run. In the above example the appId (called a rule id by KNS) is "1024".
Before the Javascript is invoked on a given Web page HBX must determine for each AppDataContext if the current page is one that matches one or more card's site list.
Gather parameters to the Javascript
The browser extension and supporting code must implement the following algorithm to gather all necessary parameters to the Javascript function:
- Get the value of all attributes of the entity of the "appParams" attribute of the context object (ignoring rdfs:comment, rdf:label attributes, rdf:type, etc.).
- Get the value of all attributes of the main p:Person entity that are named in the context object's entityParam attribute value(s).
Making parameters/values available to the app (Javascript)
How parameters are inserted varies by service type. Here is how it is done for a "kynetx" serviceType:
var KOBJ_config ={
"rids" : ["1024","xyz123"],
"1024:dataset" : "aaawa",
"1024:dataset" : "ebates",
"1024:favorite-song" : "Billy Joel: The Piano Man",
};This tells kynetx to run rules 1024 and xyz123, and for rule 1024, use dataset=aaawa and dataset=ebates. Note that each appParam value is namespaced by the appId (aka rule id, or rid) to which it is associated.