- From: Greg Billock <gbillock@google.com>
- Date: Mon, 9 Apr 2012 21:09:39 -0700
- To: James Hawkins <jhawkins@chromium.org>
- Cc: Jason Douglas <jasondouglas@google.com>, WebIntents <public-web-intents@w3.org>
Yes, and we definitely want to match usage with microdata [1]. There types are URLs, and it'll be a big win to have them match. [1] http://dev.w3.org/html5/md-LC/#typed-items On Mon, Apr 9, 2012 at 8:01 PM, James Hawkins <jhawkins@chromium.org> wrote: > Thanks for the spot; I do believe it's just an oversight which we'll get > fixed. > > Thanks, > James > > > On Mon, Apr 9, 2012 at 5:12 PM, Jason Douglas <jasondouglas@google.com> > wrote: >> >> >>> A type string of "schema.org/Person " parses as the single string >>> literal "schema.org/Person" -- the whitespace is treated as >>> demarcating empty types, but since there is a non-empty type in the >>> list, the parsed type list is ["schema.org/Person"]. >> >> >> I find it a bit confusing that this is not a URL >> (http://schema.org/Person) given that that's how it always appears "in the >> wild" in markup. It's not clear to me whether that changes anything in the >> proposal itself since it's a string literal, but in order to match, everyone >> needs to be using the same form. >> >> -jason > >
Received on Tuesday, 10 April 2012 04:10:07 UTC