[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Support for External Repository Items
When this Oasis ebXML Registry TC assumed that it would start with the ebXML v1.0 Specifications, did it also assume the requirements that the ebXML specifications were drafted against were also valid? Here is an excerpt from the ebXML Requirements document for registry and Repository: [ebXML Requirements v1.04, 19 March 2001, Section 6.32, Lines 422:425] "...In addition, context with a repository can reference content within another repository. The concept of a single repository is not scalable, nor does it promote the idea of a global web..." If this Oasis ebXML Registry TC assumed these original ebXML Requirements when it assumed the prior work derived from those requirements, then the answer is pretty clear, we should allow this. Were these basic assumptions of a priori requirements agreed to by his group? Joel -----Original Message----- From: Len Gallagher [mailto:LGallagher@nist.gov] Sent: Friday, October 05, 2001 8:41 AM To: regrep@lists.oasis-open.org Subject: Support for External Repository Items Regrep members, Attached is a short (3-page) issue and position paper that addresses the topic of "How should our Registry handle the registration of repository items that do not reside under the control of Registry Services?" One point of view is that all repository items are under the control of the Registry, so we don't have a problem. Another point of view is that we can and should be able to create RegistryEntry instances that describe a repository item that resides elsewhere. The attached 3-page document discusses this issue, evaluates how our Registry specifications handle both of these notions, and states my belief that the Registry specifications should allow registration of external repository items if the Registration Authority wants that to happen. I present the outline of a proposal that would facilitate this capability. I'm making this proposal to the entire Registry team because I think it impacts the deliberations of several of our sub-teams, especially query, external scheme, and cooperating registries. I looked at the use cases under cooperating registries and found that many of them would be satisfied simply by allowing the Registry to register repository items that live elsewhere. I think it's best to let the whole team see the issue up front so that it can be discussed with input from all effected sub-teams at the same time. -- Len ************************************************************** Len Gallagher LGallagher@nist.gov NIST Work: 301-975-3251 Bldg 820 Room 562 Home: 301-424-1928 Gaithersburg, MD 20899-8970 USA Fax: 301-948-6213 **************************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC