It's still early
morning here, Darrell so it didn't occur to me to note that one
of my goals is to eliminate working drafts from final
specifications.In fact, if things had worked out better, we'd be
including
the current official edxl-ct-v1.0.xsd
after the current working draft is officially transformed to
edxl-ct-csd04.xsd and becomes the current official edxl-ct-v1.0.xsd--to
be used as the imported schema for all updates of our EDXL
Specifications. Unfortunately the work on edxl-ct-v1.0-wd07 is
lagging behind, but we will make the change when we can.
Cheers,
Rex
On 6/12/2018 7:34 AM, Darrell O'Donnell
wrote:
So for clarity - put the CT WD07 document at the
same level of the EDXL-HAVE main XSD, sharing the same
./ImportedSchema folder?
Darrell
O'Donnell, P.Eng.
On Tue, Jun 12, 2018 at 10:03 AM,
rexbroo <
>
wrote:
My
suggestion: A -- pull wd07 separately from its
surrounding structure, and include it and the imported
schema in the folder structure of the EDXL-HAVE-v2.0
package. Unless I'm way off base, it should work with
the ./ImportedSchema schema location of
EDXL-HAVE-v2.0, yes? I am copying this to the RIM SC.,
Elysa and Jeff Waters in case Jeff disagrees.
Cheers,
Rex
On
6/11/2018 11:20 AM, Darrell O'Donnell wrote:
I am looking to close out on this
before my membership dies (13JUN). I just tried to
load in the WD07 document but it's got it's own
./ImportedSchema folder structure. What should we
do there? Choices seem to be:
A. Put EDXL-CT in the same folder as the main
HAVE schema folder.
B. Use a ./ImportedSchema/ ImportedSchema
folder - and duplicate everything (this one
feels whacked).
Darrell
O'Donnell,
P.Eng.
darrell.odonnell@ continuumloop.com
On Tue, May 8, 2018 at
3:36 PM, rexbroo <
>
wrote:
edxl-xAL.xsd:
http://docs.oasis-open.org/eme rgency/edxl-ciq/v1.0/csd04/xsd /edxl-xAL.xsd
edxl-xPIL.xsd:
http://docs.oasis-open.org/eme rgency/edxl-ciq/v1.0/csd04/xsd /edxl-xPIL.xsd
We
still have to vote on making
edxl-ct-v1.0-wd07 the new Committee
Specification, csd04 after which there
will be a similarly official
source
of truth file location like above, but
for the moment we'll have to let that
slide. It would be helpful if I could
get the level of permission necessary to
make the final schema changes
incorporating the new official
edxl-ct-v1.0.xsd which will take place
once the ballot is approved.
I'll
be very sorry to see ya go and will miss
ya very much.
Cheers,
Rex
On
5/8/2018 10:12 AM, Darrell O'Donnell
wrote:
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
Darrell
O'Donnell,
P.Eng.
darrell.odonnell@continuumloop .com
--
Rex Brooks Starbourne Communications Design
Email:
GeoAddress: 1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
Virus-free.
www.avast.com
--
Rex Brooks Starbourne Communications Design
Email:
GeoAddress: 1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
--
Rex Brooks Starbourne Communications Design
Email:
GeoAddress: 1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
