Re: [webfinger] Redefining "properties"

Mike Jones <> Sat, 16 August 2014 19:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3F5611A016C for <>; Sat, 16 Aug 2014 12:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jcN67l1gSoap for <>; Sat, 16 Aug 2014 12:21:55 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A8BE21A016B for <>; Sat, 16 Aug 2014 12:21:54 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1005.10; Sat, 16 Aug 2014 19:21:51 +0000
Received: from (2a01:111:f400:7c10::1:170) by (2a01:111:e400:401e::50) with Microsoft SMTP Server (TLS) id 15.0.1010.18 via Frontend Transport; Sat, 16 Aug 2014 19:21:51 +0000
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1010.11 via Frontend Transport; Sat, 16 Aug 2014 19:21:51 +0000
Received: from ([]) by ([]) with mapi id 14.03.0195.002; Sat, 16 Aug 2014 19:21:26 +0000
From: Mike Jones <>
To: "Paul E. Jones" <>, Will Norris <>, "" <>
Thread-Topic: [webfinger] Redefining "properties"
Thread-Index: AQHPtdU6hil2+M2G6kyYHw6GiMhwPJvMUlSAgAdMK4CAAARhmw==
Date: Sat, 16 Aug 2014 19:21:25 +0000
Message-ID: <>
References: <>, <em6aba2e86-7b0f-49d3-a041-49439c5f7df4@sydney>
In-Reply-To: <em6aba2e86-7b0f-49d3-a041-49439c5f7df4@sydney>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739439AE1FE1ETK5EX14MBXC293r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:; CTRY:US; IPV:CAL; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019005)(438002)(479174003)(24454002)(13464003)(377454003)(189002)(199003)(77096002)(50986999)(92726001)(79102001)(97736001)(19617315012)(33656002)(76176999)(87936001)(20776003)(2656002)(15202345003)(92566001)(19625215002)(19580405001)(19580395003)(86612001)(83322001)(80022001)(26826002)(77982001)(104016003)(19273905006)(85852003)(44976005)(6806004)(76482001)(15395725005)(55846006)(85306004)(106116001)(99396002)(69596002)(81342001)(107046002)(68736004)(84676001)(4396001)(81156004)(81542001)(64706001)(83072002)(16236675004)(54356999)(106466001)(74502001)(14971765001)(15975445006)(46102001)(86362001)(31966008)(84326002)(21056001)(95666004)(71186001)(74662001)(2501001)(563064011)(19607625011); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR03MB188;; FPR:; MLV:ovrnspm; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;UriScan:;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0305463112
Received-SPF: Pass ( domain of designates as permitted sender); client-ip=;;
Authentication-Results: spf=pass (sender IP is;
Cc: "" <>
Subject: Re: [webfinger] Redefining "properties"
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 16 Aug 2014 19:21:57 -0000

People want to put JWK Sets into the results.
From: Paul E. Jones<>
Sent: ‎8/‎16/‎2014 12:05 PM
To: Will Norris<>;<>
Subject: Re: [webfinger] Redefining "properties"


Sorry for the slow response.  I've been busy.

Yes, folks do want to put more complex data into JRD as opposed to linking, including objects or arrays.  I can see how this can be abused, but then I can also see an argument for not linking to data that could be trivially represented inside the JRD itself.

Unfortunately, I do not have details of the specific use cases.  All I do know is that there people working on unrelated applications where they want to be able to  do things like this with WebFinger:

"properties" :
  "" :
    "a" : "Hello",
    "b" : 32

Perhaps what might be worse is the possibility that people do this:

"properties" :
  "" : "{\"a\" : \"Hello\", \"b\" : 32}"
When working on WebFinger, there was a desire to keep it as simple as possible.  However, I fully appreciate why some would want to do something like this.  Sometimes, linking to external resources is "overkill" for the task at hand.  And, you're right that dealing with polymorphic data types can be a pain.  Then again, the JSON parser deals with much of this automatically and the client is likely going to only be looking for known members, anyway.

So, I'm not sure what to do here.  I'm OK with making a change.  It bothers me that we might break any client code that assumes all properties are strings.  But, there is always the option to add some other member named something other than "properties".

I take it you're not too keen on the idea, though.


------ Original Message ------
From: "Will Norris" <<>>
Cc: "" <<>>
Sent: 8/11/2014 11:39:19 PM
Subject: Re: [webfinger] Redefining "properties"

what are the actual use cases prompting this?  If folks are trying to store more complicated data, why is it not just a linked resource?

Personally, as a client author, I've always hated it when APIs have polymorphic data types like this.

On Mon, Aug 11, 2014 at 7:29 PM, 'Paul E. Jones' via WebFinger <<>> wrote:

I have been asked by multiple people for different purposes to see if it might be possible to redefine "properties" in the JSON Resource Descriptor.

Per RFC 7033, "properties" is defined as an object that has zero or more name/value pairs whose values are strings or null.  The suggestion is that the values should be any valid JSON type.  Thus, a property might refer to a string (as is does now) or it might refer to an object or array.

This change would break any parsers strictly implement definition of "properties".  So, there are two questions I want to present to those who are interested:

1) Would you be agreeable to change the current definition of "properties" to allow any value type?
2) If not, would be agreeable to introducing something like "properties" that essentially allows for the same and, if so, what should this new object be named?

Personally, as much as I don't like breaking backward-compatibility, I'm favorable to redefining properties to accomodate what people want to do.  I'm willing to work on an RFC 7033bis and/or a new RFC to update the JRD specification, if folks are agreeable to either (1) or (2).



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<>.
For more options, visit