"template" is defined in IETF #RFC6415 (i.e., Web Host Metadata / #hostMeta ).
https://www.rfc-editor.org/rfc/rfc6415.html
#WebFinger 's IETF #RFC7033 mentions that here:
"The JSON Resource Descriptor (JRD), originally introduced in RFC 6415"
"template" is defined in IETF #RFC6415 (i.e., Web Host Metadata / #hostMeta ).
https://www.rfc-editor.org/rfc/rfc6415.html
#WebFinger 's IETF #RFC7033 mentions that here:
"The JSON Resource Descriptor (JRD), originally introduced in RFC 6415"
It behaves exactly like I would expect it to. It returns the appropriate format given the accept type of the request. Why should this cause problems?
It can only make things better as 3rd party client apps that cannot deal with it, might be encouraged to set proper accept types.
Weird — #Pleroma 's #WebFinger can return (#XML based) #XRD data (rather than just (#JSON based) #JRD data).
I think the expectation from IETF #RFC7033 is that — WebFinger returns JRD (i.e., JSON Resource Descriptor format).
...
I wonder if this causes any problems with any 3rd party client apps.
Using Web Host Metadata's #XRD & #JRD to figure out where #WebFinger is seems unnecessarily complex to me.
(This is used by some #Fediverse software.)
...
/.well-known/host-meta
/.well-known/host-meta.json
...