[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Change Proposal and Validation Issues
Hi Everyone I'm forwarding my reply to Jeff below including my comments inline as I worked through this today. I sent this to him with the zip file that resulted from this effort, which resulted in a version of edxl-tep-v1.1-wd06 that validated for me in XML Spy. I wanted to give you an idea of the extent of the changes we have both applied over the course of this work. For RIM SC there are issues we will want to discuss for arriving at a more complete policy for our specifications moving forward. For TEP SC, I wanted you to have the changes which reflect a policy that is evolving, but that which we have had to apply in the changes made thus far to edxl-tep-v1.1 for it to follow our existing policy requiring it to validate in both XML Spy and Oxygen. So hopefully tomorrow I will be able to post the final version for review before our special telecon meeting Friday. Cheers, On 8/1/2018 9:55 AM, Jeff Waters wrote:
I made this change in the test folder where I duplicated the set of files I sent you. I note that this already included the change in edxl-ct-v1.0-wd05 to correct the typographical error in the name of edxl-gsf-v1.0.xsd. This brings up a decision point that I think we'll have to duck for the sake of edxl-tep-v1.1.xsd. We need to have a policy that provides for the use of an internet sources in our schema. For now, under the necessity of time constraints, I stand by using the following suggestion, the same as I stand by making the typographical correction to the out-of-date edxl-ct-v1.0-wd05. For now we need to make this work, but we need to understand that we'll need to revisit tep once the press of time passes. We need to make a policy for this, and there is a lot of weight behind established practice which uses internet sourcing, but that's a conversation to come. I replaced edxl-gsf-base.xsd with commented version in: ÂÂÂ schema\ImportedSchema\edxl-ct-v1.0-csd04, ÂÂÂ schema\ImportedSchema\edxl-ext-v1.0 and ÂÂÂ schema\ImportedSchema\edxl-gsf-v1.0-csd02. Having read this email several times, it seems unlikely that I will attempt to take the four folders of imported schema inside the ImportedSchema folder and condense it into one set of files while changing the schemaLocation for those files every schema where they occur, but... I added xlink.xsd and xml.xsd and deleted xlink-2003-12-31.xsd in ÂÂÂ schema\ImportedSchema\edxl-ciq-v1.0-csd04 and I added xml.xsd in ÂÂÂ schema\ImportedSchema\edxl-ct-v1.0-csd04\ImportedSchema--Note: must determine correct schemaLocation and ÂÂÂ schema\ImportedSchema\edxl-ct-v1.0-csd04\schema\ImportedSchema--Note: must determine correct schemaLocation Agreed. The question is what happens to specifications that use the wrong old versions? I always thought we could change them as we go along reviewing each spec in turn, but the current time constraint with TEP which we were updating for errors unrelated to these imported schema changes shows us that the idea of a slow, measured approach just isn't what the universe has going on in real time. I'm concerned that just the change to edxl-ct-v1.0.xsd is going to throw us off if we make this change to one single set of imported schema because it specifies its imported schema to be in its own ImportedSchema folder one level further down in the folder structure... I just ran into that the first time I tried to eliminate the edxl-ct-v1.0-csd04 folder to put edxl-ct-v1.0.xsd in ImportedSchema. It's a dilemma I hope you can find a way to fix. Attempting to do this, I placed edxl-ct-v1.0.xsd and edxl-ext-v1.0.xsd in the schema folder so that their relative schemaLocations i.e. ImportedSchema would validate. I changed the schemaLocation for edxl-ext-v1.0.xsd in edxl-tep-v1.0-wd06.xsd to "./edxcl-ext-v1.0.xsd" and I eliminated edxl-ct-v1.0-wd05.xsd. And it validated. All files validated in XMLSpy, so I hope it also validates in Oxygen. I sorta don't believe it, but I gotta have my nap now. Cheers, Rex
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]