You’re right – eaDocX assumes that the file is simply stored on a disk, so won’t open it from a URL.
This is what I mean about needing the change eaDocX to support Sharepoint!
I have a man who knows SharePoint – I’ll talk to him to see what support we can provide (in a future version, after 3.3)

As for document classification, this is a good idea.
What should it look like?
Is it enough to have a new attribute of ‘Classification’ – probably implemented as TaggedValue of the <>Artifact. (BTW – you could already do this manually..)
Would a document behave differently, depending on the security classification? Save in a different EA Package in the EA Repository ? Anything else ?