- From: Bernadette Farias Lóscio <bfl@cin.ufpe.br>
- Date: Mon, 16 Nov 2015 08:59:59 -0300
- To: Annette Greiner <amgreiner@lbl.gov>
- Cc: Erik Wilde <erik.wilde@dret.net>, "public-dwbp-wg@w3.org" <public-dwbp-wg@w3.org>
- Message-ID: <CANx1PzxRhrfeCTMZ=Q1JL5jg2Lmq+f3SYLeqrod5i9FvO_eGDw@mail.gmail.com>
Hi Annette, I agree with you! I think using API is just one of the possible ways of publishing data on the Web. cheers, Bernadette 2015-11-13 20:02 GMT-03:00 Annette Greiner <amgreiner@lbl.gov>: > My reason for asking is that I think it's important to consider possible > use cases for doing something other than publishing an API. I realize it > doesn't meet your criteria for being "webby", but there are people who use > the web in other ways, and they may have good reason for doing so. I don't > want to be dismissive of them. > -Annette > > On 11/13/15 12:57 PM, Erik Wilde wrote: > >> On 2015-11-13 19:38, Annette Greiner wrote: >> >>> I would not recommend the use of SOAP to anyone these days. I do >>> recommend the use of REST principles, even in backends that are not set >>> up as an API per se, because they make it easy to add an API later. Is >>> it always a best practice to make an API available? I'm not sure. >>> >> >> well, if it's "data on the web" i'd assume at the very least there is >> some remote access in the overall picture, right? if that;s the case, then >> it can either be the FTP/SOAP-style "let's serve some files via whatever >> transport channel we have", in which case i'm not sure why the title even >> mentions the web, or it could be a way of doing this webby, in which case >> your data model is your API, essentially. >> >> cheers, >> >> dret. >> >> > -- > Annette Greiner > NERSC Data and Analytics Services > Lawrence Berkeley National Laboratory > > > -- Bernadette Farias Lóscio Centro de Informática Universidade Federal de Pernambuco - UFPE, Brazil ----------------------------------------------------------------------------
Received on Monday, 16 November 2015 12:00:47 UTC