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
.
TWiki
>
Main Web
>
AssetHome
>
AssetMgMeetings
>
AssetMgMeetings7Feb2012
(07 Feb 2012,
SheehanAnderson
)
(raw view)
Date: Tuesday, 7 February 2012<br />Time: 1:00 PM EDT<br />Contact [[GiliMendel][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 <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">common parent specification (asset management) with child sub-specifications (software assets and hardware assets)</font></font> * <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">Pros: Separates properties that may only be valid for software assets<br /></font></font> * <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">Cons: More difficult to implement, discourages integration between providers that manage software or hardware assets </font></font> * 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
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r3 - 07 Feb 2012 - 20:04:59 -
SheehanAnderson
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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