- From: Wallis,Richard <Richard.Wallis@oclc.org>
- Date: Wed, 18 Jun 2014 14:51:20 +0000
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- CC: "<public-vocabs@w3.org>" <public-vocabs@w3.org>
>From my experience it is easier to get your head around/discuss examples in Turtle and then referring to the RDFa/JSON-LD/Microdata see how it would be then be implemented. I’ve been thinking about suggesting an optional Turtle tab for a while - so I am now. ~Richard On 18 Jun 2014, at 15:44, Markus Lanthaler <markus.lanthaler@gmx.net> wrote: > On 18 Jun 2014 at 15:26, Dan Brickley wrote: >> On 18 June 2014 14:15, Antoine Isaac <aisaac@few.vu.nl> wrote: >>> Does this include *real* licenses URIs like >>> http://creativecommons.org/licenses/by/4.0/ >>> ? >> >> Like in the last example in http://schema.org/WebPage ? :) >> >> (I realise readers don't know what is in each example 'tab' until they >> look... maybe we could improve that) > > I think the problem is, that it is very hard to "see" what data is in the default's tab (without markup) blob of text. It's almost impossible to skim it. I'm not sure whether schema.org wants to go down that route, but I think even for people that have no idea about how JSON-LD works (or even what it is), it is much easier to skim and understand. So perhaps that easiest tweak would be to show the JSON-LD tab by default!? > > > -- > Markus Lanthaler > @markuslanthaler > >
Received on Wednesday, 18 June 2014 14:51:52 UTC