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
>
AssetMgMeetings31Jan2012
(01 Feb 2012,
SheehanAnderson
)
(raw view)
Date: Tuesday, 31 January 2012<br />Time: 1:00 PM EDT<br />Contact [[GiliMendel][Gili Mendel]] if you'd like to participate. ---++++ *Agenda* * Discuss proposal to change artifacts from a blank node within the asset resource to a fragment within the asset resource * Making the asset management specification compatible with hardware and software assets * Changes made * Added an 'Identifier' property that occurs 0-or-one times * Changed the occurs of the 'GUID' and 'Version' properties from exactly-one to zero-or-one * Proposed changes * <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">Add the following properties with an occurs of zero-or-one times: Serial Number, Model Number, and Manufacturer</font></font> * <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">Questions</font></font> * <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><font size="2">Should these new properties be merged into the asset management specification or should the concept of a common parent specification (asset management) with child sub-specifications (sofware assets and hardware assets) be considered? </font></font> * Review Rational Asset Manager specification implementation ---++++ *Notes from Meeting* Minutes: * Artifact as a fragment * No objections to this change * Samples have been updated * Combining hardware and software assets * Two options * 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> * <font size="2"><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">Options need further discussion</font></font> * <font size="2"><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">Rational Asset Manager Implementation of specification</font></font> * <font size="2"><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">The output should be full rdf/xml for the asset resource. Other resources (such as service provider) will use abbreviated rdf/xml </font></font> Action Items: * Sheehan * Schedule meeting next week to continue discussion on combining the hardware and software asset resources. ---++++ *Attendees* __IBM__ * Eric Bordeau * Gili Mendel * Michael Fiedler * Sheehan Anderson * Sri Gunturi
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r4 - 01 Feb 2012 - 19:05:56 -
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