Hi Gareth (and everyone else),
The use-case ... well ... a team that we support delivers XML to a
post-production conversion process that delivers as its final product a web
... thing (part site, part application). The powers that be want to
refactor all of the technology and process used to support that web thing
with much more scalability / much fewer human touches or hand-offs. One of
the possibilities being considered uses JSON to deliver parts of that web
thing. As such, we are being asked whether the content we currently support
can be delivered to that potential To Be environment and further if it
would scale and support content creation for other parts of the web thing.
I'm currently skeptical that it would make sense to develop an XML to JSON
conversion for the purposes of documentation. I'm downright hostile to the
idea that if it were sensible that it would make sense to do it IN
Arbortext (although it could and likely would certainly make sense to
develop an authoring environment that were specifically developed to
support both the eventual publication format as well as the conversion).
That said, as long as it isn't completely backward cost prohibitive fragile
etc., I would like to extend our reach flexibility services scope etc.
So I was checking to see if anyone had already done this or something
similar. Thus far, you haven't changed my mind about the XML to JSON,
though.
Thanks to all for your responses so far!
On Wed, Nov 26, 2014 at 5:21 AM, Gareth Oakes <->
