-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples on openingHours should not use the 'time' element #143
Comments
I had a chat with Hixie about possibly getting HTML updated to allow this, if/when we get this micro-notation properly spec'd. But for now, I agree, time element is in-apropes. |
Another nudge that we should address this. https://twitter.com/Nettsentrisk/status/574859464316219392 I'd suggest:
|
This needs doing, but bumping one more milestone. Here's a grep of what's in the examples:
Are the P1Y values legit? i.e. 1 year ? |
/cc @chaals |
@unor looking at #533 (via #1012 which reminds us that http://schema.org/openingHours syntax isn't appropriate for 'time' element), it looks like your fixes don't directly address this problem. Am I missing something? |
Ah, then I misunderstood your comment in #1012 - just wanted to make sure I wasn't overlooking an existing fix |
The 'data' element was suggested
These both say "When the value is date- or time-related, the more specific time element can be used instead." which more or less advocates for the current usage of 'time'. Except the actual definition of 'time' isn't so broad and our usage is not currently a good fit. So my suggestion is:
|
+1 RDFa was simpler in that aspect with a separate datatype mechanism and the choice of arbitrary HTML elements for any kind of data ;-) Martin
|
Here is a list of every line from an examples*.txt file that contains "<time": |
…time attribute otherwise. Fixes ##143
Note that our use of @content goes beyond official Microdata, but this is already heavily done across schema.org and needs exploration elsewhere.
Restoring fixes to #143 to avoid openingHours on <time>.
Published - see http://schema.org/docs/releases.html |
http://schema.org/openingHours
The examples on
openingHours
use HTML5’stime
element:The values "Tu,Th 16:00-20:00" and "Mo-Su" don’t seem to be valid according to W3C’s HTML5 or according to WHATWG’s HTML.
The examples on
LocalBusiness
use themeta
element instead, which seems to be appropriate. Thedata
element might also be an appropriate alternative.The text was updated successfully, but these errors were encountered: