r2 - 2015-10-14 - 00:29:27 - NickCrossleyYou are here: TWiki >  LinkedData Web > BestPractices > UseOfOSLCValueTypeAndRepresentation
This wiki: The development wiki is a work area where Jazz development teams plan and discuss technical designs and operations for the projects at Jazz.net. Work items often link to documents here. You are welcome to browse, follow along, and participate. Participation is what Jazz.net is all about! But please keep in mind that information here is "as is", unsupported, and may be outdated or inaccurate. For information on released products, consult IBM Knowledge Center, support tech notes, and the Jazz.net library. See also the Jazz.net Terms of Use.

New product names: The CE/CLM products were renamed in version 7.0. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio. Some content might continue to use the previous names or contain a combination of the previous and current names.

Best Practice: Use of OSLC Value Type and Representation in Resource Shapes

State: Valid until OSLC Core 3.0 published

Contact: Nick Crossley

Scope

The OSLC 2.0 Core specification defines two properties oslc:valueType and oslc:representation to describe the type and representation of property values. The wording of those two properties is not as precise as it could be, and the meaning of combinations of the two properties is not always clear.

Recommendation

Pending clarification with OSLC Core 3.0, this is how the resource value types should be used, and the corresponding representations:

Value Type Representation
Reference Inline Either
Resource A link to an RDF resource with a stable URI. The target RDF resource SHOULD NOT be contained within the same RDF graph or same http resource as the source resource; a client may expect to be able to GET this URI separately and independently from the source URI (and possibly PUT/POST to it). A link to an RDF resource with a stable URI, which might be a hash URI. The target MUST be contained within the same RDF graph or same http resource as the source resource. A link to an RDF resource with a stable URI, which might be a hash URI. The target RDF resource MAY be contained in the same graph or http resource as the source, so the GET of the source URI might also fetch the target resource.
LocalResource n/a A link to an RDF resource with a hash URI or blank node, The target MUST be contained within the same RDF graph or same http resource as the source resource. Clients MUST assume the resource is not separately fetchable or modifiable. n/a
AnyResource n/a A link to an RDF resource. The target MUST be contained within the same RDF graph or same http resource as the source resource. Clients MUST NOT make any assumptions about the nature of the URI for this resource. A link to a resource. The representation and location of the target is not defined. Clients MUST NOT make any assumptions about the nature of the URI for this resource.

See Also

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
LinkedData.UseOfOSLCValueTypeAndRepresentation moved from LinkedData.UseOfOSLCRepresentationAndValueType on 2015-10-14 - 00:24 by NickCrossley -
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding TWiki? Send feedback