The group that worked on the public initiative proposal for WP3 ran into trouble regarding some of the element definitions. The first change they made was to eliminate the sub-elements of action and execution had definitions so similar it only made the schema confusing. They decided to remove them from the schema and just allow for the text to be written beneath the approach section. They also decided to make the “who”, “what” and “when” attributes under the scope section mandatory to make the purpose section clearer. They also made the feasibility sub-elements; social, economic and environmental, to type attributes under feasibility.
I am not surprised by the confusion between the action and execution sub-elements as our group was only able to agree on the difference in definition and use of the elements after much debate. It is easy to understand why a new group working with the schema would struggle to understand the difference between the two. I agree with their change to eliminate both attributes as I believe it will make writing the approach section seem less choppy. Making the who, what and when attributes mandatory makes sense as well as they would be included in all proposals as they convey the most essential information concerning a public project. They also suggested adding a clear definition for scope that makes it clear what information it should include. I disagree as it would be somewhat redundant as there shouldn’t be a need for any additional text under scope. The scope is by definition the who, what, why, when and how of the project. Any information under scope should be covered by one of those attributes.
Their change of making the sub-elements of feasibility to type attributes was actually a reversal of a change we made in our revision process. We encountered some schema errors when we had them defined as type attributes as it only allowed for a single feasibility entry with one sub-type. To correct this issue, we decided to change the attributes to sub-elements. In addition to fixing the schema error, this change allowed for a single feasibility paragraph in the case that the proposal was not meant to be as long as a fully developed proposal. Each sentence within that paragraph could then be defined under the appropriate tag, such as social or economic.
The also suggested adding a global reference element that would work with the bibliography to add citations within the proposal. This would give the argument more credence as it would allow for statements within the proposal to be immediately supported by a reference, which a reader could then go to to look up more information that supports the claims made by the author.
Overall, I agree with the changes made by the group to the schema as I believe they will allow for a more streamlined writing process. I agree that there is not a significant difference between the action and execution sections and would leave their changes in the schema. I would not change the scope definition and I would revert the changes made to the feasibility section as I believe it allows for a more flowing argument in the feasibility section.