RDF list of terms as organized in the dwc-assistant?
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt
Hi Matt,
If you actually want to make a SPARQL query, all of the Darwin Core terms are loaded into the triplestore that's queriable at the endpoint http://rdf.library.vanderbilt.edu/sparql?view
You can run the query
PREFIX dcterms: http://purl.org/dc/terms/ PREFIX dwc: http://rs.tdwg.org/dwc/terms/ PREFIX dwcattributes: http://rs.tdwg.org/dwc/terms/attributes/
SELECT DISTINCT ?term WHERE { ?term dwcattributes:organizedInClass dwc:Occurrence. ?term dcterms:hasVersion ?version. }
and substitute any Darwin Core class in the place of dwc:Occurrrence. If you want to use the results in an application, you can make the request to the endpoint via HTTP GET like:
http://rdf.library.vanderbilt.edu/sparql?query=PREFIX+dcterms%3A+%3Chttp%3A%...
where the query string is URLencoded. The only SPARQL response format currently supported at that endpoint is XML (Accept: application/sparql-results+xml), although hopefully in the near future it will also support JSON. I hope that if we get to the point where the draft documentation specification [1] is ratified, TDWG itself can provide a stable endpoint where these kinds of queries can be made.
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
Hi everyone, the assistant (and also the GBIF dwca validator & IPT) makes use of the term groups defined in the xml dwca extension definitions which are hand crafted. E.g. for occurrence terms this one: http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml
There is no rdf version of that I am afraid. But we could probably generate an RDF view if that is sth useful.
Markus
On 29 Nov 2016, at 12:06, Matthew Blissett mblissett@gbif.org wrote:
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
The metadata in the JSON endpoint is exactly what I was looking for.
Thanks much, Matt
On Tue, Nov 29, 2016 at 6:22 AM, Markus Döring m.doering@mac.com wrote:
Hi everyone, the assistant (and also the GBIF dwca validator & IPT) makes use of the term groups defined in the xml dwca extension definitions which are hand crafted. E.g. for occurrence terms this one: http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml
There is no rdf version of that I am afraid. But we could probably generate an RDF view if that is sth useful.
Markus
On 29 Nov 2016, at 12:06, Matthew Blissett mblissett@gbif.org wrote:
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
If I find issues with http://gbrds.gbif.org/registry/extensions.json where should I file them? What about the end point XML files (like http://rs.gbif.org/extension/ggbn/materialsample.xml)?
I'm thinking structure/syntax issues rather than semantics.
M
On Tue, Nov 29, 2016 at 11:51 AM, Matt Yoder diapriid@gmail.com wrote:
The metadata in the JSON endpoint is exactly what I was looking for.
Thanks much, Matt
On Tue, Nov 29, 2016 at 6:22 AM, Markus Döring m.doering@mac.com wrote:
Hi everyone, the assistant (and also the GBIF dwca validator & IPT) makes use of the term groups defined in the xml dwca extension definitions which are hand crafted. E.g. for occurrence terms this one: http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml
There is no rdf version of that I am afraid. But we could probably generate an RDF view if that is sth useful.
Markus
On 29 Nov 2016, at 12:06, Matthew Blissett mblissett@gbif.org wrote:
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
Hi Matt,
if you could file issues in github here that would be appreciated! https://github.com/gbif/rs.gbif.org/issues
Many thanks, Markus
On 14 Dec 2016, at 17:33, Matt Yoder <diapriid@gmail.commailto:diapriid@gmail.com> wrote:
If I find issues with http://gbrds.gbif.org/registry/extensions.json where should I file them? What about the end point XML files (like http://rs.gbif.org/extension/ggbn/materialsample.xml)?
I'm thinking structure/syntax issues rather than semantics.
M
On Tue, Nov 29, 2016 at 11:51 AM, Matt Yoder <diapriid@gmail.commailto:diapriid@gmail.com> wrote: The metadata in the JSON endpoint is exactly what I was looking for.
Thanks much, Matt
On Tue, Nov 29, 2016 at 6:22 AM, Markus Döring <m.doering@mac.commailto:m.doering@mac.com> wrote: Hi everyone, the assistant (and also the GBIF dwca validator & IPT) makes use of the term groups defined in the xml dwca extension definitions which are hand crafted. E.g. for occurrence terms this one: http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml
There is no rdf version of that I am afraid. But we could probably generate an RDF view if that is sth useful.
Markus
On 29 Nov 2016, at 12:06, Matthew Blissett mblissett@gbif.org wrote:
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
_______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
_______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
_______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
Thanks. Moving discussion to https://github.com/gbif/rs.gbif.org/issues/7
On Wed, Dec 14, 2016 at 5:05 PM, Markus Döring mdoering@gbif.org wrote:
Hi Matt,
if you could file issues in github here that would be appreciated! https://github.com/gbif/rs.gbif.org/issues
Many thanks, Markus
On 14 Dec 2016, at 17:33, Matt Yoder diapriid@gmail.com wrote:
If I find issues with http://gbrds.gbif.org/registry/extensions.json where should I file them? What about the end point XML files (like http://rs.gbif.org/extension/ggbn/materialsample.xml)?
I'm thinking structure/syntax issues rather than semantics.
M
On Tue, Nov 29, 2016 at 11:51 AM, Matt Yoder diapriid@gmail.com wrote:
The metadata in the JSON endpoint is exactly what I was looking for.
Thanks much, Matt
On Tue, Nov 29, 2016 at 6:22 AM, Markus Döring m.doering@mac.com wrote:
Hi everyone, the assistant (and also the GBIF dwca validator & IPT) makes use of the term groups defined in the xml dwca extension definitions which are hand crafted. E.g. for occurrence terms this one: http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml
There is no rdf version of that I am afraid. But we could probably generate an RDF view if that is sth useful.
Markus
On 29 Nov 2016, at 12:06, Matthew Blissett mblissett@gbif.org wrote:
Hi,
I'm not sure the DWCA assistant is a best practice, but I don't know of anything better for the job. The source code is here: https://github.com/gbif/gbif-meta-maker
When it loads, it retrieves the list of extensions from here: http://gbrds.gbif.org/registry/extensions.json . This is also used by the GBIF IPT. We have a regular cron job keeping it up to date.
Hope that helps,
Matt
On 29/11/16 03:48, Matt Yoder wrote:
Hi Steve,
Thanks for the endpoint, I will have to play with it. I think that I have returned, for practical purposes, the same set of results by parsing http://rs.gbif.org/core/dwc_occurrence_2015-07-02.xml. Your concluding observations are right on point. I want something more- the sets present in the assistant, available as some resource endpoint. I want to automatically generate Ruby constants, Rails migrations, rspec validators and more via a more or less self-updating Ruby gem. This let's me replicate the functionality in the assistant in a back end without having to guess what I should cover.
It would seem that if the assistant is a best practice (and first step for many) towards getting others to using DWCAs then the metadata that drives that assistant should be available as a meta-standard of sorts? Is the source code to the assistant available somewhere?
Thanks, Matt
I'm not sure that this query will actually do what you want, since the terms in the various dropdowns in the DwC-A Assistant aren't strictly those whose dwcattributes:organizedInClass properties have values that are the dropdown category. Also, the various extensions aren't there. But your question is a kind of use case that TDWG should think about supporting for "enhancements" [2] to the basic DwC term vocabulary.
Steve
[1] https://github.com/tdwg/vocab/blob/master/documentation-specification.md [2] see Section 4 (Vocabulary enhancements) of https://github.com/tdwg/vocab/blob/master/maintenance-specification.md
Matt Yoder wrote:
Hi All,
I was wondering if there is an RDF document like https://github.com/tdwg/dwc/blob/master/rdf/dwcterms.rdf that had something like the dwcattributes:organizedInClass therein such that I could query it to return terms as organized in the dwca-assistant (http://tools.gbif.org/dwca-assistant/)?
In other words I want to return all terms under Core::Occurence, Core::Taxon, Core::Extensions::Foo etc.
Thanks for your time, Matt _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content
participants (5)
-
Markus Döring -
Markus Döring -
Matt Yoder -
Matthew Blissett -
Steve Baskauf