- From: elf Pavlik <perpetual-tripper@wwelves.org>
- Date: Thu, 10 Dec 2015 11:14:17 +0100
- To: public-schemaorg@w3.org
Hello, On Tuesday during my presentation at http://paris.apidays.io/ I mentioned schema.org on couple of slides and explained how it contributes to evolution of distributed read-only API and already starts moving towards read/write API with schema:Action and schema:target. I also entertained the idea that besides embedding JSON-LD in <script> tag of page HTML, publishers at some point possibly could also use link rel="alternate" type="application/ld+json". Either in HTML <head> or in HTTP header, example: http://www.slideshare.net/elfpavlik/api-standardization-work-in-w3c-groups/58 While for read-only APIs embedding in HTML makes a lot of sense, for RESTful read/write APIs people often want to have separate JSON endpoints anyways. Transclusion of JSON-LD response in HTML representation does add a little to each response, even that as of today most clients still ignore that structured information. On the other side, crawlers could very easily follow rel="alternate" links and still index structured data this way. I welcome feedback on this idea :) + Greetings from Paris o/
Received on Thursday, 10 December 2015 10:14:29 UTC