how does webfinger represent numbers

9 views
Skip to first unread message

Melvin Carvalho

unread,
Jul 28, 2013, 12:29:30 PM7/28/13
to webf...@googlegroups.com
I've seen two instances:

 "properties" : { "http://webfinger.example/mail/port" : "993" }

and

       "properties" :
       {
         "http://blgx.example.net/ns/version" : 1.3,
         "http://blgx.example.net/ns/ext" : null
       },

One is quoted and one isnt.  Do these correspond to he JSON types of number, string, boolean etc. ?

Will Norris

unread,
Jul 28, 2013, 10:32:48 PM7/28/13
to webf...@googlegroups.com
yeah, since the document is JSON, they would be the relevant JSON type.  http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-16#section-4.4.3 defines property values as strings or null, so the JSON number would be invalid.


--
 
---
You received this message because you are subscribed to the Google Groups "WebFinger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webfinger+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Melvin Carvalho

unread,
Jul 28, 2013, 10:41:24 PM7/28/13
to webf...@googlegroups.com
On 29 July 2013 04:32, Will Norris <wi...@willnorris.com> wrote:
yeah, since the document is JSON, they would be the relevant JSON type.  http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-16#section-4.4.3 defines property values as strings or null, so the JSON number would be invalid.

Thanks Will!

So I guess the "1.3" example in the spec should be quoted.

Paul E. Jones

unread,
Jul 28, 2013, 11:59:32 PM7/28/13
to webf...@googlegroups.com

The 1.3 (without quotes) is an error in the spec.  I’ve already fixed that in the next draft to be published.  These are always either strings or null.

 

Paul

 

--

Reply all
Reply to author
Forward
0 new messages