Talk:Problem Statement

[Ken] Could we have one of the explicit objectives be strategies (or, better still, a single strategy) for round-tripping a document in one format to the other and back again? So, then, a "normative" transliteration between formats without changing the information set behind the documents. My use case is for the OASIS UBL project: I think our UBL community needs an unambiguous JSON transliteration of an arbitrary UBL XML document, and if a user gets a UBL JSON document, they should be able to derive the equivalent UBL XML document.

[MarkB] I think that support for multiple markup on the input side is equally important. There are any number of alternate markup methods with more or less semantic structure that are in wide use, and are easier for authors to create than XML. Examples include markdown, Wiki markup, and Java Doc. There was a discussion recently on the Content Strategy BizTech Google group on the possibility of creating simpler semantic markup format designed for occasional authors. Unfortunately it's a closed group, so you will have to join to see the discussion. My interest in this group is largely about exploring this area, though the equivalency of different forms of markup on the output side is also important to this effort as well.