W3C home > Mailing lists > Public > public-nfc@w3.org > February 2015

Re: [nfc] Unclear definition of "URL scope"

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Feb 2015 23:35:19 +0000
To: public-nfc@w3.org
Message-ID: <issue_comment.created-73988688-1423697716-sysbot+gh@w3.org>
You can definitely define a small algorithm and use it from each 
algorithm, and you probably need to in order to define the error that 
happens when the URL found in an NDEF record doesn't match the web 
app's origin.

The definition is also just not clear. You have "The term URL scope 
.... [is] a sub-string match to the web app's document URL.", which 
doesn't really mean anything. Do you want to define "URL scope" as "a 
URL that is a sub-string of the web app's document URL"? But an NDEF 
record can contain any URL. I think you mean that an NDEF record is 
only exposed to an application if its identifier is a substring of the
 application's URL?

Also, "substring" isn't really right: 
`https://www.example.com/path?x=https://www.somethingelse.com` is a 
valid URL, but you don't want an NDEF record containing 
"https://www.somethingelse.com" to match that example.com application.

-- 
GitHub Notif of comment by jyasskin
See https://github.com/w3c/nfc/issues/69#issuecomment-73988688
Received on Wednesday, 11 February 2015 23:35:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 23:35:28 UTC