Re: W3C Proposed Recommendation:

>I know it can be awkward (if one schema imports other schema that 
>exists in seperate files) but I think they be can be referenced via URIs and 
>I wasn't keen to spend lots of time on another schema dependency that could 
>get fairly complex.

xsd:import can probably be used to do the job with schemaLocation='#xxx'
identifying a schema elsewhere in the signature document. The schema
spec states that this "will resolve to a serialization of a schema
document", but that's probably fine; we can resolve it to whatever we
want. So, I'm find with the current text.


Baltimore Technologies plc will not be liable for direct,  special,  indirect 
or consequential  damages  arising  from  alteration of  the contents of this
message by a third party or as a result of any virus being passed on.

In addition, certain Marketing collateral may be added from time to time to
promote Baltimore Technologies products, services, Global e-Security or
appearance at trade shows and conferences.

This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.

Received on Thursday, 30 August 2001 13:34:19 UTC