Hi Everyone,
This is a reminder that we have our regularly scheduled telecon meeting tomorrow at 11:00 a.m. EDT. I'll remind us all again tomorrow, but I have an agenda issue:
I've been working on
fixing up the last changes to the schema of edxl-tep-v1.1-wd06
and I fell into a rabbit hole where tep1.1 uses
edxl-ct-v1.0-wd05 even though we just published
edxl-ct-v1.0-csd04 (way past wd05 and used for
edxl-have-v2.0-another time constrained challenge).
However, I don't want
to try and get into how edxl-tep-v1.1 uses edxl-ct-v1.0-wd05 in order to bring
edxl-tep-v1.1 current. Tep-v1.1 uses edxl-ct-v1.0-wd05 in conjunction
with edxl-ext-v1.0Â in ways I/we don't have the time to
understand, but edxl-ct-v1.0-wd05 has an error that prevents the
package for edxl-tep-v1.1 from validating and only needs to
change the wrong citation of edxl-gsf-v1.0 as edxl-gsf.v1.0 in
the schema.
So I want to hear opinions on making this typographic change without a whole new process for correcting an out-of-date spec with such an error. This all happened long before we tightened up our policy on imported schema and having specifications validate in both XML Spy and Oxygen. I think I can still get the edxl-tep-v1.1 package validating by Friday's still-to-be-scheduled TEP SC meeting.
Cheers,
Rex
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670