XML2RFC RFP Q & A 17 March 2011 Q1: Please indicates which operating systems and versions have to be supported: a. Microsoft Windows (Windows 7, Windows Vista, Windows XP - SP2?, ...). A1a. Should run on at least Win 7 and Win XP SP3. b. Linux ( Redhat, Debian, Ubuntu, ...): (i) Is distribution specific packaging required (.deb, .rpm, ...), or a python package (distutils, setuptools, ...) would be enough? A1b. Want .rpm and .deb install packages, setuptools install is a plus. Should run on debian, ubuntu, openSuse, fedora, mint. c. MacOs: ... A1c. Should run on OS X 10.4, 10.5, 10.6. Q2: We don't understand the sentence "This enhancement will also require that the web server support allow a user to provide their personal citations library along with the currently provided XML file containing the document" (within Personal citation library additions) because what is required is a desktop application. A2. When xml2rfc is used on the Apache Server, the user must provide the .xml file and their personal citation library additions. The server will already have the other citation libraries, so that they do not need to be uploaded. The needed files can be uploaded separately or they can be combined into a ZIP file. Q3: Would it be a desirable approach to implement the solution as a web application that can be run from a desktop shortcut? (as in http://toolsforagile.com/blog/archives/51) A3. No. The xml2rfc tool must be able to be run without being connected to the Internet, and a command-line interface is essential. A native GUI would provide additional value. If a GUI is built, a native GUI implementation on each platform is preferred, but other proposals will be considered, meaning: Windows: WinAPI Linux: KDE/Qt or Gnome OS X: Cocoa Therefore, it is suggested that native GUI be proposed as an option. Q4: Does the Python version need a GUI or is a command-line-only interface acceptable. A4. Command-line is essential, native GUI is a plus. Q5: If it does need a GUI, is there a GUI toolkit that is preferred? A5. If a GUI is built, a native GUI implementation on each platform is preferred, even if other proposals will be considered, meaning: Windows: WinAPI Linux: KDE/Qt or Gnome OS X: Cocoa Therefore, it is suggested that native GUI be proposed as an option.