Release of RiC-O 1.1

[CLAVAUD Florence]

Dear RiC users,

We have just released a new version of RiC-O, RiC-O 1.1.

You can get it, either using 'git pull' from the master branch to your local Git repository, or simply downloading the release, which comes with accompanying material (https://github.com/ICA-EGAD/RiC-O/releases/tag/v1.1).

The ontology files are as usual in the ontology/current-version folder.

Also, of course, you can access RiC-O 1.1 through the ontology IRI (https://www.ica.org/standards/RiC/ontology) or through its version IRI (https://www.ica.org/standards/RiC/ontology/1.1).

RiC-O 1.1 presents itself as an ontology richer than RiC-O 1.0, particularly as concerns the properties defined for record resources, instantiations, proxies, relations and agents, technically opening up new possibilities, and preserving or extending the semantics defined previously.

A few changes have also been made: rico:hasOrHadCategory has been renamed rico:hasOrHadType; the domain of rico:destructionDate and rico:hasDestructionDate has been reduced from rico:Thing to the union of rico:RecordResource and rico:Instantiation.

A detailed list of the changes made since RiC-O 1.0.2 is available on the release page (https://github.com/ICA-EGAD/RiC-O/releases/tag/v1.1).

If you plan to implement RiC-O, we recommend you choose this version.

A big "thank you" to all the people who, outside the ICA/EGAD group, contributed to the development of this version, through their requests, their comments, their advice, their help whatever it is.

The EGAD RiC-O development team will now start to work on the roadmap towards the next version, which will probably be a major one (RiC-O 2.0). We will come back to you about this topic later.

Best regards,

Florence Clavaud
Executive member of ICA/EGAD ; lead of RiC-O development team
Conservatrice générale du patrimoine | General curator
Responsable du Lab des Archives nationales de France| head of the Lab, Archives nationales de France

---

Merci de nous aider à préserver l'environnement en n'imprimant ce courriel et les documents joints que si nécessaire.