Author: lazer.s

I found the schema helpful as a template for the structure of my Writing Project 2 draft. Organizationally it provided a good overview of the sections commonly used to create a compelling proposal, and the definitions helped to further clarify these components.  However, I think the schema would benefit from more structural flexibility. Having all content be required to fit into one of the predefined categories does not make it a very versatile tool. For example, a person might struggle to mark-up a proposal that was not composed using the schema as a guide, as all parts of the text may not conform to the options it offers. With changes to the hierarchical relationship between the <p> elements and the structural components, such as <feasibility> and <approach>, I believe the schema will be much better suited for general use and analysis, rather than just composition.  Going forward, when making revisions to our schema it might be helpful to keep in mind all possible uses of the schema in order to make it the most useful tool it can be.

Proposals can be commonly found in many different fields. At the most basic level a proposal is merely a written suggestion for submission and consideration by an audience. For writing project 2, my group is taking a closer look at the particulars of public initiative proposals. These texts’ goal is to introduce an idea for a project that will improve a community, as well as address the benefits of implementing it, and the possible challenges that may be encountered throughout the implementation proccess.

There is a very strong correlation between the texts of public initiative proposals and RFPs (request for proposal) . As an official solicitation, RFPs directly reference project proposals, and in most cases, these proposals originate as responses to RFPs. Though these texts frequently exist within this formalized call-and-response structure they remain readily understandable to the most audiences, not just those in the trade, due to their public nature. Additionally, the project proposal may be seen as the progenitor for all subsequent documents relating to a project. Texts such as design reviews, feasability reports, etc. all will use the original proposal as a reference source.

For my most recent co-op I was working at a medical device company that produces tubeless insulin pumps for diabetics. As an FDA regulated company, I was involved with the design, construction, and execution of some of the many verification and validation tests we were required to perform by law.  Many of my peers and coworkers’ work and expertise fell very rigidly into the category of mechanical engineering. However, as a result of my preexisting knowledge of other disciplines, I was frequently put to work on projects that required interdisciplinary work. It is in my personal nature to seek to understand all aspects of a project, it is not required of the job. This can sometimes lead to the frustrating situation where, when working on a project with a partner with the same responsibilities as you, you are able to assist them with any aspect of work they are performing, while you are left to do the interdisciplinary work alone.

I think knowledge of many disciplines is beneficial to any environment, especially in the field of engineering. These days, few engineering applications can be found that can be considered “pure” mechanical, electrical, computer etc. work. The more you already know the more connections you can make both between your existing knowledge, as well as when learning new concepts.  Having interdisciplinary knowledge will make you a more valuable asset to any team.

Using XML markup on this project did not feel like a drastic change in pace for me. My writing process usually involves creating an outline and then fleshing it out with detail until it’s almost the prose that will be in the final product, so in a way, using a markup language was very similar to this only with the addition of some extra technical formatting.

The development of the schema as a class had both its pros and cons. By composing the schema as a group, a good portion of the preliminary work I would do in structuring the assignment was already done. However, at times I felt the thought I wanted to express had to be slightly contorted to fit into the rigid structure we had created.