Date: Tuesday, 7 February 2012
Time: 1:00 PM EDT
Contact
Gili Mendel if you'd like to participate.
Agenda
- In the Asset resource dcterms:title should be changed to rdfs:label
- What about artifacts which already have both a title and label?
- 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:
- dcterms:title vs rdfs:label
- Continue using dcterms:title in version 2 of the specification to maintain consistency with the other version 2 specifications that have already been released
- Combining hardware assets and software asset
- Include additional hardware asset properties within the asset specification
- In the future, sub-specifications can be created if needed
- Include a paragraph describing the differences between hardware assets and software assets
- Include a use case for hardware assets
- Update the specification to refer to both hardware and software assets where needed
- Reducing the number of relationship properties
- Still undecided. Will be setting up a meeting with Steve Speicher to further discuss this topic
Action Items:
- Gili Mendel
- Setup meeting with Steve Speicher to discuss relationship definitions in version 2 of the specification
- Jacob Yackenovich
- Review asset management specification and provide text describing hardware assets where needed
- Provide use case for hardware assets
- Sheehan Anderson
- Update specifications with new properties for hardware assets
- Incorporate changes suggested by Jacob after his review
Attendees
IBM
- Eric Bordeau
- Gili Mendel
- Jacob Yackenovich
- John Arwe
- Sheehan Anderson
- Sri Gunturi
- Tuan Dang