|I would expect the community interface to be mostly as follows:|
1. Proposal submission, plain text
2. Viewable output:
If APNIC staff is maintaining the policy document (this assumes an option 2 or option 5 monolithic policy document maintained by APNIC staff), then the XML would be entirely an internal process to APNIC staff. However, the advantage is that with any of a number of XML authorship tools that are now available, APNIC staff could easily convert Text -> XML which can then easily be used to generate HTML, PDF, Text, and possibly other formats.
As such, I’m not sure the community really cares whether APNIC uses XML or some other tool they deem useful, I think the community cares about the input and output formats. I suggested XML as a convenient tool for staff to use to achieve what at least two members of the community have now described as desirable input/output formats.
On Feb 20, 2014, at 2:23 PM, Adam Gosling <adam at apnic dot net> wrote: