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
>
AssetMgMeetings23June2011
(28 Jun 2011,
SheehanAnderson
)
(raw view)
Date: Thursday, 23 June 2011<br />Time: 11:00 AM Eastern<br />Contact [[GiliMendel][Gili Mendel]] if you'd like to participate. ---++++ *Agenda* * Updated Item: [[http://open-services.net/bin/view/Main/AssetMgSpecificationV2][Asset Management Specification V2]]. * Many updates have been made to the V2 specification based on Dave Johnson's review. There are several items to discuss. * Can we drop the relation resource and use and address the issue via OSLC Core Link Guidance (http://open-services.net/bin/view/Main/OslcCoreSpecAppendixLinks) and reification? * Is it possible to reduce the number of required properties in the [[http://open-services.net/bin/view/Main/AssetMgSpecificationV2#Asset][asset resource]]? * Should states, types, and category properties defined in the [[http://open-services.net/bin/view/Main/AssetMgSpecificationV2#Asset][asset resource]] be their own resource? What does a category string look like? * Which [[http://open-services.net/bin/view/Main/AssetMgSpecificationV2#Delegated_User_Interface_Dialogs][delegated user interfaces]] must providers support? ---++++ *Notes from Meeting* Minutes * Required properties * The following properties will be required for an asset resource. All other properties are optional * Title * RAS ID * Artifact Factory (not required to post/put an asset) * The following asset resource properties should be of type resource with a range of any. Generally the specification should try to avoid string propties and always use a resource. * State * Type * Category * Delegated UI * For an asset resource, selection should be changed from "MUST" to "Should" and creation will remain "MAY". * Relationship Resource * Instead of creating separate resources for relationships, we should use reification to include the relationship description within the asset resource. * <oslc_asset:relatedAsset rdf:ID=”n1” rdf:resource=”http://example.com/assets/451/” /> Action Items: * Sheehan * Update relationship specification/samples to use reification. * Update required properties in the asset specification. * Update property types and ranges where necessary. * Update asset samples to match specification. ---++++ *Attendees* __IBM__ * Dave Johnson * David Hodges * Kevin Bauer * Sheehan Anderson * Sri Gunturi
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 28 Jun 2011 - 13:57:05 -
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