It doesn't validate with the version of StylusStudio we use here, but I just downloaded the latest version of SS, and it did validate, so it's a bug in the older version of SS. Thanks for your help and sorry for the faulty report.

On Tue, Aug 19, 2008 at 7:52 AM, Ray Denenberg, Library of Congress <[log in to unmask]> wrote:
I'm not sure I follow, Joe. What's "not happening"?

Are you saying the following won't validate:
---------

<mods xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3 mods-3-3.xsd">
<accessCondition>xyz</accessCondition>
</mods>

-------------

It validates with XMLSpy.

--Ray


----- Original Message -----
From: "Joe Altimus" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, August 08, 2008 6:03 PM
Subject: [MODS] accessCondition element in MODS 3.3 schema


> I've noticed that no older examples of <accessCondition>, containing only
> character data (a string), validate with the MODS 3.3 schema. There is a
> comment in the schema that the redefinition was designed to allow a string
> or <extension> to occur:
>
> <xsd:complexType name="accessConditionType">
> <xsd:annotation>
> <xsd:documentation>506, 540</xsd:documentation>
> </xsd:annotation>
> <xsd:complexContent>
> <xsd:extension base="extensionType">
> <!--  ************************* definition revised in 3.3
> *************************
>                            **   base="extensionType" rather than
> string.  extensionType is **
>                            **  mixed content, and minOccurs=0 was
> added to its definition **
>                            **  so the result is that this definition
> now supports a string (as  **
>                            **  before) or an extension.
>
> but that isn't happening. Can the schema be corrected to work as the
comment
> states?
>
> Joe Altimus
> Arizona State University Libraries
>