This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Date: Thursday, 23 June 2011
Time: 11:00 AM Eastern
Contact Gili Mendel if you'd like to participate.

Agenda

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
Topic revision: r2 - 28 Jun 2011 - 13:57:05 - SheehanAnderson
 
This site is powered by the TWiki collaboration platform Copyright � 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 this site? Send feedback