[eml-dev] reusing EML elements out of context

Matt Jones jones at nceas.ucsb.edu
Wed Jul 21 23:26:27 PDT 2010


Yeah, you just need to import and use the ResponsibleParty field as Ben
suggests, which is in its own module (eml-party) and namespace.  As a side
benefit, because we modeled the ResponsibleParty on the details of ISO
19115, you should be compatible with that standard as well.

Matt

On Wed, Jul 21, 2010 at 12:22 PM, ben leinfelder
<leinfelder at nceas.ucsb.edu>wrote:

> Ryan -
> The "contact" element is declared as a modular type is used for describing
> many different parties in EML: data creators, owners, contacts, associates,
> institutions etc...
> The eml-party module can be reused in a variety of other metadata schemas.
> The EML schema documentation for this module is available here:
>
> http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-party.html#ResponsibleParty
>
> Thanks,
> -ben
>
>
> On Jul 21, 2010, at 12:55 PM, Ryan Scherle wrote:
>
> >
> > Hi all,
> >
> > The Dryad repository stores metadata using an "application profile" that
> aggregates fields from various metadata schemas, including Dublin Core,
> Darwin Core, and PRISM. This approach facilitates interoperability with
> other metadata models while still allowing us to use the specific fields
> that best serve our community.
> >
> > We're interested in using some fields from EML in the Dryad metadata
> profile. However, the current structure of the EML schema makes reuse
> difficult (see message from our developer below). Is the EML community
> interested in changing the schema to facilitate this type of use?
> >
> > --- Ryan Scherle
> > --- Data Repository Architect
> > --- National Evolutionary Synthesis Center
> >
> > Begin forwarded message:
> >
> >> From: "Kevin S. Clarke" <ksclarke at nescent.org>
> >> Date: July 21, 2010 3:24:00 PM EDT
> >> To: Ryan Scherle <rscherle at nescent.org>
> >> Subject: EML:contact
> >>
> >> In short:
> >>
> >> Dryad would like to be able to reuse the eml:contact element that is
> >> used in the eml:dataset element within the EML schema (eml:dataset has
> >> a type of eml:DatasetType; eml:contact is a child element in a
> >> sequence in that DatasetType type).  We'd like to use eml:contact in
> >> our own XSD for the Dryad Metadata Profile independent of EML's
> >> dataset.  We can't though because eml:contact (seen below and at
> >>
> http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/eml/eml-dataset.xsd?rev=1.59&content-type=text/x-cvsweb-markup
> )
> >> is only defined as a child of DatasetType so can't be used independent
> >> of that structure.  If it were defined outside of that context and
> >> then referenced from within the DatasetType that would allow for its
> >> reuse apart from the dataset context.
> >>
> >> <!-- eml:contact as defined by their schema -->
> >>
> >>        <xs:element name="contact" type="rp:ResponsibleParty"
> >> maxOccurs="unbounded">
> >>          <xs:annotation>
> >>            <xs:appinfo>
> >>              <doc:tooltip>Contact</doc:tooltip>
> >>              <doc:summary>The contact for this dataset</doc:summary>
> >>              <doc:description>The contact field contains contact
> information
> >>              for this dataset. This is the
> >>              person or institution to contact with questions about the
> use,
> >>              interpretation of a data set.</doc:description>
> >>            </xs:appinfo>
> >>          </xs:annotation>
> >>        </xs:element>
> >>
> >> Kevin
> >
> > _______________________________________________
> > Eml-dev mailing list
> > Eml-dev at ecoinformatics.org
> > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
> _______________________________________________
> Eml-dev mailing list
> Eml-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20100721/984f0b1e/attachment.html>


More information about the Eml-dev mailing list