The actual change to
the edxl-have-v2.0.xsd to accommodate the permanently "official"
edxl-ct-v1.0.xsd file url is and will remain: http://docs.oasis-open.org/emergency/edxl-ct/v1.0/csd03/xsd/edxl-ct-v1.0.xsd
so you can go ahead and make that change, too and the new
Committee Specification will eventually be installed at that
url.
It, the permanent url, like those for edxl-ciq and edxl-gsf reflects the latest Committee Specification for those supposedly-always-evolving specifications. They just haven't been used consistently correctly because at various times, different "new" versions were working their ways through the approval process while major specs were being authored and revised. So authors have used those in-process wds rather than the currently "official" "source of truth" "-v1.0.xsd" files at their permanent urls. Someday, we in the RIM really need to write up policy on this clearly, but I'm trying to get the unification done first so people will actually "trust" the official versions and never again will we see a wd in the imports of a spec.
Cheers,
Rex
Folks - what steps do we need to take to move EDXL HAVE 2.0 back to the TC? My (become vague) recollection is that the following needs to happen:
* Alignment with HL7 "front matter"* XSD adjusted to reflect minor changes to EDXL-CT. Where are the "source of truth" files for this? I can make these changes and get them checked into SVN this weekend.
A driver behind my questions is my looming OASIS membership expiry next month. I don't currently plan to renew it.
Any input would be awesome!
Thanks a ton!
cheers,
Darrell
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670