[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-dev] [ann] freebXML CC
As a reminder, the core components uses guide is an unofficial document that has never received a final formal review or approval within CEFACT.
Mark R. Crawford
Senior Research Fellow - LMI XML Lead
W3C Advisory Committee, OASIS, RosettaNet Representative
Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee
Chair - UN/CEFACT XML Syntax Working Group
Editor - UN/CEFACT Core Components
--
LMI Government Consulting
2000 Corporate Ridge
McLean, VA 22102-7805
703.917.7177 Phone
703.655.4810 Wireless
The opportunity to make a difference has never been greater
www.lmi.org
-----Original Message-----
From: Duane Nickull <dnickull@adobe.com>
To: Fred Blommestein, van <f.van.blommestein@berenschot.com>
CC: Robin Cover <robin@oasis-open.org>; Chiusano Joseph <chiusano_joseph@bah.com>; ebxml-dev@lists.ebxml.org <ebxml-dev@lists.ebxml.org>
Sent: Sat Oct 30 03:59:50 2004
Subject: Re: [ebxml-dev] [ann] freebXML CC
I'll check with them and find out where it has gone to. The website was
re-done. Did you check the ISO site?
Duane
Fred Blommestein, van wrote:
>Robin,
>
>The Core Component Primer, or, officially, the Core Components User Guide, can be downloaded from:
>http://www.ecp.nl/ebxml/docs/cc_ug_oct03.pdf
>
>That is the website of the Electronic Commerce Platform in the Netherlands.
>
>Duane, can you inform why the UN has removed this document from its site, or at least hided it so it cannot be found? Thanks.
>
>Fred
>
>
> -----Original Message-----
> From: Robin Cover [mailto:robin@oasis-open.org]
> Sent: Fri 29/10/2004 23:50
> To: Chiusano Joseph
> Cc: ebxml-dev@lists.ebxml.org
> Subject: RE: [ebxml-dev] [ann] freebXML CC
>
>
>
> On Fri, 29 Oct 2004, Chiusano Joseph wrote:
>
> > FYI, Robin Cover has featured this topic on the XML Cover Pages[1], and
> > has included some quotes from this listserv (although they are labeled
> > as being from XML-DEV, not ebXML-dev).
> >
> > [1] http://xml.coverpages.org/ni2004-10-29-b.html
>
> Fixed XML-DEV -->> ebXML-dev, sorry
>
> Any other suggestions for corrections/additions are welcome.
>
> I especially wanted a URL for the Core Components Primer (?)
> and a list of initiatives/standards that have adopted or
> adapted ebXML Core Components.
>
> Cheers,
>
> Robin
>
> >
> > Kind Regards,
> > Joseph Chiusano
> > Booz Allen Hamilton
> > Strategy and Technology Consultants to the World
> >
> >
> > > -----Original Message-----
> > > From: Matthew MacKenzie [mailto:mattm@adobe.com]
> > > Sent: Friday, October 29, 2004 10:19 AM
> > > To: Diego Ballve
> > > Cc: ebxml-dev@lists.ebxml.org
> > > Subject: Re: [ebxml-dev] [ann] freebXML CC
> > >
> > > The ebXML Registry TC defines a SOAP based protocol for
> > > interacting with a standard ebXML registry implementation.
> > > JAXR is not required by the OASIS/ISO ebXML specification.
> > > What you are really saying is that you chose it out of
> > > convenience, which is fine. I was just wondering.
> > >
> > > --
> > > Matthew MacKenzie <mattm@adobe.com>
> > > Sr. Architect, Adobe Systems
> > > http://www.adobe.com/enterprise/
> > >
> > >
> > > I suggest a new strategy, Artoo: let the Wookie win.
> > > -- C3P0
> > > On Oct 29, 2004, at 10:10 AM, Diego Ballve wrote:
> > >
> > > > Matthew MacKenzie wrote:
> > > >> Diego,
> > > >> Quick question: Why did you choose to use the JAXR API, when using
> > > >> the ebXML RS API directly would have afforded you greater
> > > >> interoperability?
> > > >
> > > > Matt,
> > > >
> > > > Answer is simple: at what cost?! JAXR provides a convenient
> > > Java API
> > > > which hides all details of XML, SOAP, XML DSIG signing &
> > > verification,
> > > > SAML SSO. All that, added to the fact that I'm an experienced JAXR
> > > > user (and a bit of developer, too) makes it a very
> > > attractive, hard to
> > > > drop choice. Besides, JAXR is the standard Java API for ebXML
> > > > Registry. It gives me the best interoperability with registries as
> > > > long as language is Java (I expect that it will work with other
> > > > registry/repository standards if they come about). I chose
> > > to go for
> > > > platform independence whereas language independence would probably
> > > > lead to platform specific stuff - which I try to avoid as much as
> > > > possible!
> > > >
> > > > Regards,
> > > > Diego
> > > >
> > > > --
> > > > Diego Ballve
> > > > Digital Artefacts Europe
> > > > http://www.digital-artefacts.fi
> > > >
> > >
> > >
> >
>
> --
>
>
>
>
>-------------
>Dit e-mailbericht en enige bijlage is vertrouwelijk en
>uitsluitend bestemd voor de geadresseerde(n). Indien u niet
>de geadresseerde bent, mag u deze e-mail of enige bijlage niet
>kopieren of aan derden ter inzage geven of verspreiden.
>Indien u deze e-mail per vergissing heeft ontvangen
>verzoeken wij u de afzender ervan onmiddellijk op de hoogte te
>stellen per e-mail en de betreffende e-mail te vernietigen.
>
>This e-mail and any attachment is confidential and may
>contain legally privileged information. If you are not the
>intended recipient, please note that this e-mail or any
>attachment may not be copied or disclosed or distributed to
>others. If you have received this e-mail by error, please notify
>the sender immediately by return e-mail, and delete this message.
>--------------
>
>
>
--
***********
Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
Chair - OASIS eb SOA TC - http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa
***********
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC