University of Geneva · API Governance Rules
University of Geneva API Rules
Spectral linting rules defining API design standards and conventions for University of Geneva.
7 Rules
warn 4
info 3
Rule Categories
unige
Rules
warn
unige-info-contact-email
Yareta API info block must carry the [email protected] contact email.
$.info.contact
warn
unige-servers-are-yareta-hosts
Servers should be the official Yareta DLCM backend hosts on unige.ch.
$.servers[*].url
info
unige-resid-uuid-identifier
Resources expose a 'resId' identifier (UUID by default, max length 50).
$.components.schemas[?(@.properties && @.properties.resId)].properties.resId
info
unige-change-info-readonly
ChangeInfo audit fields (who/when/fullName) are read-only.
$.components.schemas.ChangeInfo.properties[*]
warn
unige-orcid-pattern-present
Person ORCID values must declare the ORCID format pattern.
$.components.schemas.Person.properties.orcid
warn
unige-operation-tagged
Every operation should be tagged (Access, Ingest, or OAI-PMH).
$.paths[*][get,post,put,delete,patch]
info
unige-oais-package-descriptions
OAIS package schemas (AIP/DIP) should be documented with a description.
$.components.schemas.ArchivalInfoPackage$.components.schemas.DisseminationInfoPackage