Fwd: Re: Adding FreeTextType, AlternateTexctType and LimitedString to edxl-ct-v1.0-wd07 doesn't validate in XMLSpy

Hi Darrell, HAVE SC
listers,
I wanted to let you
know that Jeff solved the enigma I laid at your feet last week,
and we're on track to be able to keep pace with the changes to
EDXL-HAVE-v2.0 in terms of having the correct version of
edxl-ct.-v1.0.xsd available for the final zipped package of HAVE
for last roundup.
Thanks for your help
over this rather tortuous process.
Cheers,
Rex

--------

Forwarded Message

--------
Subject:
Re: Adding FreeTextType, AlternateTexctType and
LimitedString to edxl-ct-v1.0-wd07 doesn't validate in
XMLSpy
Date:
Sat, 21 Apr 2018 11:31:12 -0700
From:
Jeff Waters  <>
To:

Hi, Rex:
  I was able to validate the attached file in Oxygen by
making three changes.  Basically when referencing the
LimitedString as a type, e.g. type= LimitedString , it
needs to be prefaced with a namespace prefix, e.g.
type= ct:LimitedString .  I made two of these changes,
lines 70 and 85, and then also added  ct:  in front of
the AlternateTextType on line 75, and that seemed to
work.  It validated in Oxygen.
  I did try to validate all the other files and ran into
only one issue:
edxl-ext-v1.0.xsd didn't validate due to a bad import.  It's
trying to go up and directory and find a file that isn't
there.
  Hope this helps!
--Jeff
On Fri, Apr 20, 2018 at 6:59 AM,
rexbroo  < 
>
wrote:
Hi Jeff,
The long
subject pretty much says it. I attached the file, and
all its associated schema, including those I need to
drop.
I am working
with it in a folder that includes all imported schema,
so there are no problems from that source. I put extra
linespaces around the added items from edxl-have-v2.0
that the I pushed the TC to approve adding to the next
Committee Specification of edxl-ct. I figured that if
edxl-ct-v1.0-wd06 validated and edxl-have-v2.0
validated and I brought items in from edxl-have-v2.0
unchanged in themselves but with LimitedString first
instead of last, it would validate. It doesn't. I'm
cross-eyed. What am I missing? XMLSpy gives me this:
File
C:OASISOASIS EM
TCEDXLSupportingElements EDXL-CTedxl-ct-v1.0-wd07 edxl-ct-v1.0-wd07.xsd
is not valid.
    'LimitedString' must refer to an existing simple
or complex type.
        Error location: xs:schema / xs:complexType /
xs:sequence / xs:element / @type
        Details
            src-resolve: Value 'LimitedString' of
attribute 'type' doesn't resolve to a type definition.
    'AlternateTextType' must refer to an existing
simple or complex type.
        Error location: xs:schema / xs:complexType /
xs:sequence / xs:element / @type
        Details
            src-resolve: Value 'AlternateTextType' of
attribute 'type' doesn't resolve to a type definition.
    'LimitedString' must refer to an existing simple
or complex type.
        Error location: xs:schema / xs:complexType /
xs:simpleContent / xs:extension / @base
        Details
            src-resolve: Value 'LimitedString' of
attribute 'base' doesn't resolve to a type definition.
Sorry to be a
bother, but you're more expert than I. This is being
brought into edxl-ct to provide the basis for
<comment> and to support multiple languages as
edxl-have-v2.0 does. My goal is to have straightened
out for next week's RIM SC meeting. Any help would be
deeply appreciated. Obviously, I'm no expert with xsd.
Cheers,
Rex

--
Rex Brooks Starbourne Communications Design
Email:  
GeoAddress: 1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670

Virus-free.
www.avast.com
Attachment:
edxl-ct-v1.0-wd07.xsd
Description:  Binary data