EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362003-08-11T23:08:04ZEcoinformatics Redmine
Redmine Bug #1129 (Resolved): Change temporalCoverage calendarDate typehttps://projects.ecoinformatics.org/ecoinfo/issues/11292003-08-11T23:08:04ZDavid Blankmandblankman@lternet.edu
<p>There has been a request to change to data type on the element calenderDate to<br />include xs:gYear. This could be accomplish by creating a calenDateType that<br />would be a union of xs:date and xs:gYear.</p> Bug #1035 (Resolved): Technical documentation on eml-methods has an errorhttps://projects.ecoinformatics.org/ecoinfo/issues/10352003-04-09T23:41:04ZDavid Blankmandblankman@lternet.edu
<p>The second paragraph describing references should be deleted.</p>
<p>Current:</p>
<p>2.4.6. The eml-methods module - Methodological information for resources</p>
<p>The eml-methods module describes the methods followed in the creation of the<br />dataset, including description of field, laboratory and processing steps,<br />sampling methods and units, quality control proceudures. The eml-methods module<br />is used to describe the actual procedures that are used in the creation or the<br />subsequent processing of a dataset. Likewise, eml-methods is used to describe<br />proccesses that have been used to define / improve the quality of a data file,<br />or to identify potential problems with the data file. Note that the eml-protocol<br />module is intended to be used to document a prescribed procedure, whereas the<br />eml-method module is used to describe procedures that were actually performed.<br />The distinction is that the use of the term "protocol" is used in the<br />"prescriptive" sense, and the term "method" is used in the "descriptive" sense.<br />This distinction allows managers to build a protocol library of well-known,<br />established protocols (procedures), but also document what procedure was truely<br />performed in relation to the established protocol. The method may have diverged<br />from the protocol purposefully, or perhaps incidentally, but the procedural<br />lineage is still preserved and understandable.</p>
<p>The eml-methods module, like other modules, may be "referenced" via the<br /><references> tag. This allows a method to be described once, and then used as a<br />reference in other locations within the EML document via it's ID.</p>
<p>Peter's comments on not having references in methods is below:</p>
<p>The idea was that methods entry should be unique (what I did in THIS dataset).<br />If it's a standardised method that you want to reference, then presumabely you<br />would publish it as a protocol. If the same method applies to multiple entities<br />in your dataset, then you would just place that methods description higher up<br />(in dataset, for example).</p> Bug #1017 (Resolved): documentation error in eml-methodshttps://projects.ecoinformatics.org/ecoinfo/issues/10172003-03-21T16:25:21ZMatt Jonesjones@nceas.ucsb.edu
<p>The following error in the eml-methods documentation was reported by Eda Melendez:</p>
<p>--- Excerpt from Eda Melendez ---<br />I was looking at your online EML database module methods documentation<br />(<a class="external" href="http://knb.ecoinformatics.org/software/eml/eml-2.0.0/eml-methods.html#description">http://knb.ecoinformatics.org/software/eml/eml-2.0.0/eml-methods.html#description</a>)<br />and noticed there is a slight error on it:</p>
<p>the coverage field contains the description for the studyExtent with an extra<br />sentence:<br />"See eml-coverage for more information"</p>
<p>then the description field has the "Description" for the coverage field. So the<br />description field lacks "Description" (sounds like a paradox isn't it?)<br />--- End excerpt ---</p> Bug #1008 (Resolved): inline element doesn't support character childhttps://projects.ecoinformatics.org/ecoinfo/issues/10082003-03-07T17:31:10ZJing Taotao@nceas.ucsb.edu
<p>Today, when we tried to upload an eml2 doucment with inline charater data<br />to Metacat, a error was shown that inline element can only have element<br />children and can't have a character child(inline element is defined in<br />eml-resource.xsd). However, inline element supposes to support characters <br />children.<br />Something is wrong.</p>
<p>We took a look on the definition and found the children of inline is<br />defined as "any". So it seemes schema only consider the "any" <br />just for elements come from any namespace and we couldn't put characters<br />in there. This is different to dtd "any". In dtd, "any" can be considered<br />as elements or characters.</p>
<p>Dan found an text type defined in w3c primer web site:<br /><xsd:complexType name="text"><br /> <xsd:complexContent mixed="true"><br /> <xsd:restriction base="xsd:anyType"><br /> <xsd:sequence><br /> <xsd:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/><br /> </xsd:sequence><br /> <xsd:attribute ref="xml:lang"/><br /> </xsd:restriction><br /> </xsd:complexContent><br /></xsd:complexType></p>
<p>It allows an unrestricted mixture of character content and element content<br />from any namespace.</p>
<p>I wrote an very simple schema which contains the text type and a xml<br />instance. Then using xerces to validate the xml instance by the schema. It<br />works fine if we delete the line: <xsd:attribute ref="xml:lang"/> in the<br />complex type definition.</p>
<p>So, can we use this type to replace the anonymous type for inline or other<br />place which use "any"?</p> Bug #980 (Resolved): numberPerMilliliter and numberPerLiter missing from unitDictionaryhttps://projects.ecoinformatics.org/ecoinfo/issues/9802003-02-04T00:05:41ZDavid Blankmandblankman@lternet.edu
<p>Two density units numberPerMilliliter and numberPerLiter that were supposed to<br />have been added to the unitDictionary were never added.</p> Bug #939 (Resolved): spelling errors for 'its' in indexhttps://projects.ecoinformatics.org/ecoinfo/issues/9392003-01-10T16:57:19ZMatt Jonesjones@nceas.ucsb.edu
<p>Aaron Ellison pointed out that most uses of the word "it's" in the EML index and<br />other pages should in fact be the possibve "its". Need to check and fix this<br />throughout all documents when there is a need for a revision.</p> Bug #624 (Resolved): eml-methods/methodsType needs clarification on choice/sequencehttps://projects.ecoinformatics.org/ecoinfo/issues/6242002-10-09T19:30:49ZDavid Blankmandblankman@lternet.edu
<p>The current model for methodsType is a repetable choice of methodSteps (1 or<br />more) or sampling (0 or 1) or qualityControl (0 or more). This should be either:</p>
<p>1. a repeteable choice of methodStep or qualityControl or sampling</p>
<p>or</p>
<p>2. Sequence of methodSteps (1 or more), sampling (0 or 1?), qualityControl (0 or<br />more?).</p>
<p>We need to get some agreement on which model to use.</p>
<p>I recomend that we go with option 1.</p> Bug #600 (Resolved): eml-storedProcedure - problems & proposalhttps://projects.ecoinformatics.org/ecoinfo/issues/6002002-09-23T19:08:50ZDavid Blankmandblankman@lternet.edu
<p>As I began documenting storedProcedure it seemed to me that it is not<br />appropriately modeled. In eml-view, there is "queryStatement" which allows the<br />user to provide the sql code necessary to produce the view that is being documented.</p>
<p>In storedProcedure, however, "parameter" replaces queryStatement. In order to<br />invoke a stored procedure, however, you need more than just the parameters. You<br />need the name of the storedProcedure or something equivalent to the<br />queryStatement found in eml-view. I would proposed a structure for<br />storedProcedure that resembles eml-view.</p>
<p>I am assuming that storedProcedure is meant to apply primarily to a DBMS. If so,<br />then the storedProcedure syntax and execution must be system specific. If the<br />intent is to describe the stored procedure, then that should be done in<br />eml-software.</p> Bug #597 (Resolved): In eml-dataTable caseSensitive and orientation are modeled differentlyhttps://projects.ecoinformatics.org/ecoinfo/issues/5972002-09-19T17:01:10ZDavid Blankmandblankman@lternet.edu
<p>In eml-dataTable caseSensitive and orientation are modeled differently.</p>
<p>Orientation has an attribute of columnOrRow with an enumeration of columnMajor,<br />rowMajor.</p>
<p>caseSensitive has no attribute, just an enumeration of yes,no.</p>
<p>Is there a purpose behind the extra complexity of orientation?</p> Bug #594 (Resolved): change cardinality for designDescription and studyAreaDescriptionhttps://projects.ecoinformatics.org/ecoinfo/issues/5942002-09-18T18:51:06ZTim Bergsmatbergsma@kbs.msu.edu
<p>In researchProject, it is apparently possible to create any number of <br />designDescriptions, each of which contain any number of descriptions of type <br />TextType. I can see why someone might want to have more than one description, <br />but I see no reason why someone would want to group these into more than one <br />designDescription, UNLESS he/she could also specify some OTHER attribute of <br />that group, such as a name.</p>
<p>I think that the cardinality of designDescription should be zero or one.<br />I think that the cardinality of studyAreaDesign should be zero or one, for the <br />same reason.</p> Bug #488 (Resolved): eml-project changes neededhttps://projects.ecoinformatics.org/ecoinfo/issues/4882002-05-02T00:12:47ZMatt Jonesjones@nceas.ucsb.edu
<p>Changes as decided upon at the Sevilleta EML meeting, April 24-25, 2002:<br />Responsible: James</p>
<p>1) make personnel an element that extends ResponsibleParty with a "role" element<br />2) make siteDescription and designDescription local elements in the schema <br />instead of global as they are now<br />3) rename siteDescription to "studyAreaDescription" -- expect it to evolve to<br />follow siteDB in later versions. James, David, Karen to take lead on this.<br />3) revise sampling to include:<br /> studyExtent -- coverage and /or a paragraph*<br /> samplingDescription (paragraph+ incudes description of stratification)<br /> citation*<br /> spatialSamplingUnits? -- choice of (geographicCoverage+) or (a reference to<br />an entityID) -- I don't really understand how this will work, so be sure to<br />document the semantics fully.</p>
<p>4) link to coverage instead of the individual temporalCov and GeoCov elements</p>