EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #09680

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] SPDX - licences

CAUTION: This e-mail originated outside the University of Southampton.

We use signposting (schema.org) in our repository, activating the plugin JSONLD which does:

sub dataobj_to_html_header
        my( $plugin, $dataobj ) = @_;

        my $jsonld = $plugin->{session}->make_doc_fragment;

        my $script_tag = $plugin->{session}->make_element( "script", type => "application/ld+json", id => "jsonLinkedData" );
        my $eprintld = $plugin->convert_dataobj( $dataobj );
        my $json = JSON::to_json( $eprintld );
        $script_tag->appendChild( $plugin->{session}->make_text( $json ) );
  $jsonld->appendChild( $plugin->{session}->make_text( "\n" ) );
        return $jsonld;

We agree to use spdx, it is used to automatically extract license information from repositories.

Il 18/03/24 17:59, John Salter ha scritto:
CAUTION: This e-mail originated outside the University of Southampton.
CAUTION: This e-mail originated outside the University of Southampton.

Hi [and apologies for cross-posting],

Just wondering if anyone in the EPrints community has looked into using the SPDX licence definitions, which cover the CC licences as well as many others: https://spdx.org/licenses/


The ‘FAIR Signposting profile’: https://signposting.org/FAIR/#scholobject indicates it’s their preferred way to include licence information.

Currently EPrints has a set of short codes it uses for the licences namedset. SPDX does a similar thing with a standardised short-code, but then machine-readable details/links.


The list itself is available in a few machine-friendly formats- JSON / JSON-LD / RDFa e.g. https://github.com/spdx/license-list-data/blob/main/json/licenses.json, so could either be incorporated either into the core EPrints codebase, of into an ‘extended’ licences plugin/ingredient.


At this point in time, just wondering if other people had come across it.





John Salter



White Rose Libraries Technical Officer
IT - Application Support (Research)
University of Leeds


*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/