(r4) AssetMgSpecificationIssueTracking < Main

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>AssetMgSpecificationIssueTracking (revision 4) (raw view)

---+ Asset Management Specification Issue Tracking

List of general comments or issues against the specification development for the Asset Management domain.

Spec comments being worked (Closure description included after each comment, with prefix %GREEN%CLOSED%ENDCOLOR%. If unresolved or spec needs to be updated, it will have a prefix of %RED%OPEN%ENDCOLOR% )
---++ OSLC-AssetManagement 1.0 Draft spec comments:

---+++ AssetMgSpecificationV1
   1 %RED%OPEN%ENDCOLOR% _Section comment applies to_ - Comment description. (WikiName of commenter 03/xx/2010) 
      * *Response* Comment or resolution (WikiName of resolver 03/xx/2010)

---+++ AssetMgRestApiV1
   1 %RED%OPEN%ENDCOLOR% _Get Resources_ - Query syntatx does not seem to provide the capability to included Asset relationship specefic atcivities. (EdwinFreekenhorst - 11 Mar 2010) 
      * *Response* Comment or resolution (GiliMendel 03/11/2010) V1 of the specs. only provides limited query capabilities.... we plan to tackle search next, where we include categories, relationships, tags, with results that denote relevance, available (next drill down) categories / tags etc.
   1 %RED%OPEN%ENDCOLOR% _Get an Artifact media Resource_ - Not clear what happens if the artifact resources is a URL. I.e. is the return value the URL itself or the content of the page pointed to by the URL. (Main.EdwinFreekenhorst - 11 Mar 2010) 
      * *Response* Comment or resolution (GiliMendel of resolver 03/11/2010) V1 of the spec. does not require caching of referenced resources. ... as we iterate on V2, this can be another property of the artifact property.
   1 %RED%OPEN%ENDCOLOR% _Update an Asset_ - HTTP response status codes not present for a "locked" asset. I.e. already being updated. (EdwinFreekenhorst - 11 Mar 2010) 
      * *Response* Comment or resolution (GiliMendel of resolver 03/11/2010) OSLC does not deal with implementation's collisions, transactions (e.g., adding a set of artifacts media .... a set of posts ... all or nothing). ... from the spec's point of view it is a put or a get ... atomic. In our implementation of this we tried to get away from "locks" as well, rather, we provide the means to use an update context as to allow a all or nothing kind of a function... 
---+++ AssetMgResourceDefinitionsV1
   1 %RED%OPEN%ENDCOLOR% _Section comment applies to_ - Comment description. (WikiName of commenter 03/xx/2010) 
      * *Response* Comment or resolution (WikiName of resolver 03/xx/2010)

---+++ AssetMgQuerySyntaxV1

   1 %RED%OPEN%ENDCOLOR% _Section comment applies to_ - Comment description. (WikiName of commenter 03/xx/2010) 
      * *Response* Comment or resolution (WikiName of resolver 03/xx/2010)

Topic revision: r4 - 11 Mar 2010 - 22:10:14 - GiliMendel

Main

Webs
Main
Sandbox
TWiki

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