Changes between Version 57 and Version 58 of DASISH/SpecificationDocument
- Timestamp:
- 06/10/13 15:53:41 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DASISH/SpecificationDocument
v57 v58 90 90 All information necessary to fulfill a PUT, POST or DELETE request, such as the URI of an annotated object, is given “serialized” in the request body, but not as request parameters in the request’s URI. If a POST (PUT, DELETE) method is performed, then in the case of success it returns a serialized information about the added (resp. updated, removed) resource together with a standard HTTP response code. The information includes: the resource ID, owner’s ID, time stamp, (possibly) the list of the <sid>’s of the target sources. For the full information the user will use GET on a just created/ updated annotation, already knowing its ID. In the case of failure the corresponding error message and error status are returned, e. g, 401 Unauthorized access. Only “owner” has DELETE rights. 91 91 92 For now in this document the descriptions of the requests below often refer to the corresponding descriptions on the [[Scenario# | Scenario wiki-page]]. It will be the other way around, i.e. the Scenario will refer to this specification document after projecting stabilizes. 93 92 94 == User realm == 93 95 94 96 ||= '''Resource''' =||= '''Description''' =|| 95 ||{{{GET api/users/uid}}} || see [[Scenario#Authentication ]]||96 ||{{{ GET api/users/info?email=<...>}}} || see [[Scenario#Managingpermissionlistsofusers ]] ||97 ||{{{GET api/users/uid}}} || see [[Scenario#Authentication | the description in Scenario ]]|| 98 ||{{{ GET api/users/info?email=<...>}}} || see [[Scenario#Managingpermissionlistsofusers | See the description in Scenario]] || 97 99 == Annotations == 98 100