[OASIS Issue Tracker] (OSLCCCM-34) oslc_config:Activity does not provide a means to determine error(s)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63973#comment-63973 ] 

David Honey commented on OSLCCCM-34:
------------------------------------

While that helps, I'm not sure it is sufficient. You could have an operation complete with warnings. For example, instead of creating a global baseline, the result is a global baseline staging stream that contains a mixture of baseline staging streams (BSSs) and streams and baselines. So we need to represent both the new root BSS and a collection of errors for each failing configuration. We could provide an oslc:Error that was a summary of that error collection, but we also might want to return the URI of the new root BSS that was created. We cannot do that with a single dcterms:references. Perhaps we should keep dcterms:references to reference a newly created resource and use a separate predicate for any summary error or warning, and then an application can use private namespace predicates to provide a more detailed result, which might include a list iof failing configurations and their associated error/warning message.

> oslc_config:Activity does not provide a means to determine error(s)
> -------------------------------------------------------------------
>
>                 Key: OSLCCCM-34
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-34
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>            Assignee: Nick Crossley
>
> When a long running operation has completed with error(s), there is no way that a client can determine what errors occurred or what error message(s) ought to be shown to the requesting user by the client that initiated the request.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)