[ESDS] Identifiers in Discovery Service

Ali Rezafard <arezafar@ca.afilias.info> Fri, 29 August 2008 16:48 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 1E2DA28C111; Fri, 29 Aug 2008 09:48:46 -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 B4B9628C111 for <esds@core3.amsl.com>; Fri, 29 Aug 2008 09:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.665
X-Spam-Level:
X-Spam-Status: No, score=-3.665 tagged_above=-999 required=5 tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, 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 zqONchjYHYKF for <esds@core3.amsl.com>; Fri, 29 Aug 2008 09:48:43 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id A096C3A69FA for <esds@ietf.org>; Fri, 29 Aug 2008 09:48:43 -0700 (PDT)
Received: from bmp-336-ms506.wa.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <arezafar@ca.afilias.info>) id 1KZ79L-0001Rf-5Z for esds@ietf.org; Fri, 29 Aug 2008 16:48:39 +0000
Received: from vgateway.libertyrms.info ([207.219.45.62] helo=[172.16.16.149]) by smtp.afilias.info with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <arezafar@ca.afilias.info>) id 1KZ79K-0003lJ-81 for esds@ietf.org; Fri, 29 Aug 2008 16:48:38 +0000
Message-Id: <579F81EE-77D2-465D-8EDD-54D738CA8810@ca.afilias.info>
From: Ali Rezafard <arezafar@ca.afilias.info>
To: esds@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 29 Aug 2008 12:48:41 -0400
X-Mailer: Apple Mail (2.926)
Subject: [ESDS] Identifiers in Discovery Service
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: esds-bounces@ietf.org
Errors-To: esds-bounces@ietf.org

Dear ESDS members,

The EPCglobal Data Discovery Joint Requirements Group is currently  
collecting
enduser requirements for Discovery Services.  One of the topics is the  
kind of
identifiers that should be supported in a future standard protocol for
Discovery Services.  ( It is safe to assume that an EPCglobal standard  
for
Discovery Services will at least support EPC identifiers in URI  
format, but
maybe members of the ESDS community have some additional requirements. )

We would therefore like to take this opportunity to reach out to the  
whole ESDS
community to ask you for your views (particularly views from endusers)  
about
the kinds of identifiers that you would wish Discovery Services to  
support.
Could you please reply to the questions below with as much detail as  
possible
and send the replies as soon as possible to the ESDS mailing list, so  
that
these could also be considered as an external input to the EPCglobal  
Data
Discovery JRG from the ESDS community?

Q1.  Which identifiers do you plan to use with Discovery Services?   
Please
provide details of the name of the coding scheme, name issuing  
authority and
format of the identifier (e.g. number of characters, whether numeric or
alphanumeric)  and also indicate what kind of object it is used to  
identify
(e.g. pharmaceuticals, shipping containers, apparel, airline baggage,  
cattle,
etc.)

Q2.  Would you intend to use identifiers that are globally unique  
(e.g. URIs)?
What type of identifiers do you currently use?  Do all of your trading  
partners
use the same standard?

Q3.  Are there standardized business uses within your industry when  
the same
identifier might be used within the same community to refer to a  
different
object (e.g. at a later point in time) ?

Q4.  Does your community already have or have they discussed the use  
of a
dedicated URI prefix for the identifiers you use (could be a URN  
prefix or even
an URI prefix beginning http:// )  ?

We welcome any additional use case documents for how your company /  
industry
sector or community might use Discovery Services.

Please provide this input by September 15, 2008.

Thanks,
Ali Rezafard

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