- From: Web Schemas TF Issue Tracker <sysbot+tracker@w3.org>
- Date: Fri, 20 Apr 2012 14:10:05 +0000
- To: public-vocabs@w3.org
webschema-ISSUE-14 (boolean values): Schema.org booleans (True/False) vs RDF 'true/false' [Feedback on Schema.org] http://www.w3.org/2011/webschema/track/issues/14 Raised by: Dan Brickley On product: Feedback on Schema.org >From Martin Hepp in https://docs.google.com/document/pub?id=1Kx63gW9DBky1j97Jpwl3dU9k0pKPSgCT3EntTVvGjX4 You have to clarify the usage of http://schema.org/Boolean. The schema.org sponsors should clarify whether to use the RDF-compatible text (true/false) or the URIs http://schema.org/True and http://schema.org/False. For now, one would assume that you use the two values as individuals, e.g. <link itemprop=”propertyname” href=”http://schema.org/True” /> <link itemprop=”propertyname” href=”http://schema.org/False” /> which is incompatible with the RDFa patterns and also less concise. I suggest <meta itemprop=”propertyname” content=”true” > <meta itemprop=”propertyname” content=”false” > Proposed change: A simple text amendment for http://schema.org/True, http://schema.org/False, and http://schema.org/Boolean would do the trick.: Note: The recommended use of this datatype is with a string “true” or “false” indicating the value of the respective property. Example: <div itemscope itemtype="http://schema.org/Book"> <span itemprop="name">The Catcher in the Rye</span> Family-friendly: <meta itemprop="isFamilyFriendly" content="true"> yes </div> Proposed action: Add this note to http://schema.org/Boolean
Received on Friday, 20 April 2012 14:10:11 UTC