<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Matt,
<div class=""><br class="">
</div>
<div class="">if you could file issues in github here that would be appreciated!</div>
<div class=""><a href="https://github.com/gbif/rs.gbif.org/issues" class="">https://github.com/gbif/rs.gbif.org/issues</a></div>
<div class=""><br class="">
</div>
<div class="">Many thanks,</div>
<div class="">Markus</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 14 Dec 2016, at 17:33, Matt Yoder <<a href="mailto:diapriid@gmail.com" class="">diapriid@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">If I find issues with <a href="http://gbrds.gbif.org/registry/extensions.json" class="">
http://gbrds.gbif.org/registry/extensions.json</a><br class="">
where should I file them? What about the end point XML files (like<br class="">
<a href="http://rs.gbif.org/extension/ggbn/materialsample.xml" class="">http://rs.gbif.org/extension/ggbn/materialsample.xml</a>)?<br class="">
<br class="">
I'm thinking structure/syntax issues rather than semantics.<br class="">
<br class="">
M<br class="">
<br class="">
On Tue, Nov 29, 2016 at 11:51 AM, Matt Yoder <<a href="mailto:diapriid@gmail.com" class="">diapriid@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class="">The metadata in the JSON endpoint is exactly what I was looking for.<br class="">
<br class="">
Thanks much,<br class="">
Matt<br class="">
<br class="">
On Tue, Nov 29, 2016 at 6:22 AM, Markus Döring <<a href="mailto:m.doering@mac.com" class="">m.doering@mac.com</a>> wrote:<br class="">
<blockquote type="cite" class="">Hi everyone,<br class="">
the assistant (and also the GBIF dwca validator & IPT) makes use of the term<br class="">
groups defined in the xml dwca extension definitions which are hand crafted.<br class="">
E.g. for occurrence terms this one:<br class="">
<a href="http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml" class="">http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml</a><br class="">
<br class="">
There is no rdf version of that I am afraid.<br class="">
But we could probably generate an RDF view if that is sth useful.<br class="">
<br class="">
<br class="">
Markus<br class="">
<br class="">
<br class="">
On 29 Nov 2016, at 12:06, Matthew Blissett <mblissett@gbif.org> wrote:<br class="">
<br class="">
Hi,<br class="">
<br class="">
I'm not sure the DWCA assistant is a best practice, but I don't know of<br class="">
anything better for the job. The source code is here:<br class="">
https://github.com/gbif/gbif-meta-maker<br class="">
<br class="">
When it loads, it retrieves the list of extensions from here:<br class="">
http://gbrds.gbif.org/registry/extensions.json . This is also used by the<br class="">
GBIF IPT. We have a regular cron job keeping it up to date.<br class="">
<br class="">
Hope that helps,<br class="">
<br class="">
Matt<br class="">
<br class="">
On 29/11/16 03:48, Matt Yoder wrote:<br class="">
<br class="">
Hi Steve,<br class="">
<br class="">
Thanks for the endpoint, I will have to play with it. I think that I<br class="">
have returned, for practical purposes, the same set of results by<br class="">
parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your<br class="">
concluding observations are right on point. I want something more-<br class="">
the sets present in the assistant, available as some resource<br class="">
endpoint. I want to automatically generate Ruby constants, Rails<br class="">
migrations, rspec validators and more via a more or less self-updating<br class="">
Ruby gem. This let's me replicate the functionality in the assistant<br class="">
in a back end without having to guess what I should cover.<br class="">
<br class="">
It would seem that if the assistant is a best practice (and first step<br class="">
for many) towards getting others to using DWCAs then the metadata that<br class="">
drives that assistant should be available as a meta-standard of sorts?<br class="">
Is the source code to the assistant available somewhere?<br class="">
<br class="">
Thanks,<br class="">
Matt<br class="">
<br class="">
<br class="">
I'm not sure that this query will actually do what you want, since the terms<br class="">
in the various dropdowns in the DwC-A Assistant aren't strictly those whose<br class="">
dwcattributes:organizedInClass properties have values that are the dropdown<br class="">
category. Also, the various extensions aren't there. But your question is<br class="">
a kind of use case that TDWG should think about supporting for<br class="">
"enhancements" [2] to the basic DwC term vocabulary.<br class="">
<br class="">
Steve<br class="">
<br class="">
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md<br class="">
[2] see Section 4 (Vocabulary enhancements) of<br class="">
https://github.com/tdwg/vocab/blob/master/maintenance-specification.md<br class="">
<br class="">
Matt Yoder wrote:<br class="">
<br class="">
Hi All,<br class="">
<br class="">
I was wondering if there is an RDF document like<br class="">
https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had<br class="">
something like the dwcattributes:organizedInClass therein such that I<br class="">
could query it to return terms as organized in the dwca-assistant<br class="">
(http://tools.gbif.org/dwca-assistant/)?<br class="">
<br class="">
In other words I want to return all terms under Core::Occurence,<br class="">
Core::Taxon, Core::Extensions::Foo etc.<br class="">
<br class="">
Thanks for your time,<br class="">
Matt<br class="">
_______________________________________________<br class="">
tdwg-content mailing list<br class="">
tdwg-content@lists.tdwg.org<br class="">
http://lists.tdwg.org/mailman/listinfo/tdwg-content<br class="">
<br class="">
<br class="">
<br class="">
--<br class="">
Steven J. Baskauf, Ph.D., Senior Lecturer<br class="">
Vanderbilt University Dept. of Biological Sciences<br class="">
<br class="">
postal mail address:<br class="">
PMB 351634<br class="">
Nashville, TN 37235-1634, U.S.A.<br class="">
<br class="">
delivery address:<br class="">
2125 Stevenson Center<br class="">
1161 21st Ave., S.<br class="">
Nashville, TN 37235<br class="">
<br class="">
office: 2128 Stevenson Center<br class="">
phone: (615) 343-4582, fax: (615) 322-4942<br class="">
If you fax, please phone or email so that I will know to look for it.<br class="">
http://bioimages.vanderbilt.edu<br class="">
http://vanderbilt.edu/trees<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
tdwg-content mailing list<br class="">
tdwg-content@lists.tdwg.org<br class="">
http://lists.tdwg.org/mailman/listinfo/tdwg-content<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
tdwg-content mailing list<br class="">
tdwg-content@lists.tdwg.org<br class="">
http://lists.tdwg.org/mailman/listinfo/tdwg-content<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
tdwg-content mailing list<br class="">
tdwg-content@lists.tdwg.org<br class="">
http://lists.tdwg.org/mailman/listinfo/tdwg-content<br class="">
<br class="">
</blockquote>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>