project, methods, protocol
Peter McCartney
peter.mccartney at asu.edu
Mon Aug 26 09:24:27 PDT 2002
sorry...im going put duct tape over that mouse pad.. the sentence should
have finished with
existing links to eml-protocol would be changed to eml-methods.
I should also have mentioned that while it seems redundant to have two
modules, (eml-protocol and eml-methods) with similar structure, it is a
reflection of the two different reasons why we define complex types in xml -
to reuse CONTENT and/or to reuse STRUCURE. the requests we got to make
protocol a "resource" reflected a desire to reuse content. Making
eml-methods a module relfects a desire to re use the same content.
Over the weekend, it occurred to me that we could eliminate some of this
redundance by stripping the content out of em-Protocol and simply importing
the eml-methods module there. that would leave the content definition to
eml-methods, with em-protocl simply providing a means to make that certain
instances of that content publishable as a "resource". My feeling is there
are very few cases where the methods description for a specific dataset is
of much general use without some rewriting, so i was never very excited
about all methodogical descriptions being described and archived as
independent resources.
Peter McCartney (peter.mccartney at asu.edu)
Center for Environmental Studies
Arizona State University
480-965-6791
-----Original Message-----
From: Tim Bergsma [mailto:tbergsma at kbs.msu.edu]
Sent: Monday, August 26, 2002 5:51 AM
To: Peter McCartney
Subject: Re: project, methods, protocol
Peter,
This message from you ends abruptly. Were it any other topic, I would
assume I'd gotten all the important parts. If that is true here, please
disregard this message.
Tim.
> Peter McCartney wrote:
>
> Tim et. al.
>
> I cant figure out how to do the branch thing within cvs so im just
> doing this through email. If you thinke this is no the right track,
> then ill make a full version that works with all the schemas and get
> help to figure out the branch submission.
>
> As a trial balloon for the project/protocol bug, Ive made changes to
> eml-project and eml-protocol, and ive created a new file called
> eml-method.
>
> to summarize
>
> eml-project loses sampling, but gains a recursive link to itself.
>
> eml-method is a new module that is meant to be imported into dataset,
> entitybase and attribute. It contains elements for sampling,
> qualityControl (that is actions you took during data collection to
> control quality), and methodsteps. each methodstep contains a
> description (which may be any combination of a text description,
> pointer to a citation, or pointer to a protocol), instrumentation,
> source data, software.
>
> eml-protocol is simplied to just a text description, with optional
> elements for sofware, instrumentation or qualitycontrol (but not
> datasets, because we cant really say a generic method requires a
> specific dataset). eml-protocol is linked only in eml-method -
> existing links to
>
> Peter McCartney (peter.mccartney at asu.edu)
> Center for Environmental Studies
> Arizona State University
> 480-965-6791
>
>
>
> Name: eml-protocol.xsd
> eml-protocol.xsd Type: XML Schema
> (application/x-unknown-content-type-xsdfile)
> Encoding: QUOTED-PRINTABLE
>
> Name: eml-project.xsd
> eml-project.xsd Type: XML Schema
> (application/x-unknown-content-type-xsdfile)
> Encoding: QUOTED-PRINTABLE
>
> Name: eml-methods.xsd
> eml-methods.xsd Type: XML Schema
> (application/x-unknown-content-type-xsdfile)
> Encoding: QUOTED-PRINTABLE
--
Tim Bergsma
LTER Information Manager
W.K. Kellogg Biological Station
Michigan State University
Hickory Corners, MI 49060
616/671-2337
tbergsma at kbs.msu.edu
http://lter.kbs.msu.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20020826/ee7dcab3/attachment.htm
More information about the Eml-dev
mailing list