- From: Ed Summers <ehs@pobox.com>
- Date: Wed, 9 Oct 2013 10:31:12 -0400
- To: Dan Brickley <danbri@google.com>
- Cc: jean delahousse <delahousse.jean@gmail.com>, Guha <guha@google.com>, Thad Guidry <thadguidry@gmail.com>, Aaron Bradley <aaranged@gmail.com>, Bernard Vatant <bernard.vatant@mondeca.com>, PublicVocabs <public-vocabs@w3.org>
On Wed, Oct 9, 2013 at 10:20 AM, Dan Brickley <danbri@google.com> wrote: > Merely saying that a property expects an URL doesn't really cut it, > since most non-literal-valued properties can usefully take URLs... Can you (briefly) describe how it doesn't "cut it" to allow something like schema:occupationalCategory to point at a resource using a URL? //Ed
Received on Wednesday, 9 October 2013 14:31:40 UTC