- Sep 1, 2002Mark Baker
> I just talked to my wife (a lawyer) about this, and what wediscussed
> pretty much jives with what I've said in this thread.Please pass on thanks to your wife.
> Basically, if onereference it
> contract depends on some detail of another, then either a)
> if the referencing system can guarantee that dereferencing it willcontract
> always produce the identical contract, or b) include the other
> as an attachment. She said it's easier to include as an attachmentthan
> to try to cut and paste chunks out of it, because some context mayget
> lost in doing so.That's different from the situation I thought we were discussing.
(Although some of the same principles would apply.)
The two situations:
1. One contract refers to another contract (as above).
2. Messages about contract fulfillment events (e.g. deliveries of
goods and services or payments) refer to governing contract clauses
(as I thought we were discussing).
The usual practice with deliveries is to refer to the governing
contract (e.g. purchase order) by order ID (maybe + line number), not
to attach the whole PO. I expect the same would work for REST.
> The difference there from my previous statements, is that it's safeto
> use a reference in the case where the details of the other contractYes, and don't you think something like Paul's reference format (URI
> matter, iff it can be guaranteed to always refer to exactly that
+ hash) is the way to do it?
> Maybe some examples would help ...Coming up...
- << Previous post in topic Next post in topic >>