Re: Type matching algorithm for web intents

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
>