Enhance a PDF Form for StratML Part 1
Budget: $30 – $250 USD
The PDF form at https://stratml.us/forms/StrategicPlan.pdf (a copy of which is attached) was developed before Strategy Markup Language (StratML) Part 1, the StratML Core, was finalized as an international standard (ISO 17469-1). Two minor changes were made in the final version of the schema that need to be made in the form:
1. The Submitter FirstName element was changed to GivenName.
2. The Submitter LastName element was changed to Surname.
The ISO 17469-1 version of the schema and its documentation are available at https://stratml.us/#Part1
Additionally, for each element that is repeatable, the Add button should be moved to the bottom of the section to which it specifically appplies while the Remove button remains at the top of the section to which it specifically applies.
Currently, both the Add and Repeat buttons appear at the top of the first section and act on the last section among the repeatable items in that group of elements. That is counterintuitive and particulary confusing when the elements added or deleted are below the area presented on the screen and thus not visible to the user. The impression created is that the buttons aren't working.
The Add buttons that should be repositioned to the bottom of the elements to which they apply include those that apply to these elements:
Organization
Stakeholder, in multiple places on the form
Value
Goal
Objective
The Remove buttons should appear at the top of each the elements to which they specifically apply, rather than merely at the top of the first element in the repeatable group of elements.
Finally, in addition to the Import XML and Export XML buttons at the top of the form and third one -- named "Styled XML" -- should be provided that applies the styleseet at https://stratml.us/carmel/iso/part2stratml.xsl
It would be good if the Export XML and Styled XML buttons appeared at the bottom of the form rather than the top but that is not essential. In any event, the Import XML button should remain at the top.
Note: Files must be saved locally by the user. They are not saved to a database or repository and that is intentional. Users should post their strategic plans on their own websites or other interemediary sites they choose to use.
The output from the form must validate against the schema and seemlessly exchange data with the XForm at https://stratml.us/forms2/Part1Form.xml
BTW, I am especially interested in working with partners who are personally supportive of the vision of the StratML standard rather than merely paying for one-off projects like this. So I would be pleased if those willing and able to take on this relatively small project were to brand their version of the enhanced PDF form with their company name and logo so long as it is freely available for usage by anyone who chooses to do so at https://stratml.us/#Forms as well as anywhere else the developer(s) may wish to make it available.
For the broader vision, see https://connectedcommunity.net/ & https://aboutthem.info/ as well as the use cases at https://stratml.us/carmel/iso/UC4SwStyle.xml.
If this project is successfully completed, a natural follow-on project would be to create a PDF form for StratML Part 2, Performance Plans and Reports, that conforms to the schema for Part 2 and thus interchanges data seemlessly with the XForm at https://stratml.us/forms2/Part2Form.xml
Please note that I have also posted a project to create a query service that leverages the semantics and structure of the StratML schema. Unfortnunately, it does not seem that anyone is yet capable of developing such a service at reasonable cost, but it would be nice to think that experience with a relatively simple project like this might eventually lead to the development of more complex, value-added services like those listed at https://stratml.us/carmel/iso/SMLTASwStyle.xml
1. The Submitter FirstName element was changed to GivenName.
2. The Submitter LastName element was changed to Surname.
The ISO 17469-1 version of the schema and its documentation are available at https://stratml.us/#Part1
Additionally, for each element that is repeatable, the Add button should be moved to the bottom of the section to which it specifically appplies while the Remove button remains at the top of the section to which it specifically applies.
Currently, both the Add and Repeat buttons appear at the top of the first section and act on the last section among the repeatable items in that group of elements. That is counterintuitive and particulary confusing when the elements added or deleted are below the area presented on the screen and thus not visible to the user. The impression created is that the buttons aren't working.
The Add buttons that should be repositioned to the bottom of the elements to which they apply include those that apply to these elements:
Organization
Stakeholder, in multiple places on the form
Value
Goal
Objective
The Remove buttons should appear at the top of each the elements to which they specifically apply, rather than merely at the top of the first element in the repeatable group of elements.
Finally, in addition to the Import XML and Export XML buttons at the top of the form and third one -- named "Styled XML" -- should be provided that applies the styleseet at https://stratml.us/carmel/iso/part2stratml.xsl
It would be good if the Export XML and Styled XML buttons appeared at the bottom of the form rather than the top but that is not essential. In any event, the Import XML button should remain at the top.
Note: Files must be saved locally by the user. They are not saved to a database or repository and that is intentional. Users should post their strategic plans on their own websites or other interemediary sites they choose to use.
The output from the form must validate against the schema and seemlessly exchange data with the XForm at https://stratml.us/forms2/Part1Form.xml
BTW, I am especially interested in working with partners who are personally supportive of the vision of the StratML standard rather than merely paying for one-off projects like this. So I would be pleased if those willing and able to take on this relatively small project were to brand their version of the enhanced PDF form with their company name and logo so long as it is freely available for usage by anyone who chooses to do so at https://stratml.us/#Forms as well as anywhere else the developer(s) may wish to make it available.
For the broader vision, see https://connectedcommunity.net/ & https://aboutthem.info/ as well as the use cases at https://stratml.us/carmel/iso/UC4SwStyle.xml.
If this project is successfully completed, a natural follow-on project would be to create a PDF form for StratML Part 2, Performance Plans and Reports, that conforms to the schema for Part 2 and thus interchanges data seemlessly with the XForm at https://stratml.us/forms2/Part2Form.xml
Please note that I have also posted a project to create a query service that leverages the semantics and structure of the StratML schema. Unfortnunately, it does not seem that anyone is yet capable of developing such a service at reasonable cost, but it would be nice to think that experience with a relatively simple project like this might eventually lead to the development of more complex, value-added services like those listed at https://stratml.us/carmel/iso/SMLTASwStyle.xml