Jerome McDonough wrote:
> Ah, but the definitions for dateType are *not* currently being
> brought into the object and event schema through an xs:include, and
> that's what your validator is complaining about. You have two,
> separate global definitions of the same type embedded within two
> schema. When they are 'included' into the master PREMIS schema, they
> conflict, even though they are identical. To avoid this, there has
> to be a single definition of the type which is then brought into the
> object and event schemas via an include statement.
Thanks for the explanation, Jerome - that makes sense now. Nice to have
learned something today! And nice to know Oxygen got it right - I don't
usually doubt it.
Presumably, now that dateType is being exposed as a global definition
(however its implementation's resolved), there's scope for implementors
to redefine it locally? If so, couldn't a few more type definitions be
exposed in the same way (like Event.eventType, which I mentioned a while
back)?
All the best
Richard
--
/
\ Richard M Davis
/ Digital Archives Specialist
\ University of London Computer Centre
/ Tel: +44 (0) 20 7692 1350
\ mailto: [log in to unmask]
/
|