RE: [regrep] V3 Proposal: Namespace Manager Function

["CHIUSANO, Joseph" <JCHIUSANO@lmi.org>]

Title: RE: [regrep] V3 Proposal: Namespace Manager Function

Joel,

 

Definitely as an adjunct.  A namespace cognizant Content-based query capability would be a great approach.

 

Joe

**************************************************************************
  Joseph M. Chiusano
  Logistics Management Institute
  2000 Corporate Ridge
  McLean, VA 22102
  Email: jchiusano@lmi.org
  Tel: 571.633.7722
**************************************************************************

-----Original Message-----
From: Munter, Joel D [mailto:joel.d.munter@intel.com]
Sent: Tuesday, January 29, 2002 11:21 AM
To: 'regrep@lists.oasis-open.org'
Subject: RE: [regrep] V3 Proposal: Namespace Manager Function

Joe,

You offer a valid Use Case.  Are you proposing the Namespace Manager Functionality as an alternative to Content Based Queries?  Or just as an adjunct to it?  From FN's recent comments and my own understanding, it appears as though, you will satisfy your "customers" requests if a namespace cognizant Content-based query capability is introduced into the tools and/or into the specifications themselves.

Joel

 

-----Original Message-----
From: CHIUSANO, Joseph [mailto:JCHIUSANO@lmi.org]
Sent: Tuesday, January 29, 2002 9:13 AM
To: 'regrep@lists.oasis-open.org'
Subject: RE: [regrep] V3 Proposal: Namespace Manager Function

Farrukh, that is correct - thanks for the clarification.

Here is a more specific example of what I believe is needed:
Suppose a schema (using W3C Schema format as an example) with the following root element is submitted to the registry (note the target namespace http://www.acme.org/invoices):

<schema xmlns:xsd="<http://www.w3.org/2000/08/XMLSchema>"
               xmlns:inv="<http://www.acme.org/invoices>"
               xmlns:tmp="<http://www.acme.org/temp>"
               targetNamespace="<http://www.acme.org/invoices>">

Suppose that the schema contains some constructs like the following that are in the http://www.acme.org/invoices namespace:

<inv:element name="InvoiceNumber" type="InvoiceNumberType"/>

<inv:element name="InvoiceDate" type="xsd:date"/>

Suppose also that the http://www.acme.org/temp namespace declared above is a "temporary" namespace to which new constructs should be added in a given time period (perhaps between schema reviews); therefore, there may be constructs such as the following:

<tmp:element name="NewInvoiceID" type="tmp:InvoiceIDType"/>

The Namespace Manager proposal calls for the first 2 elements above to be associated within the registry with the http://www.acme.org/invoices namespacem and the 3rd element above to be associated with the http://www.acme.org/temp namespace.  This would allow Acme to (for instance) determine at a review time all of the constructs associated with the http://www.acme.org/temp namespace (i.e. all constructs that should be reviewed).

This is just one simple case where I believe this functionality could be useful.  I am hearing clients express a need for this type of functionality more often every day.

Regards,
Joe

<fin:BuyerParty>
<FirstName>...</FirstName>
<LastName>...</LastName>
...more information...
</fin:BuyerParty>

> **************************************************************************
>   Joseph M. Chiusano
>   Logistics Management Institute
>   2000 Corporate Ridge
>   McLean, VA 22102
>   Email: jchiusano@lmi.org
>   Tel: 571.633.7722
> **************************************************************************
>

-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
Sent: Tuesday, January 29, 2002 10:58 AM
To: David RR Webber - XMLGlobal
Cc: CHIUSANO, Joseph; 'regrep@lists.oasis-open.org'
Subject: Re: [regrep] V3 Proposal: Namespace Manager Function

David,

I think, what Joe is looking for is ability to query based on the content and
not the metadata. These content based queries would key off things like
namespace declarations and qualifiers within qualified names. This cannot
*ever* be done with Filter or SQL queries without support for content based
queries. Content based queries would handle this quite well actually.

David RR Webber - XMLGlobal wrote:

> Message text written by "CHIUSANO, Joseph"
> >
> Please tell me if I am missing a section that references the classification
> and query of content within Registry Objects.  I believe our current
> registry functionality does not get down to the level required for the
> Namespace Manager proposal.
> <<<
>
> Joe,
>
> The filtered queries will work against any content stored within
> the registeredobject properties.
>
> DW.
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

--
Regards,
Farrukh