- From: Subbu Allamaraju <subbu@subbu.org>
- Date: Thu, 28 Jan 2010 22:23:07 -0800
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Jan Algermissen <algermissen1971@mac.com>, HTTP Working Group <ietf-http-wg@w3.org>, Apps Discuss <discuss@apps.ietf.org>
Could you elaborate on the purpose of such fields when they have no bearing on rels on the wire? The last para of 4.1 does include an example, but it seems vague. It also seems that any information that can be expressed via fields can equally be described in prose as part of the description. Subbu On Jan 28, 2010, at 8:25 PM, Mark Nottingham wrote: > No, the extension fields are in the registry itself; e.g., by adding a "foo" field to it, you add a "foo" field to every registered link relation type, in the registry (NOT on the wire). > > > On 23/01/2010, at 8:53 AM, Jan Algermissen wrote: > >> >> On Jan 22, 2010, at 7:19 PM, Subbu Allamaraju wrote: >> >>> You mean "link-extension" params? >> >> Hmm, no I am getting confused :-) >> >> I;d say link-extension == field. >> >> Mark? >> >> Jan >> >> >> >>> >>> Subbu >>> >>> On Jan 20, 2010, at 11:37 PM, Jan Algermissen wrote: >>> >>>> >>>> On Jan 20, 2010, at 10:38 PM, Subbu Allamaraju wrote: >>>> >>>>> The usage of fields is not clear. Sec. 6.3 says that "entries in the Link Relation Type Registry can be extended with application-specific data". But the BNF in Sec. 5 does not specify fields. Could you clarify the intent of fields? >>>> >>>> I understand fields to be meant as link relation specific parameters. >>>> >>>> Jan >>>> >>>> >>>> >>>>> >>>>> Subbu >>>>> >>>>> On Jan 18, 2010, at 9:31 PM, Mark Nottingham wrote: >>>>> >>>>>> >>>>>> >>>>>> Begin forwarded message: >>>>>> >>>>>>> From: Internet-Draft@ietf.org >>>>>>> Date: 19 January 2010 4:30:02 PM AEDT >>>>>>> To: mnot@pobox.com, draft-nottingham-http-link-header@tools.ietf.org,lisa.dusseault@gmail.com >>>>>>> Subject: New Version Notification - draft-nottingham-http-link-header-07.txt >>>>>>> >>>>>>> New version (-07) has been submitted for draft-nottingham-http-link-header-07.txt. >>>>>>> http://www.ietf.org/internet-drafts/draft-nottingham-http-link-header-07.txt >>>>>>> Sub state has been changed to AD Follow up from New Id Needed >>>>>>> >>>>>>> Diff from previous version: >>>>>>> http://tools.ietf.org/rfcdiff?url2=draft-nottingham-http-link-header-07 >>>>>>> >>>>>>> IETF Secretariat. >>>>>> >>>>>> >>>>>> -- >>>>>> Mark Nottingham http://www.mnot.net/ >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> ----------------------------------- >>>> Jan Algermissen, Consultant >>>> >>>> Mail: algermissen@acm.org >>>> Blog: http://www.nordsc.com/blog/ >>>> Work: http://www.nordsc.com/ >>>> ----------------------------------- >>>> >>>> >>>> >>> >>> >> >> ----------------------------------- >> Jan Algermissen, Consultant >> >> Mail: algermissen@acm.org >> Blog: http://www.nordsc.com/blog/ >> Work: http://www.nordsc.com/ >> ----------------------------------- >> >> >> > > > -- > Mark Nottingham http://www.mnot.net/ >
Received on Friday, 29 January 2010 06:23:44 UTC