Comments (14)
Regarding literature and agents, I agree on how essential they are to us and am happy for the TNC to take that on, but I don't want it to delay the publication of the draft standard (for which we are aiming for September). So I will open the GitHub issue and we might dedicate a TNC meeting to it, where we can see how much time it is likely to take and whether we can include it in our current work, or do it afterwards. I know that there is some work going on within TDWG on at least agents.
Originally posted by @nielsklazenga in #47 (comment)
from tnc.
@nielsklazenga : I agree that the References/Agents components should come after we've locked in a decent draft of the Taxon Names/Usages/etc. standard.
A group is forming consisting of CoL-Folk, PLAZI-Folk, WoRMS-Folk, ZooBank-Folk, and other interested parties. A lot of that discussion will happen within the Bibliography of Life space (managed by PLAZI), but that will be more about workflow and content generation/cleanup. I think the standards discussion should take place within this TNC space.
Originally posted by @deepreef in #47 (comment)
from tnc.
To me the biggest drawback of TCS and an important blocker for its take up was the lack of standard for exchanging references. Other placeholder like specimens were bad too, but not as important. Even if references are not the intellectual core of this group, exchanging data without references will simply not work. If it's supposed to be an exchange standard someone needs to provide a definition.
from tnc.
Agreed!
from tnc.
I also agree, even if we have to do a two level standard to handle exchange when existing systems can and cannot support an increased level of granularity (much as we do for other data).
from tnc.
Then let's talk about what to do about it at our next meeting. I don't think it should be all that much work as we can just do an application profile on top of existing standards/ontologies (and anything not in there we can put in this standard, as that would have to be very specific to us).
from tnc.
Are there existing standards for references and agents that could be adopted or extended? I'm aware of https://schema.org/Person and https://schema.org/CreativeWork but there may be others.
from tnc.
One that I and a number of other people have followed is FOAF
Edit: I think maybe "drawn from" is a better description than "followed", in this context.
from tnc.
Note that for agents, I strongly recommend that we define two separate classes: Agent and AgentName. Instances of the Agent class would (in my view) fall into one of several mutually-exclusive subclasses, minimally including Person and Organization (but perhaps also "Group" or "Team", and possibly other collectives besides "Organization"). Properties of Agent instances include things like birthDate, deathDate, and maybe a few others of interest/relevance to our community.
Instances of AgentName are text-string labels applied to Agent instances, typically parsed to givenName and familyName for Agents that are of subclass Person, and parsed into something like fullName and shortName for organizations/groups.
There are many other details to sort out, and I hope to kick off this discussion in more detail later this month.
from tnc.
Wikidata already does exactly that, i.e. having agent names as objects (or Item in Wikidata), although Wikidata has items for family name and given names, the labels of which can be concatenated to the Agent Item label. There is, however, a point where, in the biodiversity community, we stop being interested and I think that is right at the Agent object (for me personally – and I think for the TNC – it is a bit earlier than that, at the Reference). This sounds to me like the choice between a SKOS label and a SKOS extended label (tdwg/tag#22).
The TDWG/RDA Attribution Interest Group (https://github.com/tdwg/attribution) is very much into Agents. I think we should leave Agents to them and focus on other parts of the Reference.
from tnc.
For references BibTex, BibJSON and CSL-JSON come to my mind. Having used CSL-JSON lately I am shocked by the lack of standardisation. I value the proven simplicity of BibTex, but its lack of author lists and normalised journals is bad. BibJSON is an improvement here.
You can retrieve metadata for all CrossRef, DataCite and mEDRA DOIs in CSL-JSON and BibTex which is a big advantage. See https://citation.crosscite.org/docs.html#sec-4 for other supported formats:
curl -LH "Accept: text/bibliography; style=bibtex" http://dx.doi.org/10.1093/database/baw125
curl -LH "Accept: application/vnd.citationstyles.csl+json" http://dx.doi.org/10.1093/database/baw125
See also https://github.com/rdmpage/bibliographic-metadata-json and discussions at CatalogueOfLife/general#23
from tnc.
MODS XML is also still active
from tnc.
I've also seen Librarians talking "RIS", "a standardized tag format [created specifically] to enable citation programs to exchange data and supported by a number of reference managers", though I'm not sure if it's been superceded by any of the more recent standards.
from tnc.
Closing this for now...
from tnc.
Related Issues (20)
- Use of this repo - TNC vs. TCS2 HOT 5
- LSIDs for taxonomic names live again HOT 42
- property:{TO BE NAMED} to indicate the novel status of a taxon in a publication HOT 20
- Teleconference 14 January 2020 20:00 UTC
- The need for "intersects" as a TNU relationship type in addition to the five RCC-5 types HOT 28
- Proposed: 'protonym' property on TaxonomicNameUsage HOT 1
- Vernacular names HOT 13
- More appropriate name for TaxonRelationshipAssertion class HOT 60
- Teleconference 24 March 2020 20:00 UTC HOT 1
- TNU Hackathon 7 April 2020 HOT 5
- Task group? HOT 14
- Teleconference 26/27 May 2020 HOT 7
- "Taxon" ID that does not change unless circumscription has changed HOT 27
- How to indicate which TNUs are current HOT 21
- RCC5 relation intersects HOT 4
- Should taxonomicName be represented as a Subclass of taxonomicNameUsage HOT 45
- Fern concept example HOT 6
- Proposal: add properties that represent TNU relationships HOT 2
- Merging Discussions
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tnc.