Re: [web-nfc] URL objects

> We agree, for URL's, data is always a url-string. The discussion is 
whether
> * type = "text/uri-list" (MIME type), or "url" (our invented value 
for this)
> * or we add a new property kind = "url" (invented value) and type is
 irrelevant for URL (for types other than URL it contains the MIME 
type).

I don't care strongly. Though mimetypes are generally a pretty crappy 
way of exposing types. For exactly this reason. Lots of stuff doesn't 
have a mimetype. And lots of things have several different mimetypes.

>From a security point of view I think we can expose the low-level 
information once we know that a tag has opted in to being "secure to 
expose to the web". At least for reading.

-- 
GitHub Notif of comment by sicking
See https://github.com/w3c/web-nfc/issues/26#issuecomment-130520500

Received on Thursday, 13 August 2015 03:39:20 UTC