vivo-ontology-1.8.0

Highlights of this release

1. Added ROR ID:
Incorporated a property for Research Organization Registry (ROR) identifiers.
2. Improved Metadata for the VIVO Ontology:
Enhanced ontology metadata to better align with community standards and to better support the FAIR principles.
3. Repository Housekeeping:
Updated README with clearer guidelines for contributors.
Improved documentation and repository workflow processes

What's Changed

• Updated link to https://vivo.lyrasis.org/ by @hauschke in #3
• Added licence to vivo.owl by @hauschke in #16
• Update new feature request issue template by @brianjlowe in #13
• Added link to VIVO development process wiki page by @hauschke in #9
• Set .gitattributes to eol=lf by @hauschke in #21
• Added rdfs:comment for bibo:issue by @hauschke in #1
• fixed typo "tye" to type by @hauschke in #24
• Removed domain statement from bibo:doi by @tawahle in #18
• Readme release information by @hauschke in #20
• Delete outdated OWL generator comment by @hauschke in #48
• change super class of the Software class by @chenejac in #49
• Adding SWHID identifiers to Software by @chenejac in #37
• Added editing policy by @hauschke in #51
• fixed broken link by @hauschke in #54
• Added dc:creator by @hauschke in #65
• Added doap:repository by @tawahle in #67
• Added vann:preferredNamespacePrefix by @hauschke in #70
• Add ROR ID by @hauschke in #56
• Added dc:description for the VIVO Ontology by @hauschke in #66
• Added doap:bug-database by @hauschke in #71
• Fixed tag closing by @hauschke in #72
• fixed incorrect creator tag by @hauschke in #74
• Add owl:versionInfo by @hauschke in #73

Contributors since 1.7

• @hauschke made their first contribution in #3
• @brianjlowe made their first contribution in #13
• @tawahle made their first contribution in #18
• @chenejac made their first contribution in #49

Full Changelog: vivo-ontology-1.7.0...vivo-ontology-1.8.0

vivo-ontology-1.7.0

This is a first release in this repository. From now on, versioning will be based on SemVer. Further information will gradually be added to the readme. If you have questions or suggestions for improvement, please open an issue.