Agenda

• Updated Item: Asset Management Specification V2.
  • Many updates have been made to the V2 specification based on Dave Johnson's review. There are several items to discuss.
  • Can we drop the relation resource and use and address the issue via OSLC Core Link Guidance (http://open-services.net/bin/view/Main/OslcCoreSpecAppendixLinks) and reification?
  • Is it possible to reduce the number of required properties in the asset resource?
  • Should states, types, and category properties defined in the asset resource be their own resource? What does a category string look like?
  • Which delegated user interfaces must providers support?

Notes from Meeting

Minutes

• Required properties
  • The following properties will be required for an asset resource. All other properties are optional
    • Title
    • RAS ID
    • Artifact Factory (not required to post/put an asset)
• The following asset resource properties should be of type resource with a range of any. Generally the specification should try to avoid string propties and always use a resource.
  • State
  • Type
  • Category
• Delegated UI
  • For an asset resource, selection should be changed from "MUST" to "Should" and creation will remain "MAY".
• Relationship Resource
  • Instead of creating separate resources for relationships, we should use reification to include the relationship description within the asset resource.
  • <oslc_asset:relatedAsset rdf:ID=”n1” rdf:resource=”http://example.com/assets/451/” />

Action Items:

• Sheehan
  • Update relationship specification/samples to use reification.
  • Update required properties in the asset specification.
  • Update property types and ranges where necessary.
  • Update asset samples to match specification.

Attendees

IBM

• Dave Johnson
• David Hodges
• Kevin Bauer
• Sheehan Anderson
• Sri Gunturi