OCFL/spec

Issues

• More references to the Implementation Notes in spec

  #638 opened a year ago by neilsjefferies
  1

• Clarify that object structure is defined by sections 3.2 through 3.9

  #637 opened 10 months ago by zimeon
  0

• using unique IDs instead of digest to reference files

  #632 opened a year ago by eroux
  13

• Broken links in OCFL 1.1 specs

  #645 opened a year ago by max-moser
  1

• More compact inventory.json format

  #642 opened a year ago by srerickson
  0

• Are Storage Roots optional?

  #620 opened 2 years ago by kieranjol
  4

• Handling mixed spec-version objects without version inventories

  #569 opened 3 years ago by zimeon
  3

• unicode normalization

  #559 opened 3 years ago by pwinckles
  1

• Is it OK to have a missing version directory?

  #540 opened 4 years ago by zimeon
  21

• Make object ID accessible from a small file without having to parse inventory

  #579 opened a year ago by ptsefton
  10

• Review number of MAY's in spec

  #639 opened a year ago by neilsjefferies
  0

• Find way to have the 'table of contents' be in a side panel in the Markdown spec, so that it is always available.

  #597 opened 2 years ago by zimeon
  0

• Adding a file size key to the inventory

  #629 opened a year ago by tomwrobel
  10

• Should OCFL include a compatibility promise?

  #572 opened 3 years ago by srerickson
  3

• Add a section describing upgrading an object to a new spec version to the Implementation Notes

  #602 opened 2 years ago by zimeon
  0

• Add a section describing upgrading a Storage Root to a new spec version to the Implementation Notes

  #603 opened 2 years ago by zimeon
  0

• changes to Implementations wiki

  #636 opened a year ago by srerickson
  2

• update NAMASTE link in Implementation Notes

  #630 opened a year ago by srerickson
  2

• Pairtree link in v1.1 of spec goes to a confluence page that requires login

  #627 opened 2 years ago by ptsefton
  3

• Making time between object validity constant and small on S3

  #605 opened 2 years ago by srerickson
  3

• NAMASTE reference points to non-public location

  #623 opened 2 years ago by scossu
  5

• Add left-hand table of contents rendering to Markdown versions of Specification and Implementation Notes

  #604 opened 2 years ago by zimeon
  2

• Release OCFL v1.1

  #612 opened 2 years ago by zimeon
  4

• Fix slack details on https://ocfl.io/

  #618 opened 2 years ago by zimeon
  0

• Validate examples in Markdown spec

  #598 opened 2 years ago by zimeon
  0

• Create change log for 1.1

  #570 opened 2 years ago by zimeon
  1

• Registered extension name clarification

  #565 opened 2 years ago by pwinckles
  8

• Improve description of storage root extensions

  #557 opened 2 years ago by zimeon
  5

• Add formerEditor: Andrew Hankinson

  #599 opened 2 years ago by zimeon
  0

• Change specification source from Respec to Markdown

  #554 opened 2 years ago by zimeon
  6

• Formatting issue: Rationalize definition part of state

  #593 opened 3 years ago by zimeon
  0

• Minor HTML issue: meta tags in implementation notes not closed

  #591 opened 3 years ago by zimeon
  0

• Minor formatting: Closing p tag is wrong

  #588 opened 3 years ago by zimeon
  0

• clarify "same object state" of version block (E066)

  #571 opened 3 years ago by srerickson
  5

• Objects containing multiple namaste files

  #581 opened 3 years ago by pwinckles
  2

• Do we need to clarify that `"fixity": null` is not allowed, or should we allow it?

  #558 opened 3 years ago by zimeon
  18

• Fixity block case sensitivity

  #564 opened 3 years ago by pwinckles
  3

• E070 should refer to "[extension, description]"

  #573 opened 3 years ago by srerickson
  0

• must a manifest entry be referenced in at least one version's state

  #537 opened 3 years ago by pwinckles
  5

• Clarify that `id` must be consistent across all versions

  #542 opened 3 years ago by zimeon
  2

• Do 1.1 compliant objects declare themselves at 1.0 or 1.1?

  #543 opened 3 years ago by zimeon
  3

• validation issues in spec examples

  #539 opened 3 years ago by pwinckles
  3

• Consistently use code font in "xyz block" references

  #562 opened 3 years ago by zimeon
  0

• Do we specify that in the version sequence there must be a monotonic sequence of non-decreasing OCFL version numbers?

  #544 opened 3 years ago by zimeon
  2

• Update author list for 1.1

  #548 opened 3 years ago by zimeon
  1

• Should we version validation_codes.md?

  #553 opened 3 years ago by zimeon
  3

• Update version in text and examples to 1.1

  #551 opened 3 years ago by zimeon
  0

• clarity on manifest requirements in historic inventories

  #538 opened 3 years ago by pwinckles
  0

• Change language to avoid talking about object operations

  #541 opened 3 years ago by zimeon
  0

• Empty versions and object stores

  #535 opened 4 years ago by pwinckles
  8