Agenda

• Combining hardware and software assets
  • Proposals
    • Include additional properties within the asset specification and include an appendix discussing the differences between hardware and software assets
      • Pros: Simple to implement, encourages integration between providers of software and hardware assets
      • Cons: May require providers to handle properties that are not necessary for the type of asset they are managing
    • Create common parent specification (asset management) with child sub-specifications (software assets and hardware assets)
      • Pros: Separates properties that may only be valid for software assets
        
      • Cons: More difficult to implement, discourages integration between providers that manage software or hardware assets
• Reducing the number of relationship properties
  • Proposals
    • Only include the dcterms:relation property. Other properties should be included under a non-oslc namespace
    • Reuse properties/namespaces from other specifications

Notes from Meeting

Minutes:

Action Items:

Attendees

IBM

• Eric Bordeau
• Gili Mendel
• Michael Fiedler
• Sheehan Anderson
• Sri Gunturi