- From: Annette Greiner <amgreiner@lbl.gov>
- Date: Tue, 3 May 2016 10:29:18 -0700
- To: public-dwbp-wg@w3.org
- Message-ID: <f8fd7d09-b203-7796-4ed1-6996f0bbfee4@lbl.gov>
Thanks for doing this, Deirdre! I like the geoJSON idea, too. I'm just realizing that we won't be able to set up a real API at our example domain, because it's an example domain, which is by definition a place where we can't really have content. I was hoping for the documentation that we could use Swagger, because that is becoming a best practice already. I'd also like to see the URIs follow a more typical REST pattern. GET http://data.mycity.example.com/transport/api/bus/stops GET http://data.mycity.example.com/transport/api/bus/stops/11 GET . http://data.mycity.example.com/transport/api/bus/routes GET http://data.mycity.example.com/transport/api/bus/routes/5 Cheers, -Annette On 5/3/16 8:35 AM, Deirdre Lee wrote: > |Hi, > > I've created an example that can be used for the API BPs| > > |Best Practice 21: Provide real-time access | > |Best Practice 23: Make data available through an API| > |Best Practice 24: Use Web Standards as the foundation of APIs| > |Best Practice 25: Provide complete documentation for your API| > > | > https://www.w3.org/2013/dwbp/wiki/Api_example > | > > |GET /bus/routes| > |GET /bus/stops| > |GET /bus/realtime| > || > > | > For 'GET /bus/stops', I've used three different ways to describe > bus-stops: > | > > * |using simple fields, | > * |using fields defined in > http://w3c.github.io/dwbp/dwbp-example.html and | > * |using geojson to describe lat/long.| > > |We should pick one approach. I think the third - simple fields and > geojson. > | > > |What do you think? > | > > |Cheers, > Deirdre > | > > -- > ------------------------------------ > Deirdre Lee, CEO & Founder > Derilinx - Linked & Open Data Solutions > > Web:www.derilinx.com > Email:deirdre@derilinx.com > Address: 11/12 Baggot Court, Dublin 2, D02 F891 > Tel: +353 (0)1 254 4316 > Mob: +353 (0)87 417 2318 > Linkedin: ie.linkedin.com/in/leedeirdre/ > Twitter: @deirdrelee -- Annette Greiner NERSC Data and Analytics Services Lawrence Berkeley National Laboratory
Received on Tuesday, 3 May 2016 17:29:37 UTC