Coder Social home page Coder Social logo

Agents and References about tnc HOT 14 CLOSED

tdwg avatar tdwg commented on July 17, 2024
Agents and References

from tnc.

Comments (14)

nielsklazenga avatar nielsklazenga commented on July 17, 2024

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 avatar nielsklazenga commented on July 17, 2024

@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.

mdoering avatar mdoering commented on July 17, 2024

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.

deepreef avatar deepreef commented on July 17, 2024

Agreed!

from tnc.

afuchs1 avatar afuchs1 commented on July 17, 2024

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.

nielsklazenga avatar nielsklazenga commented on July 17, 2024

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.

ianengelbrecht avatar ianengelbrecht commented on July 17, 2024

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.

deepreef avatar deepreef commented on July 17, 2024

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.

deepreef avatar deepreef commented on July 17, 2024

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.

nielsklazenga avatar nielsklazenga commented on July 17, 2024

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.

mdoering avatar mdoering commented on July 17, 2024

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.

mdoering avatar mdoering commented on July 17, 2024

MODS XML is also still active

from tnc.

WUlate avatar WUlate commented on July 17, 2024

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.

nielsklazenga avatar nielsklazenga commented on July 17, 2024

Closing this for now...

from tnc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.