Hi Thanks for the input. The introduction originally had wording specific to software assets, but we have purposefully made it more generic based on workgroup feedback. The issue is that an asset may have different meanings to different providers/consumers. Depending on who you ask an asset may be the final output from a software development process, physical hardware, final documentation, etc. The difference between an asset and "stuff" with "things" is that an asset has value (reference or reuse) across a broad audience and needs to be monitored or maintained.
I think you have a valid point about the introduction being hard to grasp on a first read and it would be useful for us to provide some short tangible examples. I'll write up both a software asset and hardware asset example so that the reader understands the benefits of assets/artifacts in concrete terms that fit into their domain. Thanks, Sheehan Anderson [email protected] -----Olivier Berger <[email protected]> wrote: ----- To: Sheehan Anderson/Durham/IBM@IBMUS, [email protected] From: Olivier Berger <[email protected]> Date: 04/04/2012 08:37AM Cc: [email protected] Subject: Re: [oslc-core] Specification finalization Hi. (I'm not subscribed to the oslc-assetmgmt list, so sorry sorry in advance if this has already been reported.) I think the introduction is far too generic for immediate understanding of the difference between "Asset", "Artifact" and "Media Resource". I'm probably a bit naive here, as I haven't followed prior developments of that spec, not do I have experience with asset management systems and likes. But I think that generally, such specs should be introductive enough to let casual engineers grok what this is about, even if the normative sections are of course meant for the specialists. I think an example, taken from an ALM/PLM use case would help a great deal, in this introduction. Of course the terminology is meant to refer to generic concepts, so the wording is probably accurate, but frankly, this doesn't convey much meaning for the "man in the street", IMHO (replace "asset" by "stuff" and "artifact" by "thing" and you don't diminish so much of its opacity, at first read ;). Depending on the intended audiance, my remark may be less relevant, of course. It seems that the Samples page provides an example of a Build use case. Maybe this would be a good candidate for an example diagram which translates the Asset, Artifact and Media entities in more concrete terms for a (software) engineer. Hope this helps, and otherwise, congrats for the good progress ;) Best regards, On Tue, 3 Apr 2012 15:51:53 -0600, Sheehan Anderson <[email protected]> wrote: > The OSLC Asset 2.0 specification is ready for finalization as we have met our > criteria of > a) Resolving all outstanding issues that have been reported > b) Completion of an implementation of the specification with feedback. > > We plan to finalize the specification in our next meeting on April 10th. The > finalization was not completed in our previous meeting as some members wanted > more time to review the specification and the implementation report needed to > be completed. Please take some time to review the following links and report > any issues on the wiki > (http://open-services.net/bin/view/Main/AssetMgSpecificationV2Issues) or the > OSLC Asset mailing list. > > Specification > http://open-services.net/bin/view/Main/AssetMgSpecificationV2 > > Samples > http://open-services.net/bin/view/Main/AssetMgSpecificationV2Samples > > Implementation Report / Implementation > http://open-services.net/bin/view/Main/AssetImplementationReports > https://jazz.net/wiki/bin/view/Main/RamV2RestApiMain > https://jazz.net/downloads/rational-asset-manager/releases/7.5.1.1 > > Vocabulary > http://open-services.net/bin/view/Main/AssetVocabulary > > Thanks, > Sheehan Anderson > [email protected] -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)
