On 18-01-15 11:32, Diego Bosc? wrote: > > You are not asking for a person, you are asking the server for a > specific document about a patient that does not exist. A server can > have records with identifiers 111, 112, 113, etc. which can be about > the same patient or not. If you ask the server for a inexistent > document identifier it gives you 404. Document identifier doesn't mean > patient identifier. >
I agree, using the HTTP-status is a tempting idea, because, it looks like we are requesting a document. But we aren't. REST is not for a normal document-service. For that a normal webserver is sufficient. REST is for giving a web-interface to an application, and I ask that application to create a document about a partyId, and that application creates the document with information: "This person is not in our system" That is not an error, the application gets a command to supply information about a person in context of that application, and the application does so. I think that is good. It sometimes happens that people are thinking in isolation. I know this can happen to me. I am then making a point of something no-one seems to make a point of. But regardless that risk, I have posted this question to several forums because I think this is important, and maybe I find support for my way of thinking. Bert > El 18/1/2015 11:21, "Bert Verhees" <bert.verhees at rosa.nl > <mailto:bert.verhees at rosa.nl>> escribi?: > > > https://developers.google.com/drive/web/handle-errors > > > This is exactly my point, 404 is for handling errors, someone not > being in a hospital-register is not an error. To check if someone > is, and he isn't, that is not necessarily an error. > It may even be a good thing, that someone never has been ill in a > specific hospital. > The only thing that a computer, without value judgment can say, is > that the call iss successful (HTTP-status 200), and the answer is > "No, he is not in the register". That is information. > > To call an non-existing service, that is an error, and should > return 404. That is what Restlet also has implemented. > > Bert > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > <mailto:openEHR-technical at lists.openehr.org> > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150118/27033f94/attachment.html>
