Jackson can already support multiple formats:
http://wiki.fasterxml.com/JacksonOutsideofJSON
Maybe we should consider making our serialization API compatible with it. Since our API will use most likely much more meta-info in it's specification, it probably makes more sense to have Jackson as an alternative impl of our API, instead of the other way around. This would make our objects automatically serialisable in multiple text formats.
Jackson can already support multiple formats:
http://wiki.fasterxml.com/JacksonOutsideofJSON
Maybe we should consider making our serialization API compatible with it. Since our API will use most likely much more meta-info in it's specification, it probably makes more sense to have Jackson as an alternative impl of our API, instead of the other way around. This would make our objects automatically serialisable in multiple text formats.