The "expires" member of the JRD

[Paul E. Jones]

Folks,

 

Questions have been raised about the “expires” member of the JRD two or three times now, with concerns related to the fact that HTTP has multiple ways of also indicating how long a resource representation should be cached.

 

This element is exists for historical reason, but it’s not clear to me if anyone is using it or cares to use it.

 

Shall we keep it or just remove it from the spec entirely?

 

Paul

 

[Brad Fitzpatrick]

I'd be happy seeing it removed.

HTTP seems sufficient.

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

[Gonzalo Salgueiro]

+1

Gonzalo

> _______________________________________________
> webfinger mailing list
> webf...@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger

[Tim Bray]

+1

[John Bradley]

Yes it is a XRI legacy.  Get rid of it. 

John B.

[Mike Jones]

+1

[Paul E. Jones]

Seems to be overwhelming support.  It’s gone.

[Paul E. Jones]

It took me only few seconds to remove.  If nobody is using it, I agree we should remove it.

 

I’ll get out a new version within 12 hours.

 

Paul

 

From: webfinge...@ietf.org [mailto:webfinge...@ietf.org] On Behalf Of Evan Prodromou
Sent: Friday, February 08, 2013 9:29 AM
To: Paul E. Jones
Cc: webf...@ietf.org; webf...@googlegroups.com
Subject: Re: [webfinger] The "expires" member of the JRD

 

Unless there are earth-shatteringly critical problems with the spec, I feel like it's time to ship what we've got.

The presence or absence of the optional "expires" element in JRD is of microscopic importance; let's get this thing out.

-Evan