[ohf-dev] XDS and ebXML versions: ebXML3.0 or ebXML2.1

[jguerrero@xxxxxxxxxxxx]

Hi all,

I have questions regarding versions of ebXML used by consumer and source
XDS actor.  I read this in ohf-dev list:

*********
* From: Sarah E Knoop <seknoop@xxxxxxxxxx>
* Date: Thu, 18 May 2006 09:28:12 -0700
* Delivered-to: ohf-dev@xxxxxxxxxxx

This is probably what IHE should have done in the first place, because it
allows vendors who implement a Registry to be more flexible in their SQL
implementation.
ebXML 3.0 was not rattified in time for IHE to commit to this last year.
ebXML 2.1 does not have this capability.
The old way of doing queries is implemented and in the process of being
tested.
Timing is really the issue here, along with the fact that now the consumer
uses ebXML3.0 but the XDS Source uses ebXML 2.1.
Not sure what IHE plans to do about this.
Don't think it is a good idea to leave it as such. If IHE makes this move,
I'm inclined to push that everything go to ebXML3.0.
This would potentially have implications on XDS Source and XDS Metadata.
We'll see at the meeting next week.
This functionality is possible to add onto our Consumer, it just won't be
present at the first drop. I'm inclined to wait until the final text has
gone through public comment before adding this functionality



**********

Any news about that?

I know that, by now, the XDS Consumer plugin source code uses ebXML3 and
XDS Source plugin uses ebXML2.1.
So if we are working with an ebXML2.1 registry implementation (like
ebXMLrr) with XDS Registry Initialization metadata, Is posible to make this
registry work together with the OHF client?

Another questions are:

* Is there available any XDS Registry Initialization metadata for ebXML3
registry?
* Is posible to get a ebXML 2.1 version of the OHF XDS Consumer or is not
necessary?


Thanks in advance


..................................................................

J. Andrés Guerrero

COSTAISA SA
Pau Alcover, 33
Dpto. de Estudios
Extensión 743