I'll probably dedicate a bigger post to this soon, but I wanted to show you a domainmodel, some code and the xml it generates.
What you see here is two attributes that take on quite a bit of work.
EditableBusinessObject implements IEditableObject for you and also allows you to copy the currentvalues to a loadedvalues state.
CreateSerializeSurrogate generates a surrogate class that knows how to deal with loadedvalues and with circular references.
Together, they form the backbone of the client-side of your domainmodel.

Here is an example.

DomainModel:
(notice this is the full class, no other properties are here)

Some testcode:
(notice line 16 where we do a endEdit. If we had cancelled, we would've had a proper rollback)

And the generated xml:
(notice how the lists and 'StringProperty' are changed, and see the original value).

<PersonSurrogate xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="myNamespace">

    <IntLijst xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">

        <d2p1:int>1</d2p1:int>

        <d2p1:int>2</d2p1:int>

    </IntLijst>

    <IntProperty>1</IntProperty>

    <SerializationID>0</SerializationID>

    <StringLijst xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">

        <d2p1:string>a</d2p1:string>

        <d2p1:string>b</d2p1:string>

    </StringLijst>

    <StringProperty>Ruurd Boeke</StringProperty>

    <StringProperty2>Boeke</StringProperty2>

    <OriginalValue_IntLijst xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">

        <d2p1:int>1</d2p1:int>

    </OriginalValue_IntLijst>

    <OriginalValue_IntProperty>1</OriginalValue_IntProperty>

    <OriginalValue_StringLijst xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">

        <d2p1:string>a</d2p1:string>

    </OriginalValue_StringLijst>

    <OriginalValue_StringProperty>Ruurd</OriginalValue_StringProperty>

    <OriginalValue_StringProperty2>Boeke</OriginalValue_StringProperty2>

</PersonSurrogate>

What is left, is deserializing, maybe propagating the beginedit commands to all children and then create the serverside EF variant.
Oh, and I don't like the originalValue representation. Maybe I'll generate a OriginalValue class to keep it tidy.