Re: [apps-discuss] request to register 'describes' link relation (http://tools.ietf.org/html/draft-wilde-describes-link-01)

hi all,

Since we are at this, I would also like to point out the request to
register Memento link relation types, which I submitted August 29
2012:

http://www.ietf.org/mail-archive/web/link-relations/current/msg00372.html

It was my understanding, from a brief email exchange with Mark
Nottingham, that it was possible to reserve a spot in the registry for
rel types for which there was not yet an RFC but for which a spec was
in the works. In the case of Memento, that is the I-D
https://datatracker.ietf.org/doc/draft-vandesompel-memento/. I think
this ability is rather essential: Memento rel types are already in use
in many applications and it would be rather counter-productive if
someone else could register them for some other purpose prior to the
Memento I-D reaching RFC status.

Cheers

Herbert

On Tue, Oct 9, 2012 at 6:09 PM, James M Snell <jasnell@gmail.com> wrote:
> Sticking my hand up and hoping to get some similar treatment for:
>
>   http://www.ietf.org/id/draft-snell-additional-link-relations-05.txt
>
> This one has been there for a while. I followed the same advice you just
> gave dret and changed it to informational and cleaned up the normative
> references. Pretty basic draft.
>
> - James
>
> On Tue, Oct 9, 2012 at 4:40 PM, Barry Leiba <barryleiba@computer.org> wrote:
>>
>> [I'm removing the non-IETF groups from the distribution list.]
>>
>> > this is a request to register 'describes' in the IANA link relations
>> > registry established by RFC 5988. the latest draft of the registration
>> > document is available at
>> > http://tools.ietf.org/html/draft-wilde-describes-link-01, and the last
>> > version announced on a variety of mailing lists has not generated any
>> > feedback asking for changes.
>>
>> I'll let the folks on the link-relations list respond to the
>> suitability of the specification for documenting a useful link
>> relation.  I have just a couple of process points:
>>
>> 1. In order for the registration to be done, this document will have
>> to be published somewhere that will satisfy the Designated Expert as
>> being a stable reference.  That probably means that you'll want this
>> to be an RFC, so you need to be sorting out how that will happen.
>> Happily, I'm willing to sponsor this as an AD-sponsored individual
>> submission, if the link-relations folks agree that we should register
>> this.
>>
>> 2. I don't think this should be Standards Track, though (and it
>> doesn't need to be in order to register the link relation and to be
>> the reference documentation for it).  I would prefer that you make it
>> Informational, change the "SHOULD" to "should" in the Security
>> Considerations, and remove Section 2 and the normative reference to
>> RFC 2119.  (This can wait until after the feedback from the
>> link-relations mailing list.)
>>
>> Barry, Applications AD
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
> _______________________________________________
> link-relations mailing list
> link-relations@ietf.org
> https://www.ietf.org/mailman/listinfo/link-relations
>

-- 
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/

==