Skip to content

OCFL Specification Style Guide

Jump to bottom Edit New page
Simeon Warner edited this page Sep 6, 2018 · 8 revisions

A collection of editorial rules and decisions regarding the OCFL specification.

  • Use US spelling (see #52)
  • Use only the minimal subset of RFC2119 language: MAY, MUST, MUST NOT, SHOULD and SHOULD NOT (see #35)
  • Capitalization: "OCFL Object" - always capitalize the O of Object, don't use the word object in other contexts except "object store"
Add a custom footer

Home

Meetings

  1. Community Meetings
  2. Editorial Meetings

Reference

  1. Roadmap
  2. Change Process
  3. Style Guide
  4. Validator Codes
  5. Implementations
  6. Abstract Client API
  7. Papers and Presentations on OCFL
  8. Related Reading
Clone this wiki locally