Agenda

• Discuss 2.0 supporting documents
  • Review updated OSLC Asset Management 2.0 Use Case
• Review updates to the asset resource specification.
  • Discuss artifact representation in an asset resource.
  • Discuss relationship representation in an asset resource.
  • How do we include properties defined within a rdf:Description tag? See relationships for an example.

Notes from Meeting

Minutes:

• Harirajan suggested that the supporting documents should contain code samples. For example, how does a Java developer work with the OSLC specification? Are there suggested libraries that they should be using?
  • Some of the code samples should probably be part of the core specification as they would be common across all OSLC specs.
  • The asset management specification should provide links to examples in the core and the Eclipse Lyo project.
• Artifact representation
  • Artifacts should be represented as a blank node in the asset resource. The owner of the artifact (including when the artifact is deleted) should be left up to the provider.
• Related asset representation
  • Related assets should be represented using reification as was previously decided.
  • We need to determine how to represent the reified statement in the specification table.

Action Items:

• Sheehan
  • Update artifact representation to use blank nodes.
  • Continue updating related asset representation.
  • Check if any other OSLC specifications have included code samples or if this idea has been discussed in the past.

Attendees

IBM

• Eric Bordeau
• Harirajan Padmanabhan
• Kevin Bauer
• Sheehan Anderson