Re: [regrep-semantic] MetaMatrix and ebXML Registry

["David RR Webber" <david@drrw.info>]

John,

TopQuadrant have also looked at the OASIS BCM
work and how that potential fits.

All this work is definately in the frame for our use
cases.  I'm comfortable that we will be enabling
vendors to use ebXML registry to support their
technology offerings here.

Has anyone from TopQuadrant expressed an
interest in our SCM work already?

Thanks, DW

----- Original Message ----- 
From: "John Gillerman" <john.gillerman@sisconet.com>
To: "Registry TC - SCM SC" <regrep-semantic@lists.oasis-open.org>
Sent: Sunday, February 22, 2004 1:21 PM
Subject: RE: [regrep-semantic] MetaMatrix and ebXML Registry


> Don't know if people have seen this already, but it seems relevant to the
> discussion of integration of EII tools.
>
> -----Original Message-----
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> Sent: Thursday, February 19, 2004 3:41 PM
> To: carlmattocks@checkmi.com
> Cc: Registry TC - SCM SC
> Subject: Re: [regrep-semantic] MetaMatrix and ebXML Registry
>
>
> Carl Mattocks wrote:
> >
> > We at CHECKMi call the semantic structure that supports the interaction
of
> > many different  registries / repositories / etc. a 'Compendium'.
> >
> > Lat time I took an in depth look at MetaMatrix it did not have an XML
> > interface
>
> [JMC] That has since changed. See p.2, top right of [1]: "SOAP API. Web
> services can submit queries to the MetaMatrix Server through the SOAP
> API. The result is returned as an XML document compliant to the XML
> Schema chosen for the requesting service."
>
> [1] http://www.metamatrix.com/datasheets/MetaMatrixServer.pdf
>
> > and its Metabase Schema /RIM was not public.
>
> [JMC] It appears that that is still the case. I'm attributing this to
> intel prop.
>
> Joe
>
> > <quote who="Chiusano Joseph">
> > > Q: How can our SCM-enabled ebXML Registry interact with an Enterprise
> > > Information Integration (EII) product such as MetaMatrix MetaBase [1]?
> > >
> > > A: I believe that such a product could interface with SCM-enabled
ebXML
> > > Registry by treating the Registry as an "extension" of its native
> > > metadata repository (see p.4 of[1], top left, just above header
> > > "Information Integration Through Metadata"). Operations (such as
> > > queries) that interact with its own native metadata repository can
then
> > > virtually include an SCM-enabled ebXML Registry, for an overarching
> > > "virtual operation" that spans repositories.
> > >
> > > And the best part - the product could use its own EII capabilities to
> > > achieve this seamless integration.
> > >
> > > Thoughts?
> > >
> > > Joe
> > >
> > > [1] http://www.metamatrix.com/whitepapers/eiiwhitepaper.pdf
> > >
> >
> > --
> > Carl Mattocks
> >
> > co-Chair OASIS ebXMLRegistry Semantic Content SC
> > CEO CHECKMi
> > v/f (usa) 908 322 8715
> > www.CHECKMi.com
> > Semantically Smart Compendiums
> > (AOL) IM CarlCHECKMi
>