The scope of the work is to procure a COTS product solution that is customized for authors that have little to no experience with writing XML language

The contractor shall provide COTS software solution for authoring in XML with licenses for up to 1,000 users to create and maintain tax instructions and publications.  This software will assist in authoring tax instructions and publications in XML format to be used as source files in the creation of Portable Document Format (PDF), Hypertext Markup Language (HTML), Docbook XML, and ePub that meets the following features:

1. Compatible with existing IRS DTD
2. Requires minimal retraining < 2 hours
3. Is a web-based solution that can be hosted on site with the ability to be hosted in a cloud environment.
4. Customizable to add customized features and interaction with 3rd party tools, such as Link Author, Adobe AEM Assist, OneDrive, or SharePoint online.
5. A configurable WYSIWYG display that able to closely resemble the PDF using a single column format. Such that when author the user has a very good understanding of how the composed file will look.
6. Standardized linking to the Code of Federal Regulations (CFR), Internal Revenue Code (IRC), Internal Revenue Bulletin (IRB), and Revenue Procedures and Revenue Rulings.
7. Ability to link to specific locations within the XML file. Ability to add anchors within XML file to link to the specific location.
8. Customizable Metadata. Who the owner business unit(s) is, user business unit(s) and author(s). Also need to identify if there is Official Use Only (OUO) within the document, the catalog number, and if active or obsolete.
9. When the software starts up, checking for the values of the respective part title and chapter title of the file in a centralized XML file stored on a web server and update the value within the user’s file. If no value is present on the server, inform the user of such.
10. When user completes the part n.o attribute on the <part> tag, pulling the respective part title from a centralized XML file stored on a web server. If no value is present on the server, inform the user of such.
11. When user completes the chap no attribute on the <chapter> tag, pulling the respective chapter title from a centralized XML file stored on a web server. If no value is present on the server, inform the user of such.
12. Locking <particle> and <chapter title> tags from end user editing. Only the authoring software can alter the content of the tags.
13. Context Rules always on. If there are rules, we need all XML files to follow, why would we allow someone to ever complete actions/edits outside of the rules?
14. Providing the ability to turn off the display of software features that our users will never use.
15. Plain language error messages for explaining context errors in completeness check
16. Plain language text for all menu items, warnings, tooltips and settings within the software
17. Ability to insert tables.
18. Locate controls for features all together--i.e Table editing is in one menu not 4 menus/views.
19. Tables must have a header row. This row is read before all the body rows. This is required for 508 compliance (visually impaired employees who use screen readers).
20. Tables to have a summary (508 compliance).
21. Ability to edit table widths. Currently we have 3 inch, 4.5in, 6.625in and 8.5in.
22. Portrait or landscape tables.
23. Table templates. Can save a table as a template and then insert it anywhere in the IRM.
24. Default table templates already created. Such as if/then table and if/and/then tables.
25. Templates named with plain-language, not abbreviations.
26. For tables: Ability to edit lines between columns, rows and outside border.
27. Ability to copy/paste tables from other sources/software. (Ex. Excel, Word, HTML, PDF).
28. Ability to insert graphics.
29. Graphics must have descriptors, such as paragraphs, lists, etc. This is required for 508 compliance.
30. Ability to view graphics within XML file.
31. A check to resolve any errors. Currently it is called Check Completeness. Such as, if an element or tag has no content within it (empty tag).
32. Ability to find/replace text and tags.
33. Ability to cut/copy/paste text and tags.
34. Ability to copy directly from Microsoft Word and other kinds editing programs. EG, a bullet list from .docx to .xml is recognized and tagged as a bullet list.
35. Ability to select the entire tag(s) and the content within it.
36. Ability to track changes. Accept/reject one change at a time or accept/reject all at once. Ability to view tracked changes, original document, or new document without tracked changes highlighted. Display who made the change at exactly what time.
    1. Show