- From: Dan Brickley <danbri@danbri.org>
- Date: Thu, 12 Jul 2012 14:00:52 +0200
- To: Leigh Dodds <ld@talis.com>, Joshua Shinavier <josh@fortytwo.net>
- Cc: public-vocabs@w3.org
On 12 July 2012 12:38, Leigh Dodds <ld@talis.com> wrote: > On 12 July 2012 10:39, Joshua Shinavier <josh@fortytwo.net> wrote: >> ... >> On Thu, Jul 12, 2012 at 3:42 AM, Leigh Dodds <ld@talis.com> wrote: >>> I note that the table in the wiki refers to ds:license but this is not >>> called out anywhere. >> >> Currently, the idea is simply to point to a WebPage about the license, >> but I'm open to other suggestions. > > I think thats probably sufficient. Most licenses have a clear > destination page. Would be nice to have the property documented and an > example added. > >>> Does a generic license property apply to the >>> Dataset schema or is there a more general term? We should probably add this to the FAQ, as it crops up a lot: the schema.org project does not plan to get into the business of representing licenses or similar restrictions. There is some risk such properties would be misunderstood, as described http://lists.w3.org/Archives/Public/public-vocabs/2012May/0093.html ... excerpting: "We don't want schema.org's descriptive vocabulary to be misinterpreted by anyone as proscriptive, i.e. as something broadly like the http://www.robotstxt.org/ protocol - as a way of communicating with search service providers." I realise that describing license info is an important concern for many. Both RDFa and Microdata provide syntactic options for non-schema.org properties to be mixed in with schema.org-based descriptions. Alternatively, others (e.g. IPTC rNews and LRMI) have chosen to document usage patterns for properties which aren't officially documented at schema.org. I hope some similar compromise design can meet people's needs here. Dan
Received on Thursday, 12 July 2012 12:01:47 UTC