search

google / eddystone

Specification for Eddystone, an open beacon format from Google
Apache License 2.0
3.08k stars 762 forks source link

Eddystone-URL HTTP URL encoding duplicates expansion values #55

Closed alexvanboxel closed 9 years ago

alexvanboxel commented 9 years ago

It seems that range 0x00-0x06 is exactly the same as 0x07-0x0D in the Eddystone-URL HTTP URL table.

Example 0x00 = .com 0x07 = .com

is this by design. If not? Better to remove it. If it is it should be explained in the document.

scottjenson commented 9 years ago

0x00 is actually '.com/' it has a trailing / (every byte counts ;-)

Scott

alexvanboxel commented 9 years ago

OK, I see this now. But isn't it semantically the same. Having www.google.com encoded with or without the / is the same if you don't include a path in the URI. If you need a path you have to use the one with the /.

This would free up a range for the some of the new top level domains. Anyway. I created a pull request with documentation change.

scottjenson commented 9 years ago

merged. Thanks for the change