OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Registry Submissions and Queries

To get one approach to how this could work, you might want to take a look at section 3.6.3 of 
the eCo specification which describes how the business registry would work.

In this approach, the only thing that gets put in the registry is the base url to the 
published interface for the business. The published interface to a business registry defines a 
set of queries that can be requested of that registry.

For the case of a particular document which is published by a particular business, you would 
eventually use document and information item registry for that business. The published 
interface defines the query DocumentRegistryGetDocumentTypeRoot which is accessed by appending 
that query to base url for the business registry.


>From: "Petit, John" <jpetit@kpmg.com>
>To: ebXML-Architecture@lists.oasis-open.org
>Subject: Registry Submissions and Queries
>Date: Thu, 30 Mar 2000 14:44:39 -0500
>MIME-Version: 1.0
>I thought through a scenario in which an SME "publishes" its data via ebXML
>registries and repositories. Looking at the architecture described in 0.4, a
>number of questions came up. When a document is published to a registry from
>an SME controlled repository, exactly how much information is sent to the
>registry? Is it just the URL...is it part (or all) of the document? Duane,
>you probably have the answers to these questions, but they are not yet clear
>in the architectural description. 
>Also, what query formats do you see being used? 
>Cheers, John Petit 
>XMLfs Team 
>Office: 970 728 9468 
>Mobile: 312 961 8956 
>The information in this email is confidential and may be legally privileged.
>It is intended solely for the addressee. Access to this email by anyone else
>is unauthorized. 
>If you are not the intended recipient, any disclosure, copying, distribution
>or any action taken or omitted to be taken in reliance on it, is prohibited
>and may be unlawful. When addressed to our clients any opinions or advice
>contained in this email are subject to the terms and conditions expressed in
>the governing KPMG client engagement letter.         
Peter Kacandes

Application Planning, Architecture & Strategy	phone number: 	X36529
WWOPS IT/Supply Chain Management		email:	peter.kacandes@ebay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC