[webfinger] Redefining "properties"

["Paul E. Jones" <[e-mail]>]

Folks,

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).

Paul