I've replaced "subscribe" with "current"; otherwise, these are the same as in the last round. I think they're ready to go -- any more comments?


 -  Attribute Value: previous
- Description: A URI that refers to the immediately preceding document in a series of documents.
 -  Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Such agents should also take care to detect circular references.

 -  Attribute Value: next
- Description: A URI that refers to the immediately following document in a series of documents.
 -  Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Such agents should also take care to detect circular references.

 -  Attribute Value: first
- Description: A URI that refers to the furthest preceding document in a series of documents.
 -  Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Such agents should also take care to detect circular references.

 -  Attribute Value: last
- Description: A URI that refers to the furthest following document in a series of documents.
 -  Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Such agents should also take care to detect circular references.

 -  Attribute Value: current
- Description: A URI that, when dereferenced, returns a feed document containing the most recent entries in the feed.
 -  Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document).


--
Mark Nottingham     http://www.mnot.net/

Reply via email to