Mitar

So how I imagine this to work is that I extend definitions of fields also to include non-reference fields and then validate documents in [objectify](https://github.com/peerlibrary/meteor-peerdb/blob/master/lib.coffee#L80). Once we have that we...

So I think that PeerDB replaces collection2, but can use simple-schema for compatibility with other packages.

Just for the record, name stays. :-) I have many projects starting with "peer" in this is one of them. :-) It is a family of related projects and while...

I see above also another implicit suggestion, to allow other forms of ID generation. I think that could be made into another ticket and could become part of `Meta` definition...

> I think providing a way to pass default options to the Meteor collection (like idGeneration etc) will be a very good addition. I would not pass things directly, but...

I just published another package, a way to define [publish middleware](https://github.com/peerlibrary/meteor-middleware).

:-) Ah, lovely naming discussions. :-)

I think the best way to find packages is to add links to them to wikis, reference them in mails, etc. :-)

So what would be a better name (package name) in your opinion?

So for me middleware is something intuitive because it is the way [express](http://expressjs.com/4x/api.html#middleware) works. And for me this is exactly what publish is in Meteor, a stack of things you...