https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-05-09T23:21:10ZEcoinformatics RedmineEML - Bug #480: eml-resource changes neededhttps://projects.ecoinformatics.org/ecoinfo/issues/480?journal_id=15922002-05-09T23:21:10ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>Completed subitems 1, 2, 3, 4, 5, 7, 8, 9, and 11. Regarding pubDate (4), the<br />XML Schema datatypes spec does not allow truncation of any date type, so the<br />"xs:date" type must be a full calendar date, and the "xs:gYear" must be a 4<br />digit year and can not contain a month or day. Therefore, I have changed the<br />type of the "pubDate" field to be "xs:string", and specified inthe docs that the<br />date should follow ISO 8601 format. We may want to consider creating a derived<br />type that is either a gYear or a xs:date value.</p>
<p>Changes to coverage (6) are waiting on required changes to the eml-coverage<br />module.</p>
<p>That leaves items (6-coverage) and (10-distribution) remaining.</p> EML - Bug #480: eml-resource changes neededhttps://projects.ecoinformatics.org/ecoinfo/issues/480?journal_id=15932002-05-14T22:53:57ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>Item (6) is finished now that coverage has been updated in eml-coverage.</p>
<p>Item (10): Distribution:<br />I have created a content model that I think satisfies the spirit of our<br />Sevilleta discussions in full, but is more compact than the exact content model<br />that we discussed there. However, I still have problems with using the named<br />parameter list as it currently stands in the module. Right now, the model is:</p>
<p><!ELEMENT distribution ((connection|offlineMedium)+)><br /><!ELEMENT connection (onlineURL|parameter+)><br /><!ATTLIST connection name CDATA #IMPLIED<br /> scheme CDATA #IMPLIED> <br /><!ELEMENT onlineURL (#PCDATA)><br /><!ELEMENT parameter (#PCDATA)><br /><!ATTLIST parameter name CDATA #IMPLIED></p>
<p>This means someone can submit either a url or a list of named parameters for a<br />connection. However, the latter does not have well defined semantics, and so it<br />is impossible to actually construct a connection using this information without<br />a human interpreting the connection information. For example, if I give you the<br />following named parameter list for the scheme "database", precisely how do you<br />connect?<br /> hostid=5<br /> machinemap=7<br /> network=tcp/ip<br /> machinename=rover<br /> machinedomain=somewhere.com<br /> protocol=http<br /> location=perm</p>
<p>My point is, the semantics of the parameter list are specific to the scheme, and<br />URLs provide a standard way of encoding those semantics. If users create EML<br />for a common http URL as a param list, we will effectively be eliminating the<br />possibility of machine-processable connections.</p>
<p>An alternative is to provide a token substitution mechanism in the URLs. For<br />example, if the user can define a token delimiter (e.g., "@"), then a url might<br />be encoded as:</p>
<pre><code><a class="external" href="http://host.org:9087/webapps/cgi/getdata?id=@identifier@&username=jones">http://host.org:9087/webapps/cgi/getdata?id=@identifier@&username=jones</a></code></pre>
<p>In which case a single parameter needs to be provided to make the connection. <br />Trying to go beyond a simple URL encoding like this gets us into the realm of<br />re-inventing SOAP/WSDL or other service description systems. I really don't<br />think we should go there.</p>
<p>Sooo...I propose that we either 1) eliminate the parameter list entirely<br />(preferred), or 2) augment the URLs with a token substitution mechanism.</p> EML - Bug #480: eml-resource changes neededhttps://projects.ecoinformatics.org/ecoinfo/issues/480?journal_id=15942002-06-14T02:00:45ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>Changes completed and in CVS.</p> EML - Bug #480: eml-resource changes neededhttps://projects.ecoinformatics.org/ecoinfo/issues/480?journal_id=15952013-03-27T21:14:25ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 480</p>