Excellent, Jeff,
We will incorporate this change in the 15-day Puboic Review that is upcoming. I'm glad it is such a slight change.
Since this was also the case with the TEP schema set, I should have caught it.
Thanks again,
Rex
Hi, Rex:
 I made two changes to get all the schema to validate:(1) I moved edxl-ext-v1.0.xsd up a directory (out of ImportedSchema and into the main Schema directory)(2) I changed the import statement of edxl-ext-v1.0.xsd inside of the edxl-have-v2.0-wd04.xsd schema
ÂÂ (line 16) to read:schemaLocation="./edxl-ext-v1.0.xsd"/>
The problem was that the edxl-ext-v1.0.xsd (in the ImportedSchema subdirectory) was trying to import edxl-ct-v1.0.xsd (which was in the main schema directory) as if it was in the local directory, and it couldn't find it since those two files weren't in the same directory, so it didn't validate. So I moved edxl-ext-v1.0.xsd up a directory. At first, I thought I would move edxl-ct-v1.0.xsd down into the ImportedSchema subdirectory instead, but that didn't work, since it imports xPIL, xAL and gsf, and it's looking for those in the ImportedSchema subdirectory. So I would have had to change three import statements instead of just changing one import statement the other way. Also I looked to see how we had done it with SitRep, and in that case we had moved edxl-ext-v1.0.xsd up also.
--Jeff
On Mon, Aug 13, 2018 at 5:15 PM rexbroo <rexb@starbourne.com> wrote:
Hope you can get to this, Jeff,
Please see if yu can get the HAVE 2.0 schema package to validate in Oxygen. I downloaded a trial version and was unable to load edxl-ct-v1.0.xsd, even though it is located in schema folder along with main schema.
I didn't discover it until late afternoon.
Rex
-------- Forwarded Message --------
Subject: Re: Where we stand with joint HL7/OASIS Announcement at BoF Date: Mon, 13 Aug 2018 17:09:52 -0700 From: rexbroo <rexb@starbourne.com> Reply-To: rexb@starbourne.com To: Elysa Jones <elysajones@yahoo.com>, Scott M. Robertson <Scott.M.Robertson@kp.org>
Hi All,
I didn't get to this until late afternoon. Sorry. If Jeff could see if he can get it to validate in Oxygen before we push it thru the TC, we'd be appreciative.
I just uploaded a zip package for EDXL-HAVE-v2.0-WD04.
Scott should check the prose document to be sure it is correct.It is the one he uploaded back in February. I noticed that the footer has the wrong date, but because I'm not sure what else needs to be corrected at the same time we get ok for Notices, Copyright, Logo issues settled, I left it as is. I worked on the schema last week after I got TEP validated and I have revalidated in XMLSpy again today. However I could not get it to validate in my trial version of Oxygen. It is just the same old issue with schemaLocation of ImportedSchema, but I don't have the skill necessary to properly identify why it isn't validating in Oxygen.
IF everyone wants to go ahead and call a special meeting tomorrow, RIM SC and Adoption TC meetings can be postponed. Just be aware that there will be changes to the prose document.
Elysa, I leave it to you to call a special meeting if you think that's best.
Cheers,
Rex
On 8/13/2018 1:45 PM, Elysa Jones wrote:
If we could put the document out for final TV review ASAP we can call a meeting within a day for a vote. Besides us it will only be Gary and Tim that have current voting permission.
Sent from Yahoo Mail for iPhone
On Monday, August 13, 2018, 3:31 PM, Scott M. Robertson <Scott.M.Robertson@kp.org> wrote:
If I understand correctly, the first thing needed is to have the TC vote on moving forward with publication? An emergency meeting as soon as possible is then necessary. Is it appropriate to call a meeting with a 1 day notice?
Â
I will send the rest of my response in another message. I think the meeting issue should not wait while I craft my comment and questions on the rest.
Â
Â
Scott M Robertson
Principal Technology Consultant
PharmD, RPh, FHL7, GISP, CISSP
Â
Kaiser Permanente
Technology Risk Office | Health IT Strategy & Policy
310-200-0231 (office)----------
kp.org/thriveÂ
From: elysajones@yahoo.com <elysajones@yahoo.com>
Sent: Sunday, August 12, 2018 5:34 PM
To: rexb@starbourne.com; Scott M. Robertson <Scott.M.Robertson@kp.org>
Subject: FW: Where we stand with joint HL7/OASIS Announcement at BoF
Importance: HighÂ
Caution: This email came from outside Kaiser Permanente. Do not open attachments or click on links if you do not recognize the sender.
After talking with Dee on Fri, she gathered the following details of how we go forward. I guess we can do the 15-day review without the Notices section being finalized.Â
Â
Iâm concerned about HL7 having to update the MOU. I do not understand the âforkingâ concern when there is no equivalent document in HL7. The staff has been very reluctant to âendorseâ any other SDO spec. I just hope they donât back out.
Â
It sounds like they are waiting for the TC to act on a review and vote for CSD and CSPRD-15 day. We donât have a meeting scheduled for 8/14 but could call a special meeting for this purpose if you guys agree.
Â
Thoughts?
Elysa
Â
From: Dee from OASIS <dee.schur@oasis-open.org>
Sent: Saturday, August 11, 2018 8:57 AM
To: 'Elysa Jones' <elysajones@yahoo.com>
Subject: Where we stand with joint HL7/OASIS Announcement at BoF
Importance: HighÂ
Elysa,
Does this help at all?
Let me know if you want me to do anything at this point.
Best,
dee
Â
Â
Â
Â
Â
Â
On Fri, Aug 10, 2018 at 3:50 PM, Paul Knight <paul.knight@oasis-open.org> wrote:
Hi all,
Â
To clarify a bit (as I understand it):
ÂÂ PAUL has been cleared to start the PR (15-day review), if he hasn't already done so.Â
I am ready to get the document sent out for PR, AFTER the TC reviews and votes to submit it for PR (likely at the TC meeting next Tuesday, August 14).ÂI'll have things ready to plug together quickly after the TC acts.
Â
At this point we don't have an approved document or an approval date - both are needed to start the PR.
Â
As shown in the EMTC minutes for their August 7 meeting:
EDXL Hospital Availability Exchange (HAVE) SC. Awaiting OASIS agreementon finalizing ``Notices'' section then we can then begin final reviewinternally before an expected 15-day public review.I've also confirmed this with email to Elysa, Rex, Scott Robertson, and Beth Pumo (on August 8). (cc: Jamie, Scott)
Â
But not to worry -Â
The timeline looks good:Â (as long as no Material changes are needed due to PR comments)
Â
- start PR - Aug. 15
- finish PR - Aug. 30
- wait 7 days if any comments are received - Sept 6? - (potential non-Material edits can occur during Aug 31-Sept 10 if needed)
- start CS ballot - likely after TC meeting Sept 11 - say Sept 12
- finish CS ballot - Sept 19
- publish CS - Sept 20 or 21
Â
ÂBest regards,
Paul
Â
On Fri, Aug 10, 2018 at 5:10 PM, Jamie Clark <jamie.clark@oasis-open.org> wrote:
Hello Dee and Jane.
(FYI Chet's out until next week.)
I'm sure you read the longer answer about EDXL-HAVE, which I already provided to Elysa, below.
Here's a "TL;DR" re-cap, with names in CAPS:
Â
NOW
- PAUL has been cleared to start the PR (15-day review), if he hasn't already done so.
- As soon as he does, JAMIE will send a confirming email to HL7 about all the logo and TM use that our TC says is OK with HL7.
NEXT ~15 DAYS
- ELYSA and SCOTT R and the TC will respond to the RE as usual.
- ELYSA and SCOTT R will ping their HL7 counterparts to make sure they have a shot at the review, if they have any more tweaks.
- JAMIE will send a proposed MoU edit over to HL7 to address the forking issue. (And disclose to LAURENT and the BOARD.)
NEXT ~45 DAYS AFTER THAT
- ELYSA and SCOTT R and the TC will take whatever other steps after the PR are needed to get to their final CS by October. (The usual TC Process requirements.)
- LAURENT will sign our proposed non-forking amendment to the MoU for sharing with HL7 and the BOARD.
- JAMIE and CHET will confirm whether we have HL7's OK and the non-forking MoU amendment, by that same October date. (Board's policy on submissions).ÂÂ
Basically, by deciding to do a CS shared with HL7, rather than a CN, EMTC triggered the additional needs for the MoU amendment and joint publication permission. As I told Elysa, that's fine; it just wasn't what Chet and the original MoU were expecting. Scott R did share a very brief "it's OK" e-mail from Karen at HL7, but we need a bit more than than to finalize it all.Â
Â
EMTC also always retains the right to publish their doc separately as OASIS ... but if the TC wants to take a flyer on the joint permission stuff being finalized, with a joint document done by the time of the "cooperation announcement," that's certainly their right. Another alternative for them would be to run a ballot approval of both versions (OASIS+HL7, and just OASIS) so that they are guaranteed to have something approved by October whether or not HL7 comes through. But that's EMTC's decision.ÂÂÂ
.Â
Cordially Jamie
James Bryce Clark, General Counsel
OASIS: Advancing open standards for the information society
https://www.oasis-open.org/staff
EU Commission 2018 Rolling Plan for Open ICT Standards: http://j.mp/EUstds2018Next OASIS/World Bank Borderless Cybersecurity conference, October 2018: https://us18.borderlesscyber.org/en/
Â
Â
On Fri, Aug 10, 2018 at 1:39 PM, Dee from OASIS <dee.schur@oasis-open.org> wrote:
Hi Jamie, Paul and Chet,
Â
I just spoke with Elysa and we need your help. I am not certain what needs to be done at this point and who needs to do it (TC, HL7, OASIS?) Âto move forward with the joint press release which we need to make before the HAVE BoF on 2 October, see link below:
Â
https://www.eventbrite.com/e/bridging-the-gap-part-2-hl7oasis-advancements-in-emergency-continuity-of-care-tickets-48747729772. We are announcing our cooperation at this event.
Â
If one of you can clearly outline exactly what needs to be done and who needs to do it, that would be really useful.
Â
Thank you,
dee
Â
Â
Â
Dee Schur
Senior Manager, Development & Advocacy
OASIS | Advancing open standards for the information societyÂ
+1.781.425.5073 x211 (Office) | +1.941.321.6733 (Cell)
http://www.oasis-open.orgÂ
Borderless Cyber 2018, 3-5 Oct, Washington, D.C.
Organized by The World Bank, OASIS, and Georgetown UniversityÂ
Â
NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670