Create a "manifesto" repository in the IIIF organisation that handles the "live" object, keep current "manifesto" as the server.

[aeschylus]

I would like to get started on the bare "implementation of spec with getters and setters" version of "manifesto". Since this repository is an express server with REST methods for dealing with manifests, I have tentatively called the IIIF repo "manifesto-client", but would like to change the name to "manifesto".

Keeping the server/REST interface separate from the model implementation seems advantageous. Ideas, comments?

[aeschylus]

"manifesto" and "manifesto-server"?

[sdellis]

I have no objection to using the "manifesto" name for the bare-bones "SDK" implementation, so I say run with it! This was simply a way to create a playground for me to test out editing a variety of manifest and annotationList documents (and perhaps bundle it as a way of testing viewer apps' REST interactions). Manifesto-server works for this one... or perhaps post-ulate? theo-rest?. :)

[sdellis]

At the risk of being too clever, "creed" might work too (Create REad Edit Delete). Anyway, I'll come up with something for this. Carry on, and looking forward to participating!

[aeschylus]

Alright. I've changed it over. See https://github.com/IIIF/manifesto. It will be interesting to see these two co-evolve.