Coordination with ebXML

[Vincent Buller <vincent@and.nl>]

Hello Karl, all,

I wasn't planning -unfortunately- on attending ebXML Vancouver - last year
we had to choose for either OASIS or ebXML to move forward with the address
and profile specification. This has definitely and full-heartedly become
OASIS, also because some expectancy was raised that since ebXML is not just
a friend of OASIS but more something of a 'child', there would be some
inherent coordination in place.

I have spoken briefly to Bob Sutor at XML/One last October about this very
subject, and the message there was that discussion was already going on at
the top level and we could expect an OASIS and ebXML joint communication
about the management of Core COmponents vs. OASIS work.

I have not heard anything since (maybe I've missed something?). I do however
agree with Bob Sutor that the best level this would be handled at is OASIS
level, not individual workgroup level where each workgroup would be
repeating the others' efforts - I noticed the need to coordinate with ebXML
was also mentioned in the recent press-release about the new OASIS "Business
Transactions" committee. I also believe that, with the recently increased
level of actual XML specification work done within OASIS itself, the
coordination with related organizations such as ebXML should be properly
sorted out before it all gets too fuzzy.

I must also observe that with the amount of participation we're having in
CIQ it will be practically impossible to also take other than small
'political' jobs on our shoulders if we wish to do some development.

I am looking forward to hearing everybody's thoughts on this subject!

Best regards,
Vincent



> -----Original Message-----
> From: Karl Best [mailto:karl.best@oasis-open.org]
> Sent: Friday, January 26, 2001 7:51 AM
> To: ciq@lists.oasis-open.org
> Subject: RE: Minutes of the tele-conference CIQ meeting held on 15
> January 2001
>
>
> Vincent:
>
> > I also still believe aligning work
> > with ebXML is very important; i.e. making clear that OASIS
> is already
> > working on a customer profile and making sure this work is not
> > duplicated by
> > the ebXML core components group. Since OASIS and ebXML are related
> > organizations/initiatives, I find this of higher priority
> than cpExchange
> > which has been a difficult effort sofar. Karl, could you create any
> > certainty in this area from an OASIS perspective?
>
> Yes, I believe that coordination with ebXML is a higher priority than
> coordinating with CPExchange. One is friend, the other foe
> :-) Let's make
> sure we're not competing with friends.
>
> Any chance that one of you can attend the ebXML meeting in
> Vancouver the
> week of 12 Feb?
>
> </karl>
> ============================================================
> Karl F. Best
> OASIS - Director, Technical Operations
> 978.667.5115 x206
> karl.best@oasis-open.org  http://www.oasis-open.org
>
>
> > -----Original Message-----
> > From: Vincent Buller [mailto:vincent@and.nl]
> > Sent: Thursday, January 25, 2001 6:08 AM
> > To: 'Ram Kumar'; ciq@lists.oasis-open.org
> > Subject: RE: Minutes of the tele-conference CIQ meeting held on 15
> > January 2001
> >
> >
> > === Please disregard previous mail - this is the full
> version :-) =======
> >
> > Hello Ram, all,
> >
> > thanks for distributing the minutes on short notice.
> However, let's kick
> > some life into this list, as I haven't heard anything since!
> >
> > Ram, I read you updated NAML - would you care to distribute
> the updated
> > version?
> >
> > John, looking forward to the document on security - I hope this
> > will help us
> > in addressing potential questions like the ones that CPExchange
> > appeared to
> > have got from a hyped US senator. I read nothing about
> discussion on this
> > part? Has there been any? I would like to hear what other people
> > think about
> > the time and attention we should spend on this.
> >
> > I am not sure what to read in the bits about how we are
> > progressing with the
> > xNAL specification itself. As I see it we will simply copy and
> > paste the AND
> > GlobalAddress into the Mastersoft NAML to create a
> startingpoint for xNAL.
> > In December Ram expressed the wish to verify, by making a
> > comparison table,
> > that everything expressed in his address format could be
> expressed in
> > GlobalAddress. I myself am confident that this is possible,
> since we *are*
> > processing addresses from all countries that NAML covers within
> > my company.
> > Also, Ram and I have actually compared our DTDs during
> XML2000 and we
> > couldn't find any substantial differences, so for me this chapter
> > is closed.
> > Perhaps Ram could be more specific about the areas that he
> still believes
> > are not covered in GlobalAddress, perhaps by sending some
> examples or
> > sending his current draft comparison table with suspected
> problem areas
> > highlighted?
> >
> > On the other hand I do recognize the need, by the time of
> our first draft
> > xNAL release end of March, for some sample data. This is the
> > timeline I have
> > put forward, and since I am sure you appreciate the effort
> it will take to
> > compile such a sample dataset, this is also the earliest that I
> > can have it.
> >
> > What we talked about at our kickoff meeting is to make an extensible
> > multilevel definition. For example, for Address this would
> mean that one
> > should be able to markup a street as a whole
> (street&premise:"prinses
> > julianastraat 26") or in parts (street:"prinses julianastraat",
> > premise:"26"). This is a next step that we can start discussing now.
> >
> > I am currently converting the GlobalAddress DTD to the
> latest W3C schema
> > definition; this allows us to be more expressive as we discussed in
> > December. Ram, did you look at XML Schema and can you have a go at
> > converting your specification?
> >
> > As for contacts with other organizations: I have a
> tentative meeting date
> > with mr Wandt, which he has to confirm. I also still
> believe aligning work
> > with ebXML is very important; i.e. making clear that OASIS
> is already
> > working on a customer profile and making sure this work is not
> > duplicated by
> > the ebXML core components group. Since OASIS and ebXML are related
> > organizations/initiatives, I find this of higher priority
> than cpExchange
> > which has been a difficult effort sofar. Karl, could you create any
> > certainty in this area from an OASIS perspective?
> >
> > Ram, did you hear anything from the DocBook people on the
> e-mail you sent
> > them?
> >
> > Cheers,
> > Vincent
> >
> >
> >
> > > -----Original Message-----
> > > From: Ram Kumar [mailto:rkumar@msi.com.au]
> > > Sent: Friday, January 19, 2001 2:45 AM
> > > To: ciq@lists.oasis-open.org
> > > Cc: rkumar@msi.com.au
> > > Subject: Minutes of the tele-conference CIQ meeting held
> on 15 January
> > > 2001
> > >
> > >
> > > MINUTES
> > >
> > > Attendees:  John Benett, Karl Best and Ram Kumar
> > > Absentees: Vincent Buller
> > >
> > > Ram has updated the NAML DTD and the document with the minor
> > > changes suggested during the Dec.6 meeting.
> > >
> > > Ram is now creating a table that will consist of NAML
> address elements
> > > and Global address model elements. This will be helpful
> in integrating
> > > the two models.
> > >
> > > The action items from the meeting are as follows:
> > >
> > > 1. Vincent to release an updated version of the AND Global address
> > >     model document as promised in the Dec.6 meeting. This
> document is
> > >     expected to contain many address examples that describe
> > > about the tags
> > >     that are defined in the model. Given that there are not enough
> > > information
> > >     to understand the tags and the address structure in the
> > > current doc,
> > >     the examples will make it easier to understand. Once this
> > > is available,
> > >     Ram will compile the table that matches the address
> > > structures of the
> > >     Global Address and NAML. This table will then be helpful
> > > in integrating
> > >     the two models.
> > >
> > > 2. Vincent to set an appointment with Mr.Wandt of CEN and
> > > discuss about
> > >     their plans of coming up with an XML model for addresses.
> > > We need to
> > >     convince Mr.Wandt's group to work closely with us which
> > > will benefit
> > > each groups.
> > >     This is important.
> > >
> > > 3. Karl is waiting on Vincent to talk to Mr.Wandt before he
> > > can talk to
> > > CPExchange
> > >     group about working closely with CIQ. If we take the
> > > story of CEN's
> > > interest
> > >    in working with us, this will add more value when we sell
> > > our story to
> > > CPEXchange.
> > >
> > > 4. John has collected documents on P3P and other security
> > > standards and will
> > >    provide us a report by the beginning of Feb.2001.
> > >
> > >
> > > NEXT CONFERENCE CALL:
> > >
> > > February 15, 2001 - same time as this month's call.
> > >
> > > Cheers
> > >
> > > Ram
> > >
> >
> >
>