[esip-semantictech] [EXTERNAL] Re: [Esip-citationguidelines] SWEET citation

Mon Jul 1 13:26:22 EDT 2019

I agree, DOI and you don’t need the file type for a citation. That should be info in the landing page.
For that version of SWEET, I’m sure the semantic group can correct me, isn’t it younger than 2002?

--
Jessica Hausman
Jet Propulsion Lab
4800 Oak Grove Dr.
MS 158-242
Pasadena, CA 91109
http://orcid.org/0000-0002-1861-1526
Tel: +1 818-354-4588

From: Esip-citationguidelines <esip-citationguidelines-bounces at lists.esipfed.org> on behalf of "Parsons, Mark via Esip-citationguidelines" <esip-citationguidelines at lists.esipfed.org>
Reply-To: "Parsons, Mark" <parsom3 at rpi.edu>
Date: Friday, June 28, 2019 at 3:43 PM
To: Ruth Duerr <ruth.duerr3 at gmail.com>
Cc: Ruth Duerr via esip-semanticweb <esip-semanticweb at lists.esipfed.org>, Esip-citationguidelines <esip-citationguidelines at lists.esipfed.org>, Pier Luigi Buttigieg <pbuttigi at mpi-bremen.de>
Subject: [EXTERNAL] Re: [Esip-citationguidelines] [esip-semantictech] SWEET citation

I like Pier Luigi’s approach with a DOI for a zenodo/github location. This seems more persistent, in so much as we trust the longevity of Zenodo and GitHub (or Zenodo more than GitHub).

I see no need to include the file format in the citation. (It looks like a typo :-))

2¢

-m.

On 28 Jun 2019, at 20:25, Ruth Duerr via Esip-citationguidelines <esip-citationguidelines at lists.esipfed.org<mailto:esip-citationguidelines at lists.esipfed.org>> wrote:

All good topics for the next ESIP Semantic Committee Telecon!

Ruth

On Jun 27, 2019, at 5:19 PM, Pier Luigi Buttigieg <pbuttigi at mpi-bremen.de<mailto:pbuttigi at mpi-bremen.de>> wrote:

I'd substitute the github link with a true URI (the target may move away from github) and add some sort of hash.
Is http://sweetontology.net<http://sweetontology.net/>/ the right IRI?
Most OBO ontologies will issue a new IRI for each release, such as
http://purl.obolibrary.org/obo/envo/releases/2019-03-14/envo.owl
May be a good idea for SWEET too?
ENVO also ties Zenodo DOIs to its releases :
https://zenodo.org/badge/latestdoi/13996/EnvironmentOntology/envo

----------
Sent from a mobile device - excuse the brevity
w: https://orcid.org/0000-0002-4366-3088
On 28 Jun 2019, at 01:05, Ruth Duerr via esip-semanticweb <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>> wrote:
Hi all,

Believe it or not I need to cite the SWEET ontology.  Here is the only recommendation I’ve found for citing an ontology (in Dutta, B. (2018). Theoretical analysis and propositions for “ontology citation.” In Proc. of the Int. Conf. on Exploring the Horizons of Library and Information Sciences: From Libraries to Knowledge Hubs, 7-9 August, 2018 Bangalore, India, pp. 451-458. ISBN 978-93-5311-726-9. Available at https://arxiv.org/pdf/1809.01462):

Table 1. The proposed template for referring an ontology

Creator. (Date). Acronym: full name of the ontology. Version(revision), URI [Ontology file format]
Where,
•  Creator refers to the main authors of an ontology (and not the contributors). In the
case of ontology, it is often the case that besides the creators, there are people who contribute to the ontology in various forms (e.g., participate in the meetings, gives feedback, evaluate the ontology, point to the possible bugs in an ontology, create/assist in preparing the ontology documentation, etc.). We suggest mentioning only the author names. All the author names should be provided. It is suggested to render the author name(s) in the form of surname, first name. In case of unavailability of any personal author name, provide the group name, i.e. the name of the organization (or institution) produced the ontology.
•  The Date is the date of publication (release date) of an ontology. It is suggested to provide the complete date of publication of a particular version of an ontology. The suggested date format is YYYY-MM-DD.
•  The name of an ontology. The name of an ontology may consist of two parts: acronym and full name of an ontology. In the case of ontology, the use of the acronym is very common. Most of the ontologies are known by their acronym (e.g., SUMO for Suggested Upper Merged Ontology, DOLCE for Descriptive Ontology for Linguistic and Cognitive Engineering, BFO for Basic Formal Ontology, MOD for Metadata for Ontology Description and publication). Following the acronym, provide the full name of the ontology. As indicated above, the acronym and the full name of an ontology should be separated by a colon “:”.
•  Version(revision) is an important information for providing access to a particular version of an ontology. An ontology goes through several revisions and editions, time to time gets updated. As indicated, the version number should be mentioned first and following this, the revision number (if any) of an ontology should be provided within a circular bracket “()”.
•  URI, the URI of an ontology, preferably the URI pointing to an ontology file. However, in case of availability of an ontology in multiple file formats, it is suggested to provide the base URI of the ontology.
•  Ontology file format. Provide the file formats within the square bracket “[]”. Also, use commas “,” to separate the multiple file formats (e.g., [rdf/xml, owl/xml, obo, n3]).
Example:

That would make the SWEET citation something like:

Raskin, Rob. (2002?). SWEET: Semantic Web for Earth and Environmental Terminology. 2 (3.0), https://github.com/ESIPFed/sweet [ttl]

Does that seem fine to everyone?

Ruth

________________________________

esip-semanticweb mailing list
esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>
https://lists.esipfed.org/mailman/listinfo/esip-semanticweb

_______________________________________________
Esip-citationguidelines mailing list
Esip-citationguidelines at lists.esipfed.org<mailto:Esip-citationguidelines at lists.esipfed.org>
https://lists.esipfed.org/mailman/listinfo/esip-citationguidelines

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-semanticweb/attachments/20190701/e9b954ca/attachment-0001.htm>