Difference between revisions of "Template vocabulary"

Revision as of 20:41, 15 March 2011

Vocabulary to describe a Template Context. Contains information necessary to dynamically instantiate regular contexts. Imported by Persona vocabulary.

Files

• Most recently published
• SVN source: template.owl

Intro

A template context is pointed to by the p:template attribute of a regular context. The template context may be an instance of template:TemplateContext it may be an vanilla h:Context. If it is a TemplateContext then it has the contents described on this page.

Whether or not it is a TemplateContext or an h:Context the context instance itself may have a view-builder:viewRoot attribute (see View-builder vocabulary) and/or an app-data:app-data attribute.

UML Overview

Classes

TemplateContext

A template contains control information necessary to instantiate and control regular context instances.

• 0..1 app-data:appData - provides a "template" for the AppData object within a dynamically created AppDataContext (see App-data vocabulary)
• 1..1 authNMaterialsType
• 1..1 contextType
• 1..1 templateRole
• 0..1 udiMetadata

UDIMetadata

A set of attribute/values that, taken together, are considered the "metadata" for the XRDS service endpoint. See http://www.azigo.com/udi/udi-resolution.html#anchor3 for an example.

Attributes

authNMaterialsType

Type of authentication materials required to open this context.

• domain: TemplateContext
• value: string, one of {"urn:udi:authnmaterials:1.0:usernamePassword"}

contextType

The type of context endpoint to instantiate from this template. This corresponds to the value of the <Type> element in XRDS resolution (see http://www.azigo.com/udi/udi-resolution.html).

• domain: TemplateContext
• value: string, one of {"$context$sparql" , "$context$xdi"}

templateRole

The default role that p:Person nodes should inherit when dynamically created with contexts controlled by on this template

• domain: TemplateContext
• value: persona:Role

udiMetadata

UDIMetadata instance

Example

Here is a sample TemplateContext. It contains all of the metadata necessary to dynamically create the UDI service endpoint shown in this sample XRDS discovery document.

<http://org.eclipse.higgins.ontology.examples/template-example>
     rdf:type owl:Ontology , template:TemplateContext ;
     app-data:appData :AppData_1 ;
     higgins:vocabulary <http://www.eclipse.org/higgins/ontologies/2010/6/persona> ;
     template:authNMaterialsType
             "urn:udi:authnmaterials:1.0:usernamePassword"^^xsd:string ;
     template:contextType
             "$context$xdi"^^xsd:string ;
     template:udiMetadata
             :UDIMetadata_1 ;
     owl:imports <http://www.eclipse.org/higgins/ontologies/2010/6/persona> .

:AppData_1
     rdf:type app-data:AppData ;
     app-data:appId "1024"^^xsd:string ;
     app-data:description
             "A wonderful app"^^xsd:string ;
     app-data:serviceType
             "kynetx"^^xsd:string ;
     app-data:serviceURL "http://kynetx.com/appServer"^^xsd:anyURI ;
     app-data:version "2.4"^^xsd:string .

:UDIMetadata_1
     rdf:type template:UDIMetadata ;
     :address "ldap://ldap.company.net:389"^^xsd:string ;
     :connectionType "LDAP"^^xsd:string . 

:address
     rdf:type owl:DatatypeProperty ;
     rdfs:domain template:UDIMetadata ;
     rdfs:range xsd:string .

:connectionType
     rdf:type owl:DatatypeProperty ;
     rdfs:domain template:UDIMetadata ;
     rdfs:range xsd:string .

Or visually:

Notes:

1. userUpdateable attribute not shown above

Links

• Persona Data Model 2.0