5N/AIt might be helpful, for tools development, to offer an XML description
5N/Aof package transactions and manifests.
8N/AThat is, if we're backing into a full fledged package dialect, beyond
8N/Asomething single line-based, then we should consider whether an XML
8N/Adocument is a suitable choice. Usual pro-XML, con-XML position follows.
105N/A1. Specific cases in support.
105N/AMultiline text properties and localized text properties argues for use
105N/ASympathy with <property>, <value>, and <propval> in the smf(5) DTD might
105N/A2. Specific cases against.
105N/AServer side assembly of the transaction into a package version means
105N/Athat the manifest might be difficult to construct. Or maybe not:
105N/Aopen -> <manifest package="...">
105N/A(But accept and publish will require that manifest to be imported and