Link Type Hints
It was proposed off line recently that we can extend the link types resource to include information about what rdf:type(s) are expected on either end of a link. While not restrictive this information could be used by clients in user interfaces to suggest appropriate link types when a source resource is in context. When selecting the target end of a link it might be used to provide additional filtering (if not using delegated UI and using OSLC simple query instead).
The proposal is that we allow two new properties on a link type resource;
oslc_am:sourceHint
and
oslc_am:targetHint
. These are multivalued properties that reference rdf:type URIs that can be expected on either end of a link with that type.
The motivation is to 1) provide service implementer UIs with an oppertunity to short list link types when presenting options to a user creating a new link type. 2) provide clients with some expectation as to what types of resource can be found on the other end of a link.
The proposed extended link type resource is:
Resource: Link Type Resource (LTR)[extended]
A Link Type Resource (LTR) represents type of link that is or can be used when defining links from AM resources. The type has an ID (expressed as a URI), whose universally accepted semantics may be defined elsewhere. This resource represents the definition as it is used by this service provider. This resource is meant as a convenience for clients to get a list of known/registered link types with human readable labels and definitions that can be used in client user interfaces when links are being created.
- Name:
LinkType
- Type URI
http://open-services.net/ns/am#LinkType
Prefixed Name |
Occurs |
Read-only |
Value-type |
Represen-tation |
Range |
Description |
dcterms:title |
exactly-one |
unspecified |
XMLLiteral |
n/a |
n/a |
Title (reference: Dublin Core) of the resource represented as rich text in XHTML content. Short name identifying a resource, often used as an abbreviated identifier for presentation to end-users. SHOULD include only content that is valid inside an XHTML <span> element. |
dcterms:identifier |
exactly-one |
unspecified |
String |
n/a |
n/a |
A unique identifier for a resource. Assigned by the service provider when a resource is created. Not intended for end-user display. |
dcterms:description |
zero-or-one |
unspecified |
XMLLiteral |
n/a |
n/a |
Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML <div> element. |
oslc_am:sourceHint |
zero-or-many |
unspecified |
Resource |
Reference |
any |
An expected, or at least possible resource type that a client might expect to see on the owning end (RDF subject) of an instance of this link type. |
oslc_am:targetHint |
zero-or-many |
unspecified |
Resource |
Reference |
any |
An expected or at least possible resource type that a client might expect to see on the target end (RDF object) of an instance of this link type. |
dcterms:creator |
zero-or-many |
unspecified |
Resource |
Either |
any |
Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case. |
dcterms:contributor |
zero-or-many |
unspecified |
Resource |
Either |
any |
Constributor or contributors of resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case. |
dcterms:created |
zero-or-one |
True |
DateTime |
n/a |
n/a |
Timestamp of resource creation (reference: Dublin Core). |
dcterms:modified |
zero-or-one |
True |
DateTime |
n/a |
n/a |
Timestamp last latest resource modification (reference: Dublin Core). |
oslc:serviceProvider |
zero-or-many |
unspecified |
Resource |
Reference |
oslc:ServiceProvider |
The scope of a resource is a URI for the resource's OSLC Service Provider. |
oslc:instanceShape |
zero-or-one |
unspecified |
Resource |
Reference |
oslc:ResourceShape |
Resource Shape that provides hints as to resource property value-types and allowed values. |
AM Service Provider Capabilities
Topic revision: r2 - 19 Jan 2011 - 18:03:41 -
JimConallen