Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 1.53 KB

RELEASING.md

File metadata and controls

61 lines (42 loc) · 1.53 KB
Raw

Process for releasing OEWN

XML Release

This is generated by Python scripts in this repo

Edit the file scripts/merge.py and WNDB_License.txt to update the version.

python scripts/from_yaml.py
cp wn.xml english-wordnet-20XX.xml
gzip english-wordnet-20XX.xml

WNDB Release

This is generated from by the GWN Scala API

First unzip the previous release into a folder called oewn20XX/

./gwn -i english-wordnet-20XX.xml -o oewn20XX/ -f WNLMF -t WNDB --wordnet-license WNDB_License.txt
zip -r english-wordnet-20XX.zip oewn20XX/

Testing:

sudo cp oewn20XX/* /usr/share/wordnet
wordnet novel_lemma_in_this_edition -over

RDF Release and en-word.net site

This is based on Wordnet Angular

Firstly, load the database from the XML file

cargo build --release
rm -f wordnet.db
cargo run --release --bin wordnet-angular -- --reload --wn ../../globalwordnet/english-wordnet/wn.xml -s en

Now dump the RDF data

cargo run --release --bin wordnet-rdf-dump -- -s en > wn.ttl
rapper -i turtle -o turtle wn.ttl > english-wordnet-2023.ttl
gzip english-wordnet-2023.ttl

In that repo edit src/main.rs and src/english-index.html to add links and downloads for next edition. Add the download files to the src/ folder and restart server.

Creating the release

Create a new release on GitHub and provide some nice summary of the main issues handled. Attach the XML, WNDB and RDF files to this link.