> From [log in to unmask] Fri Jun 7 13:13 MET 2002
> MMDF-Warning: Parse error in original version of preceding line at
> lamin.ukoln.ac.uk
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
> Importance: Normal
> Date: Fri, 7 Jun 2002 12:14:25 +0100
> From: Pete Johnston <[log in to unmask]>
> Subject: Re: Comments on Guidelines for implementing DC in XML
> Comments: To: Hoylen Sue <[log in to unmask]>
> To: [log in to unmask]
>
>
> > 1. Rec 2: should use XML Namespaces to uniquely identify DC properties
> >
> > Since these are guidelines, different implementations may
> > choose to define their XML constructs differently for the
> > same DC property. This will cause problems for tools
> > expecting that an XML Namespace corresponds to exactly one
> > XML Schema definition.
> >
> > For example, one implementation may use:
> >
> > <metadata1 xmlns:dc="http://purl.org/dc/elements/1.1/">
> > ...
> > <dc:identifier>http://example.org/foobar</dc:identifier>
> > ...
> > and they have defined in an XML Schema that dc:identifier
> > is a URI.
> >
> > Someone else uses this implementation
> >
> > <metadata2 xmlns:dc="http://purl.org/dc/elements/1.1/">
> > ...
> > <dc:identifier>335-300-323-3</dc:identifier>
> > ...
> >
> > and they have defined in an XML Schema that dc:identifier
> > is a xsd:string with some pattern facet.
> >
> > Both would satisfy the guidelines, but will cause problems
> > for an integration tool that deals with both formats, since
> > it will see two different XML Schema definitions for the same element.
> >
> >
How you will prevent this to happen using xml-schema technology?
rs
|