[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] RE: EDXL-HAVE spec questions
I'm afraid that as TC Administrator I must jump in here. There were no changes made to the schema as part of the Errata (that is, no new copy of schema files were delivered as part of the errata review or called out in the review notice); in fact, changing the schema would, in the vast majority of cases, be a substantive change and therefore require a new version of the specification be produced, rather than an errata. Examples are non-normative; the schema itself was not incorporated into the specification, so only the standalone version exists. Whatever changes you make and deliver it must be noted that they are not in conformance with the specification as it currently exists, but that (hopefully) the TC will be taking the necessary action to rectify the problems that have been discovered. Regards, Mary Mary P McRae Director, Standards Development Technical Committee Administrator OASIS: Advancing open standards for the information society email: mary.mcrae@oasis-open.org web: www.oasis-open.org twitter: @fiberartisan #oasisopen phone: 1.603.232.9090 Standards are like parachutes: they work best when they're open. On Mar 1, 2010, at 9:41 AM, ltincher@evotecinc.com wrote: > I am not at a computer right now - but I cannot stress enough that this is > NOT about the examples. The SChema no longer allows Triage Codes the way > they are outlined in the spec.... > > Thanks, > Lee > >> Elysa, This illustrates why it is a very bad idea to put example XML in >> the specification. Sigh. OASIS needs to stop doing this - and make >> examples external to the document - in the same way as XSD artifacts are. >> Please tell them to go with what the xsd Schema is telling them the XML >> should be - and NOT the specification examples. On their second point - >> Bed capacities - I too had puzzled over a good way to use this. I agree >> with their call to use only BedType and ignore SubCategoryBedType. It >> may help them to quickly load the EDXL schema into the CAM toolkit >> (sourceforge.net/projects/camprocessor) and then generate XML examples and >> documentation - so they can construct the exchange XML that they need. >> ===================================================== "It only allows >> zero or more elements, followed by zero or more elements, followed by >> zero or more elements. >> >> I can't figure out how to properly represent or interpret bed capacities >> in this structure. Can you advise on the correct method? If it is true >> that this just doesn't work as intended, should we decide to use only and >> avoid the use of in the EDXL-HAVE Haiti Profile?" >> Thanks, DW -------- Original Message -------- >> Subject: Re: [emergency] RE: EDXL-HAVE spec questions >> From: Elysa Jones >> Date: Mon, March 01, 2010 8:29 am >> To: "Lee Tincher" ,"'Ka-Ping Yee'" >> , "'Bill Lang'" >> Cc: "'Roni Zeiger'" , "'Martin Omander'" >> , ,"'Gusty, Denis'" >> , "'William Kalin'" >> >> Sukumar, as editor of HAVE, can you respond to this ASAP? I'm less >> concerned about "process" at this time than getting these folks what they >> need to be able to exchange HAVE messages in Hati. Please respond. Elysa >> >> At 06:14 AM 3/1/2010, Lee Tincher wrote: >> >> Ka-Ping, >> >> You are correct in all points on the new Errata. I have been in contact >> with OASIS to get this clarified/fixed ASAP. The PR4 errata does not have >> many of these errors (but has some other ones)Â… >> >> All – we need this clarified as soon as we can – this is excessively >> important to the success of HAVE in the Haiti response. >> >> Thanks, >> Lee >> >> Better to write for yourself and have no public, than to write for the >> public and have no self. - Cyril Connolly >> >> From: Ka-Ping Yee [ mailto:kpy@google.com] >> Sent: Monday, March 01, 2010 5:27 AM >> To: Lee Tincher; Bill Lang >> Cc: Roni Zeiger; Martin Omander >> Subject: EDXL-HAVE spec questions >> >> Hello Lee, >> I've run into a couple of problems with the EDXL specification, and was >> hoping you could help out? >> >> This is the document I'm using: >> http://docs.oasis-open.org/emergency/edxl-have/os/emergency_edxl_have-1.0-spec-os.pdf >> >> (This is the link listed at >> http://www.oasis-open.org/specs/index.php#edxlhave.) >> >> And this is the XSD schema I'm using: >> http://docs.oasis-open.org/emergency/edxl-have/os/edxl-have-os.xsd >> >> >> >> First, a few things that look like simple typos in the EDXL-HAVE example >> document (Appendix A): >> >> 1. The element seems to be in the wrong order. According to the schema, >> it seems it should appear between and , not after . Can you confirm? >> >> 2. The example has a element, but there is no such XML element in the >> schema. According to the schema, it seems that and should be immediate >> children of . Can you confirm? >> >> 3. The example has a element, but there is no such XML element in the >> schema. According to the schema, it seems that and should be immediate >> children of . Can you confirm? >> >> 4. The example has a element, which I assume is a typographic error and >> should be . Can you confirm? >> >> >> Second, though, a more concerning problem with the BedCapacity section >> (Section 3.2.4): >> >> The text, and example 1, suggest that the element should contain a (, ) >> pair, followed by any number of (, ) pairs. >> >> However, example 1 doesn't validate. The XSD schema doesn't allow for >> this structure; it only allows zero or more elements, followed by zero or >> more elements, followed by zero or more elements. >> >> I can't figure out how to properly represent or interpret bed capacities >> in this structure. Can you advise on the correct method? If it is true >> that this just doesn't work as intended, should we decide to use only and >> avoid the use of in the EDXL-HAVE Haiti Profile? >> >> >> >> Many thanks! >> >> >> >> ­ Ping >> Technical Lead, Google Person Finder >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> --------------------------------------------------------------------- To >> unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]