XML for Policy and Procedure documentation

[Deb]

I am on a project that involves development of policy and procedure
documentation for Sarbanes-Oxley compliance. I'm thinking developing an XML
framework will provide the most extensibility and opportunities for re-use.
I'm familiar with XML, although have never implemented it in a solution.
Considering that the actual policy language could be any number of pages, are
there any limits on the size of an XML element?

Does anyone have any particular experience in a P&P implementation using XML?

Would InfoPath be the right tool, or would MS Word do well?

One of fthe requirements is to be able to publish each policy individually
as well as part of a PDF on a Sharepoint site.

Any suggestions or help is greatly appreciated.
Thank you!
Deb

 

[Franck Dauché]

Hi Deb,

The main reason to use InfoPath is to give the ability to users to modify
xml documents with a very user-friendly interface. So, the first question
is: do you need to provide data-entry features to your users or do they just
need to read existing documents?

On the other hand, keep in mind that IP is not a great "reporting" tool.
So, second question is: Do you need to provide documents as sophisticated
reports?

If you are more worried about data-entry and modification of the xml,
infoPath is your tool. If the documents are read-only for the end users and
that features from reporting tools are expected, InfoPath may not be your
best option.

Hope that it helps.

Regards,

Franck Dauché

 

[Deb]

Thanks, Frank. Data entry will not be part of the equation. The audience
are reading only. Reporting may become a requirement, althought probably a
low priority one. Re-use and being able to generate varying deliverables are
high priority items.

 

[Franck Dauché]

Hi Deb,

In that case, it is your call. If you are not familiar with any other
product that could do the job, you can give infoPath a try, it is a great
product!

Good luck.

Regards,

Franck Dauché