Jangle (Just Another Next Generation Library Environment) is an open source project designed to facilitate API access to Library Systems. If you build, use, manage or just want simple access to a library system and would like to get involved, join the Google Group or visit the project pages and become part of the project.
This registry is intended to help define authoritative identifiers for negotiating requests for specific metadata types in standards such as Jangle or unAPI.
The identifiers themselves arbitrary; while consistency is helpful, it's not mandated. Also using a term that makes sense for a given format (such as the explicit mime-type or namespace) will be more intuitive. The important part is to have agreement on exactly what a given identifier stands for.
HOWTO build a Jangle connector
Note, everything here is negotiable. If you have a better idea for anything, please provide comments!
All GET requests should return a JSON object with the following keys:
time, string
UTC timestamp of request
request, string
returns the path and query string of the incoming request,
data, array
an array of objects,
While the simpler of the two architectural components (core and connector), the Jangle core has the distinction of being public face of Jangle and therefore the only part of Jangle that most people should ever have to see.
The core, in essence, is an Atom Publishing Protocol proxy to the registered backend connectors. It routes the HTTP requests to the connectors, and serializes the JSON responses to Atom feeds.
There is quite a bit of confusion over what Jangle actually is and I, myself, have at times been one of the confused as well. Since the scope and focus of Jangle has changed dramatically (although not completely fundamentally) since its inception as a project, there is a lot of detritus about past ideas of what Jangle is or should be. While it's possible that the current direction of Jangle might join that flotsam, I think we've found a reasonable direction.
So, what is Jangle?