Post Meta Library Design Pattern Summaries

I’ve written two design pattern summaries, one for Fieldmanager and one for Custom Metadata Manager, and I’d suggest anyone who wants to contribute right now to write one. Each library makes their own assumptions about what a metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data object is, how it should be incorporated into the UIUI User interface, with striking differences, although the end result is more or less similar. These differences are what is important.

Pieces of software are like organisms. Each of these post meta libraries has a different biological structure; we get to dissect this software, and pick apart the design patterns and analyze their utility and uniqueness.

I think my pattern review of Fieldmanager is most on point in what we need to highlight for discussion. Also, please note: everyone has comment access, that is for a reason ;). Peer review and commenting welcome.

At this point, we need to decide what a meta data object should be. In that regard, questions to keep in mind while writing a design pattern summary: What is meta data in the eyes of this library? How are meta data objects described? Are there other distinct objects? How do they relate to each other? If any, what are the separations of responsibilities between these different components?