From a34193d3711508fb811344f4a7be2e2e09c3d115 Mon Sep 17 00:00:00 2001 From: Dennis Geurts Date: Mon, 29 Jun 2015 07:37:50 +0200 Subject: [PATCH] fix for #243 --- specification/AdvertisingMode.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/specification/AdvertisingMode.md b/specification/AdvertisingMode.md index 8cec2ce..993a005 100644 --- a/specification/AdvertisingMode.md +++ b/specification/AdvertisingMode.md @@ -164,6 +164,13 @@ below. Note: URIs are written only with the graphic printable characters of the US-ASCII coded character set. The octets 00-20 and 7F-FF hexadecimal are not used. See “Excluded US-ASCII Characters” in RFC 2936. + +### UriBeacon HTTP URL decoding + +During the decoding process of a sequence of characters denoting a UriBeacon one should first determine whether it starts with a Uri scheme prefix. +Then, if the scheme prefix denotes an HTTP URL prefix, all subsequent characters should be insepcted and expanded accordingly. It is possible +for the sequence of characters to contain multiple HTTP URL expansion characters. + ## References - `Service UUID` type is defined in Core Specification Supplement, Part A, section 1.1 - `Service Data` type is defined in Core Specification Supplement, Part A, section 1.11