Re: [ESDS] Interaction models for Discovery Services

Kary Främling <Kary.Framling@hut.fi> Thu, 10 July 2008 14:01 UTC

Return-Path: <esds-bounces@ietf.org>
X-Original-To: esds-archive@optimus.ietf.org
Delivered-To: ietfarch-esds-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F6BB3A69E1; Thu, 10 Jul 2008 07:01:01 -0700 (PDT)
X-Original-To: esds@core3.amsl.com
Delivered-To: esds@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A5C83A69E1 for <esds@core3.amsl.com>; Thu, 10 Jul 2008 07:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtJZHfT6Ms1m for <esds@core3.amsl.com>; Thu, 10 Jul 2008 07:01:00 -0700 (PDT)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id 385503A6932 for <esds@ietf.org>; Thu, 10 Jul 2008 07:01:00 -0700 (PDT)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtp (Exim 4.54) id 1KGwhs-0006VC-8I; Thu, 10 Jul 2008 17:01:12 +0300
Message-ID: <48761626.3060901@hut.fi>
Date: Thu, 10 Jul 2008 17:01:10 +0300
From: Kary Främling <Kary.Framling@hut.fi>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: "Kenneth R. Traub" <kt@alum.mit.edu>
References: <8438190C-CAE5-4D1F-8FD6-758D7C909DAF@cantab.net><4875FAD4.9010808@hut.fi> <F1E8CE72-929D-408D-BB79-080B636CDCEF@cantab.net> <E4D3C33AACB84BB6A2FCFCE18A6CD6F3@Ulysses>
In-Reply-To: <E4D3C33AACB84BB6A2FCFCE18A6CD6F3@Ulysses>
X-Spam-Checker: TKK/TKO/hutcs/SpamAssassin
Cc: esds@ietf.org
Subject: Re: [ESDS] Interaction models for Discovery Services
X-BeenThere: esds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion of the ESDS \(Extensible Supplychain Discovery Service\)" <esds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/esds>, <mailto:esds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/esds>
List-Post: <mailto:esds@ietf.org>
List-Help: <mailto:esds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/esds>, <mailto:esds-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: esds-bounces@ietf.org
Errors-To: esds-bounces@ietf.org

Thank you for making this clear - it looks like the answer I was hoping 
for!

   Kary

>> ESDS is considering not only Electronic Product Codes (EPC) but more
>>     
> general kinds of identifiers - so any references to 'EPC' or 'EPC
> identifier' could also be interpreted as an individual ID of an object,
> whether expressed as a string, a URN or specifically an EPC URN string.
>
> A small point, but I believe you mean to say "...a URI or specifically an
> EPC URI string."  There's no reason to restrict identifiers to just URNs
> (which are a subset of URIs).
>
> On the other hand, I'm not sure you'd want to allow non-URI strings, as
> you'd have little hope of insuring their global uniqueness.
>
> The correct formulation is probably "absolute URI".
>
> Ken
>
> ---
> Ken Traub Consulting LLC
> +1 (617) 285-4495
> kt@alum.mit.edu
>
>
>   

_______________________________________________
ESDS mailing list
ESDS@ietf.org
https://www.ietf.org/mailman/listinfo/esds