Changes between Version 58 and Version 59 of DASISH/Scenario


Ignore:
Timestamp:
05/15/13 14:28:41 (11 years ago)
Author:
olhsha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DASISH/Scenario

    v58 v59  
    2525See [[XSD and XML#RespondingGETapiannotationslinkhttp:en.wikipedia.orgwikiSagrada_FamC3ADliaaccessread | Example: getting annotations for Sagrada Famiglia wiki-page]]
    2626
    27 * Client: Resolving fragments (mapping) happens after the response. There are two internal lists for the client: the resolvable and unresolvable targets.
    28 
    29 QUESTION 1: How to signalise a client that certain sources are not resolved? To send the list of not-resolved targets in the respond? To make an envelope for GET as well?
     27If the client  cannot fit annotated fragments into the current version of the document, the corresponding target source is called unresolved.  Unresolvability of a target source triggers the client-side workflow of getting a cached representation of the concerning version of the source.
    3028
    3129= Viewing an individual annotation =
     
    105103[[XSD and XML#GETapiusersinfoemailalecormpi.nl | Getting user info via his/her e-mail ]]
    106104
    107 QUESTION 2: what to do if no user with this e-mail is found, an http status "page not found" is returned? Or an envelope with the action PROVIDE_USER_INFO?
     105If a user with the given e-mail does not exists, status 404 is returned.
    108106
    109107