Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

There are two factors that define require a major release:

  1. breaking changes to the API
  2. required backend data migration

...

  • A robust test suite should be part of that milestone.


new fcrepo-vocabulary repository

  • reduces potential for misspellings
  • uses RDF commons  - a level of abstraction above Jena.
  • in labs right now
  • should wait to merge into core until after the next version (0.3) of that alignmentRDF commons comes out.
  • increases reusability
  • Unknown User (acoburn)  :  would like to keep the included ontologies to what is being used in the code.

API Specification - Taking it to the streets

A. Soroka has institutional support to move the process forward.  He is working to get the API (starting with the core) to the point where we can put it out to the wider community for feedback.

Perhaps we need a document that shows the delta between  the reference implementation and the API  today.  We could use this to track our progress towards 5.x.  Non-Adam's could help on this.

Aisha: Maybe consider looking at https://apiblueprint.org/..

 

Move Yinlin's tests into fcrepo4-labs

...