The HTML ORM viewers (follow links from http://ormsolutions.com, including information on displaying your own diagrams online) offer a reasonable framework for discussion, but this is obviously not a full replica of NORMA at this point.
What's currently showing publicly is a viewer (single diagram in http://ormsolutions.com/tools/orm.aspx and all ORM diagrams in a model at http://ormsolutions/tools/ormPrint.aspx) with no additional information. What we have behind the scenes is an editor framework built on the same fact-centric framework as the viewer, verbalization snippets that work with the web browser, and integrated comment forums that allow model-centric discussions. My 'model-centric' I mean that threads are tied to specific items in the model to provide a targeted discussion. There is theoretically nothing to stop integration with other content-management systems (SharePoint, etc), I just haven't tackled that yet.
While this is a nice start, there is a lot of work still to do to get the web tool to NORMA levels of functionality. The first issue is verbalization (model browser, search, relational diagram display, fact editor, etc. also need to be addressed). Currently, I cheat by programmatically opening the ORM file with modified snippets that work with the web viewer, then upload all verbalizations for the model to a server-side database. This is a reasonable stopgap and performs well under AJAX, but is obviously not a general solution. Verbalizations have a large amount of text and are numerous--the verbalizations for all individual selections in a model is a lot of data. So, until I have a native client-side verbalizer to go with the browser I'm not really ready to throw the doors wide open on this technology because (with all due respect to forum members) I don't want verbalizations from all of your models in my db.
Integrating the web viewer (svg) html into the reports to show graphics for individual elements is also a possibility.