[open-science] citing a code and data on a GitHub repository

[Carl Boettiger]

Brian, thanks for clarifying.  I think a schema or semantic annotation of
the software descriptions published in JORS would be a great service to the
community.  Looking forward to seeing what you come up with,

- Carl


On Tue, Dec 3, 2013 at 11:51 AM, Brian Hole <brian.hole at ubiquitypress.com>wrote:

> JORS currently uses standard artice metadata. This is being enhanced at
> the moment however as a new online editor for the papers is in the works
> (to be released in January), which gives us a good opportunity to address
> the metadata as well, and we'll definitely take a look at DOAP and other
> examples to see how this could be improved.
>
> - Brian
>
> On 3 December 2013 18:02, Carl Boettiger <cboettig at gmail.com> wrote:
>
>> Great question. DOAP looks pretty promising.
>>
>> In ecology we have our own XML-schema metadata standard for describing
>> software, whose vocabulary is pretty generic:
>> http://knb.ecoinformatics.org/software/eml/eml-2.1.1/eml-software.html Not
>> RDF but the standard has been around for 10 years with reasonable adoption
>> in our discipline.  I assume other disciplines have similar creatures.
>>
>> Of course language-specific repositories often have their own way of
>> representing software metadata.  For instance, R packages on CRAN specify
>> generic metadata such as project title, description, authors, version, url,
>> bug reports, etc, in a machine-readable querable plain text format, e.g.
>> http://cran.r-project.org/web/packages/XML/  Certainly there are other
>> examples (cpan, etc).
>>
>> Would be nice if everyone wrapped some semantics like DOAP around this to
>> make these things more universal.
>>
>> Does JORS provide a machine-readable version of the metadata in their
>> descriptions?
>>
>>
>> On Tue, Dec 3, 2013 at 9:29 AM, Brian Hole <brian.hole at ubiquitypress.com>wrote:
>>
>>> JORS (the Journal of Open Research Software) is another alternative:
>>> http://openresearchsoftware.metajnl.com - with the additional benefit
>>> that the descriptions are citable.
>>>
>>> - Brian
>>>
>>> On 3 December 2013 17:17, Tom Morris <tfmorris at gmail.com> wrote:
>>>
>>>> On Tue, Dec 3, 2013 at 12:10 PM, Arfon Smith <arfon at github.com> wrote:
>>>>
>>>>> I'd be interested to hear if there's been any effort put into how to
>>>>> properly describe the function of a piece of code in a file like
>>>>> BibJSON. For example, knowing that a piece of code was written in
>>>>> Python, was for an astrophysics domain and performed coordinate
>>>>> transformations. It feels like that could be encapsulated in some kind
>>>>> of meta descriptor file which could then be indexed (and searched).
>>>>>
>>>>> Has anyone seen anything like this done?
>>>>>
>>>>
>>>> DOAP? https://github.com/edumbill/doap/wiki
>>>>
>>>> Tom
>>>>
>>>> _______________________________________________
>>>> open-science mailing list
>>>> open-science at lists.okfn.org
>>>> http://lists.okfn.org/mailman/listinfo/open-science
>>>> Unsubscribe: http://lists.okfn.org/mailman/options/open-science
>>>>
>>>>
>>>
>>> _______________________________________________
>>> open-science mailing list
>>> open-science at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/open-science
>>> Unsubscribe: http://lists.okfn.org/mailman/options/open-science
>>>
>>>
>>
>>
>> --
>> Carl Boettiger
>> UC Santa Cruz
>> http://carlboettiger.info/
>>
>
>
> _______________________________________________
> open-science mailing list
> open-science at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-science
> Unsubscribe: http://lists.okfn.org/mailman/options/open-science
>
>


-- 
Carl Boettiger
UC Santa Cruz
http://carlboettiger.info/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-science/attachments/20131203/2b0f47b8/attachment-0003.html>