> From [log in to unmask] Fri Jul 12 16:06 MET 2002
> MIME-Version: 1.0
> Date: Fri, 12 Jul 2002 15:56:24 +0200
> From: =?iso-8859-1?Q?Piccand_R=E9gis?= <[log in to unmask]>
> Subject: Re: Mixing dc qualifier with other namespace's qualifier allowed ?
> To: [log in to unmask]
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from quoted-printable to 8bit by scarlett.mathematik.Uni-Osnabrueck.DE id QAA24843
>
> Hello Roland,
>
> >
>
> > have :
> >
> > <dcmi:relation qualifier="isPartOf"
> > positionInBatch="12">Batch55</dcmi:relation>
>
> What is this expression supposed to assert?
>
> -> this expresses further the relation of the resource with "Batch55". It
> isPartOf Batch55 and is in position 12.
Could you have a resource "Batch59", which is also in position="12" ?
Or ist there an ordered list of resources?
From your schema i just get that Batch55 is a string - why you call it
a resource?
>
>
> >
> > where "qualifier" is of a DCMI namespace and "positionInBatch" is
> originally
> > from a "dcmieav" namespace.
>
> You want attributes called with unqualified (!) names
> for the same (!) element living in different xml-namespaces?
>
> -> yes ... the definition of my "dcmi" schema imports a "dcmieav" schema,
> out of which I pick up qualified types for new qualifiers attributes
> (dcmieav:positionInBatch). Due to the targetNamespace of the schema being
> DCMI, I can use "positionInBatch" qualifier along with other DCMI qualifier.
>
> > However, is this "legal" in a DCMI point-of-view ? Is the mixing of
> > attributes from namespace other than DCMI allowed ?
>
> In which sense "allowed" ?
>
> -> In other words, am I conforming to the DCMI when I use element refinement
> (qualifier) that are not part of the Dublin Core Qualifiers
> (http://www.dublincore.org/documents/2000/07/11/dcmes-qualifiers/)
Sure you can do that - but you shouldn't claim they live in a dc namespace
namespace. "element refinement" is a semantic rather than a syntactic
notion.
It's a different (though important) issue how you inform a receiving application,
that it SHOULD understand a given xml-construction as related to DC/DCQ in
a specific way - or more generally: how a given xml-construction should be interpreted
in terms of metadata vocabularies, which are understood in (a) broader community(ies)
and might be used in services above the level of DC15.
I doesn't seem to me, that an XML schema as such is all what one needs to meet such
objective - [An XSLT is not determined (!) by input/output schema].
Cheers,
rs
>
> > Thanks in advance for any help or pointers,
> > Régis Piccand
> >
> >
>
>
|