From julian.reschke@gmx.de Sun Mar 3 09:33:51 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2E021F8775 for ; Sun, 3 Mar 2013 09:33:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.949 X-Spam-Level: X-Spam-Status: No, score=-102.949 tagged_above=-999 required=5 tests=[AWL=-1.650, BAYES_00=-2.599, MANGLED_REGSTR=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o94fA6YoljfT for ; Sun, 3 Mar 2013 09:33:50 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 838A721F8769 for ; Sun, 3 Mar 2013 09:33:50 -0800 (PST) Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MARmu-1U55F918w6-00BZHT for ; Sun, 03 Mar 2013 18:33:49 +0100 Received: (qmail invoked by alias); 03 Mar 2013 17:33:49 -0000 Received: from p54BB34C3.dip.t-dialin.net (EHLO [192.168.1.105]) [84.187.52.195] by mail.gmx.net (mp001) with SMTP; 03 Mar 2013 18:33:49 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX191OzcoQCl1iz7CIvkAiVwpJVPo7EwzeN+MPUYlfv oLk8Eq2m/nz/cj Message-ID: <5133897C.6010505@gmx.de> Date: Sun, 03 Mar 2013 18:33:48 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Bjoern Hoehrmann Subject: Re: 'meta' link relation References: <51236F3C.9070700@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Mar 2013 17:33:51 -0000 On 2013-02-19 13:56, Bjoern Hoehrmann wrote: > * Julian Reschke wrote: >> So it seems that the definition we *could* use is >> , right? Should we then >> note that thos has been obsoleted, and that "describedby" is more current? > > Referencing that document, or any other I've mentioned, is fine by me. I Well, we need something that actually describes it. > do not think it's useful to decide whether "describedby" is identical to > "meta" and whether the latter is "obsolete" now. Problems here would be- It appears the people (DC) who came up with the relation name first do not use it anymore. That certainly sounds like "obsolete" to me. If somebody thinks that this should be registered as something recommended, he/she should write down a definition and register *that*. Otherwise, we can add the name to the registry, stating where it appeared first and that it appears to be abandoned. > gin with RFC 5988 saying "Refers to a resource providing information > about the link's context." while the referenced document (and the regis- > tration template the RFC uses is wrong, there is no Documentation field) Oh, the horror. I was tempted to open an erratum, but this is just a one-time registration form that already has been processed by IANA. > has "The relationship A 'describedby' B asserts that resource B provides > a description of resource A." and "provides information about" and "pro- > vides a description of" is not quite the same thing. And if "meta" is > obsolete, why does e.g. the FOAF specification not use "describedby" and Pointer? > why does the source code of http://www.dublincore.org/ still use "meta", > and so on... You may want to ask the maintainers of that site. I have no problem registering "meta", but it would be really nice if we had a proper description, not just a few mentions and one spec that has been obsoleted. Best regards, Julian From derhoermi@gmx.net Sun Mar 3 10:29:31 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E52ED21F87E4 for ; Sun, 3 Mar 2013 10:29:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.384 X-Spam-Level: X-Spam-Status: No, score=-3.384 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Os8xVsUtdeU9 for ; Sun, 3 Mar 2013 10:29:30 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 6C75421F87AD for ; Sun, 3 Mar 2013 10:29:30 -0800 (PST) Received: from mailout-de.gmx.net ([10.1.76.19]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MIBYu-1UEyHg2AGM-003ud1 for ; Sun, 03 Mar 2013 19:29:26 +0100 Received: (qmail invoked by alias); 03 Mar 2013 18:26:15 -0000 Received: from p5B233D3B.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.35.61.59] by mail.gmx.net (mp019) with SMTP; 03 Mar 2013 19:26:15 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX1+mMDAYkjGmlNMhkOCJpg/yEPlycEqJWaCdxjEjBc 16ps2jdxyfpfmb From: Bjoern Hoehrmann To: Julian Reschke Subject: Re: 'meta' link relation Date: Sun, 03 Mar 2013 19:26:16 +0100 Message-ID: References: <51236F3C.9070700@gmx.de> <5133897C.6010505@gmx.de> In-Reply-To: <5133897C.6010505@gmx.de> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Mar 2013 18:29:32 -0000 * Julian Reschke wrote: >On 2013-02-19 13:56, Bjoern Hoehrmann wrote: >> has "The relationship A 'describedby' B asserts that resource B provides >> a description of resource A." and "provides information about" and "pro- >> vides a description of" is not quite the same thing. And if "meta" is >> obsolete, why does e.g. the FOAF specification not use "describedby" and > >Pointer? Still at . >I have no problem registering "meta", but it would be really nice if we >had a proper description, not just a few mentions and one spec that has >been obsoleted. I think http://dublincore.org/documents/dcmes-xml/#sec4 is a sufficient reference for the meaning of the relationship keyword. Not perfect, but people are unlikely to write dozens of single-page RFCs with one-line definitions to add a similarily short row to the registry table... -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ From hvdsomp@gmail.com Sun Mar 3 16:07:10 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33FEC21F88C1 for ; Sun, 3 Mar 2013 16:07:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IozM0Q+Yqade for ; Sun, 3 Mar 2013 16:07:05 -0800 (PST) Received: from mail-ia0-x22e.google.com (mail-ia0-x22e.google.com [IPv6:2607:f8b0:4001:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBF621F8899 for ; Sun, 3 Mar 2013 16:07:02 -0800 (PST) Received: by mail-ia0-f174.google.com with SMTP id u20so4284127iag.33 for ; Sun, 03 Mar 2013 16:07:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=8YAWHWbCCFFn028Zqa9QeejH613nhjqXL7NJ/dB5Yso=; b=FcT1bYBxPjoaqTfGzAe1VUDe4aWA7CgcZFaiPlMM0ePbbpA3t2SozhEYBiA75nXVIv wy1p/9qdVklEOuv5nBM3QloDpfdpgwQvLlRLvjfwRzE4zT7D1aIlyZkcC95e3O8J59MD hAo+hpzTJsr4KhFRfoswPdxqfZ8CPrn8DzSlBAGsfNw7AXcbxVZRMBbFR9LeBY34RW0A pq8LmgUARvw1w1p9aWn0mKG3B8A6IsYxIVU3D5hiySQPVcVvp9bGRKL40fcyTlP43L/l GNT0Xv4+NLUJZnlVzf1bI0GOV9ZB8dg+ucujX/tHyq+c6+Rev4aHHVtGWJcjh6RWFkot gkYQ== MIME-Version: 1.0 X-Received: by 10.50.237.71 with SMTP id va7mr1035782igc.88.1362355621809; Sun, 03 Mar 2013 16:07:01 -0800 (PST) Received: by 10.64.69.194 with HTTP; Sun, 3 Mar 2013 16:07:01 -0800 (PST) Date: Sun, 3 Mar 2013 17:07:01 -0700 Message-ID: Subject: NEW RELATIONS: timegate ; timemap ; memento ; original From: Herbert van de Sompel To: link-relations@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Robert Sanderson , Michael Nelson X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2013 00:07:10 -0000 Hi all, I would like to request adding the following Relation Types to the Registry: - "timegate" - "timemap" - "memento" - "original" These Relation Types are used in Memento "Time Travel for the Web" for which a new Internet Draft was just published at http://www.ietf.org/id/draft-vandesompel-memento-06.txt I include the description of each Relation Type below. For completeness, I also include the meaning of the terms TimeGate, TimeMap, Memento, Original Resource as introduced in the Memento specification: o Original Resource: An Original Resource is a resource that exists or used to exist, and for which access to one of its prior states may be required. o Memento: A Memento for an Original Resource is a resource that encapsulates a prior state of the Original Resource. o TimeGate: A TimeGate for an Original Resource is a resource that is capable of datetime negotiation to support access to prior states of the Original Resource. o TimeMap: A TimeMap for an Original Resource is a resource from which a list of URIs of Mementos of the Original Resource is available. Greetings Herbert Van de Sompel ================== Relation Type: timegate Description: A link with a "timegate" Relation Type is used to point from the Original Resource, as well as from a Memento associated with the Original Resource, to a TimeGate for the Original Resource. Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt Notes: Used in the Memento "Time Travel for the Web" framework. ================== Relation Type: timemap Description: A link with a "timemap" Relation Type is used to point from a TimeGate or a Memento associated with an Original Resource, as well as from the Original Resource itself, to a TimeMap for the Original Resource. Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt Notes: Used in the Memento "Time Travel for the Web" framework. ================== Relation Type: memento Description: A link with a "memento" Relation Type is used to point from a TimeGate or a Memento for an Original Resource, as well as from the Original Resource itself, to a Memento for the Original Resource. Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt Notes: Used in the Memento "Time Travel for the Web" framework. ================== Relation Type: original Description: A link with an "original" Relation Type is used to point from a TimeGate or a Memento to its associated Original Resource. Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt Notes: Used in the Memento "Time Travel for the Web" framework. ================== -- Herbert Van de Sompel Digital Library Research & Prototyping Los Alamos National Laboratory, Research Library http://public.lanl.gov/herbertv/ == From jan.algermissen@nordsc.com Sun Mar 17 07:15:21 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1585321F85DC for ; Sun, 17 Mar 2013 07:15:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUmDozlo9kT0 for ; Sun, 17 Mar 2013 07:15:20 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by ietfa.amsl.com (Postfix) with ESMTP id 0900521F85DA for ; Sun, 17 Mar 2013 07:15:20 -0700 (PDT) Received: from [192.168.2.103] (p548F9DCF.dip.t-dialin.net [84.143.157.207]) by mrelayeu.kundenserver.de (node=mrbap3) with ESMTP (Nemesis) id 0Lr24R-1Uuykp1G5b-00eZ4U; Sun, 17 Mar 2013 15:14:44 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: NEW RELATIONS: timegate ; timemap ; memento ; original From: Jan Algermissen In-Reply-To: Date: Sun, 17 Mar 2013 15:14:44 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Herbert van de Sompel X-Mailer: Apple Mail (2.1499) X-Provags-ID: V02:K0:Qp1662r3C2tHGD/ESoghbsohsN4II7fCoIGk1TXzvvZ uFN+RQtLBDZRuF73ZJdmxP01EqbZF75TPoqUKraGUrFjSHvG3l ZeaTIgGCYLuR0Dk9X4mymQSUsM7JY5opdeiqhjGt7bWxaYnHSN dl5G4FwqiFZC9DTEEipFWzQ4DNxGEBnpuVF3rmYHZUGWf123bO 3pPs4a2eUx4UsQrqNm4AqLx7fYtOZzWdFs4dmM3dWY8jX9ETxa vQrwTehPuphybR36YQcxH80GBdGGl+DfEkEi8k2mLp/S2PGAyD ThCkqSprMCCF6MfLU18ngqdhZ3rr8gia7piG0jVtg1Mb9sOOdw 13chgJR4ciyyM+3aZqjSQ8J6JMct7vG+HC/fRwIWdDO8wVhyK9 hZ3pGnL9Gwa8Q== Cc: Robert Sanderson , Michael Nelson , link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 14:15:21 -0000 Hi Herbert, I think we need the reference to be a stable document first. Pointing to = a 06-version does not seem to make much sense, IMO. Jan On 04.03.2013, at 01:07, Herbert van de Sompel = wrote: > Hi all, >=20 > I would like to request adding the following Relation Types to the = Registry: > - "timegate" > - "timemap" > - "memento" > - "original" >=20 > These Relation Types are used in Memento "Time Travel for the Web" for > which a new Internet Draft was just published at > http://www.ietf.org/id/draft-vandesompel-memento-06.txt >=20 > I include the description of each Relation Type below. For > completeness, I also include the meaning of the terms TimeGate, > TimeMap, Memento, Original Resource as introduced in the Memento > specification: >=20 > o Original Resource: An Original Resource is a resource that > exists or used to exist, and for which access to one of its prior > states may be required. >=20 > o Memento: A Memento for an Original Resource is a resource that > encapsulates a prior state of the Original Resource. >=20 > o TimeGate: A TimeGate for an Original Resource is a resource that > is capable of datetime negotiation to support access to prior states > of the Original Resource. >=20 > o TimeMap: A TimeMap for an Original Resource is a resource from > which a list of URIs of Mementos of the Original Resource is > available. >=20 > Greetings >=20 > Herbert Van de Sompel >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Relation Type: timegate >=20 > Description: A link with a "timegate" Relation Type is used to point > from the Original Resource, as well as from a Memento associated with > the Original Resource, to a TimeGate for the Original Resource. >=20 > Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >=20 > Notes: Used in the Memento "Time Travel for the Web" framework. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Relation Type: timemap >=20 > Description: A link with a "timemap" Relation Type is used to point > from a TimeGate or a Memento associated with an Original Resource, as > well as from the Original Resource itself, to a TimeMap for the > Original Resource. >=20 > Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >=20 > Notes: Used in the Memento "Time Travel for the Web" framework. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Relation Type: memento >=20 > Description: A link with a "memento" Relation Type is used to point > from a TimeGate or a Memento for an Original Resource, as well as from > the Original Resource itself, to a Memento for the Original Resource. >=20 > Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >=20 > Notes: Used in the Memento "Time Travel for the Web" framework. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Relation Type: original >=20 > Description: A link with an "original" Relation Type is used to point > from a TimeGate or a Memento to its associated Original Resource. >=20 > Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >=20 > Notes: Used in the Memento "Time Travel for the Web" framework. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > --=20 > Herbert Van de Sompel > Digital Library Research & Prototyping > Los Alamos National Laboratory, Research Library > http://public.lanl.gov/herbertv/ >=20 > =3D=3D > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations From hvdsomp@gmail.com Sun Mar 17 07:49:17 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC0E21F8948 for ; Sun, 17 Mar 2013 07:49:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BIbTXW69i9X for ; Sun, 17 Mar 2013 07:49:16 -0700 (PDT) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 89EF721F893D for ; Sun, 17 Mar 2013 07:49:16 -0700 (PDT) Received: by mail-ie0-f179.google.com with SMTP id k11so6011037iea.38 for ; Sun, 17 Mar 2013 07:49:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dGAJWggFyGUIwB3Wv4m+SHkZhdnOqD0MC/ta1PMZyys=; b=G/KGY8mvSjEinQapIFeuUuTiIY64UGCNpW9FFogiIveSmX4zE8jiuazQvsO2+gKGKt AYR01J09TRz0IM70H1YF2HBpHKygVsAXybwO7bvDb3KDwV+fgv4imqcEecAVaH5rnCwG HbZbi6Z7uu/PSdoG2fvojNm6SmR04GgAASefJpJpmD2kTDbC9KqiYAywp9OfNJ+EeWIW lEcsomrGazkqjwBCHVk0oKO+rlY323kG9/O2jgTkagHsU9POoPdfaBJFLy13AUM3Va1T pgs5ujKqR62BbXoPiIUBoUiYPyD7Jx8t/rFFTGPaCYjdbfMC08cHb14uUdrvvxFK5Erj cT9A== MIME-Version: 1.0 X-Received: by 10.42.136.67 with SMTP id s3mr7739827ict.31.1363531756108; Sun, 17 Mar 2013 07:49:16 -0700 (PDT) Received: by 10.64.69.194 with HTTP; Sun, 17 Mar 2013 07:49:15 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Mar 2013 08:49:15 -0600 Message-ID: Subject: Re: NEW RELATIONS: timegate ; timemap ; memento ; original From: Herbert van de Sompel To: Jan Algermissen Content-Type: text/plain; charset=ISO-8859-1 Cc: Robert Sanderson , Michael Nelson , link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 14:49:17 -0000 Dear Jan, In the link relation registry at http://www.iana.org/assignments/link-relations/link-relations.xml I see several entries that point to versions of Internet Drafts: - http://tools.ietf.org/html/draft-snell-additional-link-relations-07 - http://tools.ietf.org/html/draft-wilde-profile-link-04 If for some reason the same approach can not be followed for the Memento relation types, then I can see two alternatives: (1) Use the version-independent URI of the spec as posted on the Memento site: http://www.mementoweb.org/guide/rfc/ID/ The current version of the Internet Draft is always available from that URI, and the RFC will eventually be available from there too. (2) Use the version-independent URI of the spec in the IETF data tracker: https://datatracker.ietf.org/doc/draft-vandesompel-memento/ Many greetings Herbert On Sun, Mar 17, 2013 at 8:14 AM, Jan Algermissen wrote: > Hi Herbert, > > I think we need the reference to be a stable document first. Pointing to a 06-version does not seem to make much sense, IMO. > > Jan > > > On 04.03.2013, at 01:07, Herbert van de Sompel wrote: > >> Hi all, >> >> I would like to request adding the following Relation Types to the Registry: >> - "timegate" >> - "timemap" >> - "memento" >> - "original" >> >> These Relation Types are used in Memento "Time Travel for the Web" for >> which a new Internet Draft was just published at >> http://www.ietf.org/id/draft-vandesompel-memento-06.txt >> >> I include the description of each Relation Type below. For >> completeness, I also include the meaning of the terms TimeGate, >> TimeMap, Memento, Original Resource as introduced in the Memento >> specification: >> >> o Original Resource: An Original Resource is a resource that >> exists or used to exist, and for which access to one of its prior >> states may be required. >> >> o Memento: A Memento for an Original Resource is a resource that >> encapsulates a prior state of the Original Resource. >> >> o TimeGate: A TimeGate for an Original Resource is a resource that >> is capable of datetime negotiation to support access to prior states >> of the Original Resource. >> >> o TimeMap: A TimeMap for an Original Resource is a resource from >> which a list of URIs of Mementos of the Original Resource is >> available. >> >> Greetings >> >> Herbert Van de Sompel >> >> ================== >> >> Relation Type: timegate >> >> Description: A link with a "timegate" Relation Type is used to point >> from the Original Resource, as well as from a Memento associated with >> the Original Resource, to a TimeGate for the Original Resource. >> >> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >> >> Notes: Used in the Memento "Time Travel for the Web" framework. >> >> ================== >> >> Relation Type: timemap >> >> Description: A link with a "timemap" Relation Type is used to point >> from a TimeGate or a Memento associated with an Original Resource, as >> well as from the Original Resource itself, to a TimeMap for the >> Original Resource. >> >> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >> >> Notes: Used in the Memento "Time Travel for the Web" framework. >> >> ================== >> >> Relation Type: memento >> >> Description: A link with a "memento" Relation Type is used to point >> from a TimeGate or a Memento for an Original Resource, as well as from >> the Original Resource itself, to a Memento for the Original Resource. >> >> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >> >> Notes: Used in the Memento "Time Travel for the Web" framework. >> >> ================== >> >> Relation Type: original >> >> Description: A link with an "original" Relation Type is used to point >> from a TimeGate or a Memento to its associated Original Resource. >> >> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >> >> Notes: Used in the Memento "Time Travel for the Web" framework. >> >> ================== >> >> -- >> Herbert Van de Sompel >> Digital Library Research & Prototyping >> Los Alamos National Laboratory, Research Library >> http://public.lanl.gov/herbertv/ >> >> == >> _______________________________________________ >> 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/ == From jan.algermissen@nordsc.com Mon Mar 18 00:20:19 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17EA121F88FB for ; Mon, 18 Mar 2013 00:20:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.63 X-Spam-Level: X-Spam-Status: No, score=-1.63 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jf6zWvWyN0uO for ; Mon, 18 Mar 2013 00:20:18 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by ietfa.amsl.com (Postfix) with ESMTP id CB88C21F8821 for ; Mon, 18 Mar 2013 00:20:17 -0700 (PDT) Received: from [172.20.10.2] (tmo-107-126.customers.d1-online.com [80.187.107.126]) by mrelayeu.kundenserver.de (node=mrbap3) with ESMTP (Nemesis) id 0MhU26-1U3grv3FPW-00McZd; Mon, 18 Mar 2013 08:19:43 +0100 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: NEW RELATIONS: timegate ; timemap ; memento ; original From: Jan Algermissen In-Reply-To: Date: Mon, 18 Mar 2013 08:19:40 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <4862AA0B-B261-4C1D-A511-12158A78FE58@nordsc.com> References: To: Herbert van de Sompel , "julian.reschke@gmx.de Reschke" , Mark Nottingham X-Mailer: Apple Mail (2.1499) X-Provags-ID: V02:K0:HY+ohc84pyqJ77NQH5sYLw/zKel13qtvyl+MTn8B66l KAKKTzKLntkxUZo7xKYGuxLwcxcBxDquRZJIgvMRee3QHNGT9x cCE1XIexbzah+hvImV+d0E/e7dDPx+Umm2r6BGwyriRVE5sMhN Jkg4dRet8bWG9avS+8cLkQKGSXEjelzV71dEGwz6o+u9EKAdtm s4Pzorr1+JDWZJ3anaT3ZpHzngf3dppwYFohRKKanwGOIAprrx 0OAIzBfa8tE98ohWiYBFCuR6D2PIOB8+PSy/8RVDHegnt7uon3 N3lf+xlSHr5GOgsoM1dwEnUT/UIan15lBGmwjbhyjFzgW00Pdm OdeSRgVlG7i4pqgo9OldubjblMnYVtHkUSch7s22u7nFUHyuBQ H3G1s+KNypKLw== Cc: Robert Sanderson , Michael Nelson , link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Mar 2013 07:20:19 -0000 Herbert, On 17.03.2013, at 15:49, Herbert van de Sompel = wrote: > Dear Jan, >=20 > In the link relation registry at > http://www.iana.org/assignments/link-relations/link-relations.xml I > see several entries that point to versions of Internet Drafts: >=20 > - http://tools.ietf.org/html/draft-snell-additional-link-relations-07 > - http://tools.ietf.org/html/draft-wilde-profile-link-04 That is strange - but I guess the idea is to update them, once the specs = are done. Agreed - there is no reason your link relation types could not be = defined the same way. Having said that, I suggest some corrections to the I-D. - Throughout section 2.2 please s/Relation Type/Link Relation Type/ - You write that resource MUST/SHOULD include certain Link headers but = it is the response entities that you mean, yes? Can you be more precise, what response entities and which requests you = are referring too? Supposedly GET, or? - I am not entirely sure whether such things can be constrained - I feel = this is an over-specification that goes beyond HTTP. IOW: I think it is up to the server. Can you reword that in a "if you find a link with rel type XY, then = ...." fashion? @Mark, Julian - what is your take on this? Jan >=20 > If for some reason the same approach can not be followed for the > Memento relation types, then I can see two alternatives: >=20 > (1) Use the version-independent URI of the spec as posted on the = Memento site: >=20 > http://www.mementoweb.org/guide/rfc/ID/ >=20 > The current version of the Internet Draft is always available from > that URI, and the RFC will eventually be available from there too. >=20 > (2) Use the version-independent URI of the spec in the IETF data = tracker: >=20 > https://datatracker.ietf.org/doc/draft-vandesompel-memento/ >=20 > Many greetings >=20 > Herbert >=20 > On Sun, Mar 17, 2013 at 8:14 AM, Jan Algermissen > wrote: >> Hi Herbert, >>=20 >> I think we need the reference to be a stable document first. Pointing = to a 06-version does not seem to make much sense, IMO. >>=20 >> Jan >>=20 >>=20 >> On 04.03.2013, at 01:07, Herbert van de Sompel = wrote: >>=20 >>> Hi all, >>>=20 >>> I would like to request adding the following Relation Types to the = Registry: >>> - "timegate" >>> - "timemap" >>> - "memento" >>> - "original" >>>=20 >>> These Relation Types are used in Memento "Time Travel for the Web" = for >>> which a new Internet Draft was just published at >>> http://www.ietf.org/id/draft-vandesompel-memento-06.txt >>>=20 >>> I include the description of each Relation Type below. For >>> completeness, I also include the meaning of the terms TimeGate, >>> TimeMap, Memento, Original Resource as introduced in the Memento >>> specification: >>>=20 >>> o Original Resource: An Original Resource is a resource that >>> exists or used to exist, and for which access to one of its prior >>> states may be required. >>>=20 >>> o Memento: A Memento for an Original Resource is a resource that >>> encapsulates a prior state of the Original Resource. >>>=20 >>> o TimeGate: A TimeGate for an Original Resource is a resource that >>> is capable of datetime negotiation to support access to prior states >>> of the Original Resource. >>>=20 >>> o TimeMap: A TimeMap for an Original Resource is a resource from >>> which a list of URIs of Mementos of the Original Resource is >>> available. >>>=20 >>> Greetings >>>=20 >>> Herbert Van de Sompel >>>=20 >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> Relation Type: timegate >>>=20 >>> Description: A link with a "timegate" Relation Type is used to point >>> from the Original Resource, as well as from a Memento associated = with >>> the Original Resource, to a TimeGate for the Original Resource. >>>=20 >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >>>=20 >>> Notes: Used in the Memento "Time Travel for the Web" framework. >>>=20 >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> Relation Type: timemap >>>=20 >>> Description: A link with a "timemap" Relation Type is used to point >>> from a TimeGate or a Memento associated with an Original Resource, = as >>> well as from the Original Resource itself, to a TimeMap for the >>> Original Resource. >>>=20 >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >>>=20 >>> Notes: Used in the Memento "Time Travel for the Web" framework. >>>=20 >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> Relation Type: memento >>>=20 >>> Description: A link with a "memento" Relation Type is used to point >>> from a TimeGate or a Memento for an Original Resource, as well as = from >>> the Original Resource itself, to a Memento for the Original = Resource. >>>=20 >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >>>=20 >>> Notes: Used in the Memento "Time Travel for the Web" framework. >>>=20 >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> Relation Type: original >>>=20 >>> Description: A link with an "original" Relation Type is used to = point >>> from a TimeGate or a Memento to its associated Original Resource. >>>=20 >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt >>>=20 >>> Notes: Used in the Memento "Time Travel for the Web" framework. >>>=20 >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>> -- >>> Herbert Van de Sompel >>> Digital Library Research & Prototyping >>> Los Alamos National Laboratory, Research Library >>> http://public.lanl.gov/herbertv/ >>>=20 >>> =3D=3D >>> _______________________________________________ >>> link-relations mailing list >>> link-relations@ietf.org >>> https://www.ietf.org/mailman/listinfo/link-relations >>=20 >=20 >=20 >=20 > --=20 > Herbert Van de Sompel > Digital Library Research & Prototyping > Los Alamos National Laboratory, Research Library > http://public.lanl.gov/herbertv/ >=20 > =3D=3D From jasnell@gmail.com Mon Mar 18 00:39:00 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E68EA21F8555 for ; Mon, 18 Mar 2013 00:38:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvllfiBa3r9s for ; Mon, 18 Mar 2013 00:38:58 -0700 (PDT) Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id E8C0921F854D for ; Mon, 18 Mar 2013 00:38:56 -0700 (PDT) Received: by mail-oa0-f50.google.com with SMTP id l20so5316785oag.9 for ; Mon, 18 Mar 2013 00:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=r7yMMs7J0NaANBLBSfL5B4qaJRGQDKashJkzqdaivO0=; b=JsMYUWP4gSnjSLWwP3KSFvxSN/LqruAUZAx5UYIzgSww7/zTbufVQ8dC0asoDsZ5u9 1cOtTxA5uoS1/+jEspJJVCmgp6JURDEC21YuClICtk5FdADSPFtXUm66v2bl3f7fqXRv gVgkaXxYRZJET+wTVEYgp3fhoQD7cRHmLKpBfaP7EJtAscYa6zSBn+jkONM4Wfzk35nX 4bnVCTKooRwYwZt6QDTgnw22dKNt/hzg0yCjOtRYmyuY+2g+r8WHQe9Jcv4h/+2MhA41 0bqdDLUy9mDltZBURx0PseG3wNmRaKBbUXylyZRdoUXs6jIAuxR/HssMFb5+uEnqxJkE xRVg== MIME-Version: 1.0 X-Received: by 10.182.245.72 with SMTP id xm8mr6436665obc.1.1363592336472; Mon, 18 Mar 2013 00:38:56 -0700 (PDT) Received: by 10.60.23.193 with HTTP; Mon, 18 Mar 2013 00:38:56 -0700 (PDT) Received: by 10.60.23.193 with HTTP; Mon, 18 Mar 2013 00:38:56 -0700 (PDT) In-Reply-To: <4862AA0B-B261-4C1D-A511-12158A78FE58@nordsc.com> References: <4862AA0B-B261-4C1D-A511-12158A78FE58@nordsc.com> Date: Mon, 18 Mar 2013 00:38:56 -0700 Message-ID: Subject: Re: NEW RELATIONS: timegate ; timemap ; memento ; original From: James M Snell To: Jan Algermissen Content-Type: multipart/alternative; boundary=14dae93a0d95d581d704d82e147e Cc: link-relations@ietf.org, "julian.reschke@gmx.de Reschke" , Robert Sanderson , Mark Nottingham , Michael Nelson X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Mar 2013 07:39:00 -0000 --14dae93a0d95d581d704d82e147e Content-Type: text/plain; charset=UTF-8 On Mar 18, 2013 12:20 AM, "Jan Algermissen" wrote: > > Herbert, > > On 17.03.2013, at 15:49, Herbert van de Sompel wrote: > > > Dear Jan, > > > > In the link relation registry at > > http://www.iana.org/assignments/link-relations/link-relations.xml I > > see several entries that point to versions of Internet Drafts: > > > > - http://tools.ietf.org/html/draft-snell-additional-link-relations-07 > > - http://tools.ietf.org/html/draft-wilde-profile-link-04 > > That is strange - but I guess the idea is to update them, once the specs are done. > Those specs are done really. All they are waiting for is rfc# to be issued. The respective relations were added to the registry per the iana actions step of final publication. - James > Agreed - there is no reason your link relation types could not be defined the same way. > > Having said that, I suggest some corrections to the I-D. > > - Throughout section 2.2 please s/Relation Type/Link Relation Type/ > > - You write that resource MUST/SHOULD include certain Link headers but it is the response entities that you mean, yes? > Can you be more precise, what response entities and which requests you are referring too? Supposedly GET, or? > > - I am not entirely sure whether such things can be constrained - I feel this is an over-specification that goes > beyond HTTP. IOW: I think it is up to the server. > > Can you reword that in a "if you find a link with rel type XY, then ...." fashion? > > @Mark, Julian - what is your take on this? > > > Jan > > > > > > > > If for some reason the same approach can not be followed for the > > Memento relation types, then I can see two alternatives: > > > > (1) Use the version-independent URI of the spec as posted on the Memento site: > > > > http://www.mementoweb.org/guide/rfc/ID/ > > > > The current version of the Internet Draft is always available from > > that URI, and the RFC will eventually be available from there too. > > > > (2) Use the version-independent URI of the spec in the IETF data tracker: > > > > https://datatracker.ietf.org/doc/draft-vandesompel-memento/ > > > > Many greetings > > > > Herbert > > > > On Sun, Mar 17, 2013 at 8:14 AM, Jan Algermissen > > wrote: > >> Hi Herbert, > >> > >> I think we need the reference to be a stable document first. Pointing to a 06-version does not seem to make much sense, IMO. > >> > >> Jan > >> > >> > >> On 04.03.2013, at 01:07, Herbert van de Sompel wrote: > >> > >>> Hi all, > >>> > >>> I would like to request adding the following Relation Types to the Registry: > >>> - "timegate" > >>> - "timemap" > >>> - "memento" > >>> - "original" > >>> > >>> These Relation Types are used in Memento "Time Travel for the Web" for > >>> which a new Internet Draft was just published at > >>> http://www.ietf.org/id/draft-vandesompel-memento-06.txt > >>> > >>> I include the description of each Relation Type below. For > >>> completeness, I also include the meaning of the terms TimeGate, > >>> TimeMap, Memento, Original Resource as introduced in the Memento > >>> specification: > >>> > >>> o Original Resource: An Original Resource is a resource that > >>> exists or used to exist, and for which access to one of its prior > >>> states may be required. > >>> > >>> o Memento: A Memento for an Original Resource is a resource that > >>> encapsulates a prior state of the Original Resource. > >>> > >>> o TimeGate: A TimeGate for an Original Resource is a resource that > >>> is capable of datetime negotiation to support access to prior states > >>> of the Original Resource. > >>> > >>> o TimeMap: A TimeMap for an Original Resource is a resource from > >>> which a list of URIs of Mementos of the Original Resource is > >>> available. > >>> > >>> Greetings > >>> > >>> Herbert Van de Sompel > >>> > >>> ================== > >>> > >>> Relation Type: timegate > >>> > >>> Description: A link with a "timegate" Relation Type is used to point > >>> from the Original Resource, as well as from a Memento associated with > >>> the Original Resource, to a TimeGate for the Original Resource. > >>> > >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt > >>> > >>> Notes: Used in the Memento "Time Travel for the Web" framework. > >>> > >>> ================== > >>> > >>> Relation Type: timemap > >>> > >>> Description: A link with a "timemap" Relation Type is used to point > >>> from a TimeGate or a Memento associated with an Original Resource, as > >>> well as from the Original Resource itself, to a TimeMap for the > >>> Original Resource. > >>> > >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt > >>> > >>> Notes: Used in the Memento "Time Travel for the Web" framework. > >>> > >>> ================== > >>> > >>> Relation Type: memento > >>> > >>> Description: A link with a "memento" Relation Type is used to point > >>> from a TimeGate or a Memento for an Original Resource, as well as from > >>> the Original Resource itself, to a Memento for the Original Resource. > >>> > >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt > >>> > >>> Notes: Used in the Memento "Time Travel for the Web" framework. > >>> > >>> ================== > >>> > >>> Relation Type: original > >>> > >>> Description: A link with an "original" Relation Type is used to point > >>> from a TimeGate or a Memento to its associated Original Resource. > >>> > >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.txt > >>> > >>> Notes: Used in the Memento "Time Travel for the Web" framework. > >>> > >>> ================== > >>> > >>> -- > >>> Herbert Van de Sompel > >>> Digital Library Research & Prototyping > >>> Los Alamos National Laboratory, Research Library > >>> http://public.lanl.gov/herbertv/ > >>> > >>> == > >>> _______________________________________________ > >>> 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/ > > > > == > > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations --14dae93a0d95d581d704d82e147e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mar 18, 2013 12:20 AM, "Jan Algermissen" <jan.algermissen@nordsc.com> wrote:
>
> Herbert,
>
> On 17.03.2013, at 15:49, Herbert van de Sompel <hvdsomp@gmail.com> wrote:
>
> > Dear Jan,
> >
> > In the link relation registry at
> > http://www.iana.org/assignments/link-relations/link-relations.= xml I
> > see several entries that point to versions of Internet Drafts: > >
> > - http://tools.ietf.org/html/draft-snell-additional-link-rel= ations-07
> > - http://tools.ietf.org/html/draft-wilde-profile-link-04
>
> That is strange - but I guess the idea is to update them, once the spe= cs are done.
>

Those specs are done really. All they are waiting for is rfc= # to be issued. The respective relations were added to the registry per the= iana actions step of final publication.

- James

> Agreed - there is no reason your link relation types co= uld not be defined the same way.
>
> Having said that, I suggest some corrections to the I-D.
>
> - Throughout section 2.2 please s/Relation Type/Link Relation Type/ >
> - You write that resource MUST/SHOULD include certain Link headers but= it is the response entities that you mean, yes?
> =C2=A0 Can you be more precise, what response entities and which reque= sts you are referring too? Supposedly GET, or?
>
> - I am not entirely sure whether such things can be constrained - I fe= el this is an over-specification that goes
> =C2=A0 beyond HTTP. IOW: I think it is up to the server.
>
> =C2=A0 Can you reword that in a "if you find a link with rel type= XY, then ...." fashion?
>
> =C2=A0 @Mark, Julian - what is your take on this?
>
>
> Jan
>
>
>
>
> >
> > If for some reason the same approach can not be followed for the<= br> > > Memento relation types, then I can see two alternatives:
> >
> > (1) Use the version-independent URI of the spec as posted on the = Memento site:
> >
> > http://www.me= mentoweb.org/guide/rfc/ID/
> >
> > The current version of the Internet Draft is always available fro= m
> > that URI, and the RFC will eventually be available from there too= .
> >
> > (2) Use the version-independent URI of the spec in the IETF data = tracker:
> >
> > https://datatracker.ietf.org/doc/draft-vandesompel-memento/
> >
> > Many greetings
> >
> > Herbert
> >
> > On Sun, Mar 17, 2013 at 8:14 AM, Jan Algermissen
> > <jan.algermissen= @nordsc.com> wrote:
> >> Hi Herbert,
> >>
> >> I think we need the reference to be a stable document first. = Pointing to a 06-version does not seem to make much sense, IMO.
> >>
> >> Jan
> >>
> >>
> >> On 04.03.2013, at 01:07, Herbert van de Sompel <hvdsomp@gmail.com> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I would like to request adding the following Relation Typ= es to the Registry:
> >>> - "timegate"
> >>> - "timemap"
> >>> - "memento"
> >>> - "original"
> >>>
> >>> These Relation Types are used in Memento "Time Trave= l for the Web" for
> >>> which a new Internet Draft was just published at
> >>> http://www.ietf.org/id/draft-vandesompel-memento-06.txt
> >>>
> >>> I include the description of each Relation Type below. Fo= r
> >>> completeness, I also include the meaning of the terms Tim= eGate,
> >>> TimeMap, Memento, Original Resource as introduced in the = Memento
> >>> specification:
> >>>
> >>> =C2=A0o =C2=A0Original Resource: An Original Resource is = a resource that
> >>> exists or used to exist, and for which access to one of i= ts prior
> >>> states may be required.
> >>>
> >>> =C2=A0o =C2=A0Memento: A Memento for an Original Resource= is a resource that
> >>> encapsulates a prior state of the Original Resource.
> >>>
> >>> =C2=A0o =C2=A0TimeGate: A TimeGate for an Original Resour= ce is a resource that
> >>> is capable of datetime negotiation to support access to p= rior states
> >>> of the Original Resource.
> >>>
> >>> =C2=A0o =C2=A0TimeMap: A TimeMap for an Original Resource= is a resource from
> >>> which a list of URIs of Mementos of the Original Resource= is
> >>> available.
> >>>
> >>> Greetings
> >>>
> >>> Herbert Van de Sompel
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>
> >>> Relation Type: timegate
> >>>
> >>> Description: A link with a "timegate" Relation = Type is used to point
> >>> from the Original Resource, as well as from a Memento ass= ociated with
> >>> the Original Resource, to a TimeGate for the Original Res= ource.
> >>>
> >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.t= xt
> >>>
> >>> Notes: Used in the Memento "Time Travel for the Web&= quot; framework.
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>
> >>> Relation Type: timemap
> >>>
> >>> Description: A link with a "timemap" Relation T= ype is used to point
> >>> from a TimeGate or a Memento associated with an Original = Resource, as
> >>> well as from the Original Resource itself, to a TimeMap f= or the
> >>> Original Resource.
> >>>
> >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.t= xt
> >>>
> >>> Notes: Used in the Memento "Time Travel for the Web&= quot; framework.
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>
> >>> Relation Type: memento
> >>>
> >>> Description: A link with a "memento" Relation T= ype is used to point
> >>> from a TimeGate or a Memento for an Original Resource, as= well as from
> >>> the Original Resource itself, to a Memento for the Origin= al Resource.
> >>>
> >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.t= xt
> >>>
> >>> Notes: Used in the Memento "Time Travel for the Web&= quot; framework.
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>
> >>> Relation Type: original
> >>>
> >>> Description: A link with an "original" Relation= Type is used to point
> >>> from a TimeGate or a Memento to its associated Original R= esource.
> >>>
> >>> Reference: http://www.ietf.org/id/draft-vandesompel-memento-06.t= xt
> >>>
> >>> Notes: Used in the Memento "Time Travel for the Web&= quot; framework.
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>
> >>> --
> >>> Herbert Van de Sompel
> >>> Digital Library Research & Prototyping
> >>> Los Alamos National Laboratory, Research Library
> >>> http://publi= c.lanl.gov/herbertv/
> >>>
> >>> =3D=3D
> >>> _______________________________________________
> >>> 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.g= ov/herbertv/
> >
> > =3D=3D
>
> _______________________________________________
> link-relations mailing list
> link-relations@ietf.org=
> https= ://www.ietf.org/mailman/listinfo/link-relations

--14dae93a0d95d581d704d82e147e-- From mnot@mnot.net Mon Mar 18 18:12:12 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124E821F86C3 for ; Mon, 18 Mar 2013 18:12:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.932 X-Spam-Level: X-Spam-Status: No, score=-105.932 tagged_above=-999 required=5 tests=[AWL=-3.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgubSuc5LLlL for ; Mon, 18 Mar 2013 18:12:11 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 6D76721F86C1 for ; Mon, 18 Mar 2013 18:12:11 -0700 (PDT) Received: from [192.168.1.80] (unknown [118.209.42.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 53AEC509B7; Mon, 18 Mar 2013 21:12:04 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: NEW RELATIONS: timegate ; timemap ; memento ; original From: Mark Nottingham In-Reply-To: Date: Tue, 19 Mar 2013 12:12:00 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4862AA0B-B261-4C1D-A511-12158A78FE58@nordsc.com> To: James M Snell X-Mailer: Apple Mail (2.1499) Cc: "julian.reschke@gmx.de Reschke" , Robert Sanderson , Michael Nelson , link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Mar 2013 01:12:12 -0000 On 18/03/2013, at 6:38 PM, James M Snell wrote: > Those specs are done really. All they are waiting for is rfc# to be = issued. The respective relations were added to the registry per the iana = actions step of final publication. Right. Memento is still in ISE review. Cheers, -- Mark Nottingham http://www.mnot.net/ From algermissen1971@me.com Wed Mar 20 02:29:39 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72DD521F8514 for ; Wed, 20 Mar 2013 02:29:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6gPkzbc10Kky for ; Wed, 20 Mar 2013 02:29:38 -0700 (PDT) Received: from nk11p03mm-asmtp001.mac.com (nk11p03mm-asmtp001.mac.com [17.158.232.236]) by ietfa.amsl.com (Postfix) with ESMTP id B970A21F83EF for ; Wed, 20 Mar 2013 02:29:38 -0700 (PDT) Received: from [10.90.134.89] ([87.253.171.216]) by nk11p03mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MJY00FNDD121O10@nk11p03mm-asmtp001.mac.com> for link-relations@ietf.org; Wed, 20 Mar 2013 09:29:28 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626,1.0.431,0.0.0000 definitions=2013-03-20_03:2013-03-19, 2013-03-20, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1302030000 definitions=main-1303200031 Content-type: text/plain; charset=iso-8859-1 MIME-version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Remarks for draft-wmills-oauth-lrdd-07 From: algermissen1971 In-reply-to: <1361266245.51526.YahooMailNeo@web31805.mail.mud.yahoo.com> Date: Wed, 20 Mar 2013 10:29:27 +0100 Content-transfer-encoding: quoted-printable Message-id: <79DBDFCB-73D3-452D-B5AA-7E627819F510@me.com> References: <1361266245.51526.YahooMailNeo@web31805.mail.mud.yahoo.com> To: William Mills X-Mailer: Apple Mail (2.1499) Cc: link-relations X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2013 09:29:39 -0000 Hi Bill, On 19.02.2013, at 10:30, William Mills wrote: > I agree that they overlap. I'm open to any clear way to represent = this, I chose not to go with a "version" link extension, since it's = incrementally (by that infinitesimal calculus dx) more complicated and = it then requires a registry of constants. >=20 Sorry to be a bit late. After trying, I find no way to propose anything that is better than to = simply enumerate the endpoints as you did. I still do not like the overlap, but the problem is much more inherent = in the way that OAuth 1 and 2 (not) approach discovery and avoid making = use of hypermedia, IMHO. But thats all done now. Hence, from my POV, the I-D is good to go. Jan > Discussion is forward progress, so I'm happy. >=20 > -bill >=20 > From: algermissen1971 > To: "wmills_92105@yahoo.com" =20 > Cc: link-relations =20 > Sent: Tuesday, February 19, 2013 12:01 AM > Subject: Remarks for draft-wmills-oauth-lrdd-07 >=20 > William, >=20 > thanks for incorporating the changes[1]. >=20 > Persionally, I am always trying to avoid semantic overlap between = specs and with that hat on, I still have problems with the various link = relations being tied to specific OAuth versions. >=20 > I'll go through the specific definitions again over the next days to = see if I can sustain my point that, at least for some of them, the = specific OAuth version does not matter but is rather a runtime = capability negotiation issue. >=20 > Please bear with me :-) >=20 > Jan >=20 > [1] http://www.ietf.org/rfcdiff?url2=3Ddraft-wmills-oauth-lrdd-07 >=20