Export (0) Print
Expand All

3 Structure Examples


In the following sections, the schema definition might differ from the processing rules imposed by the protocol. The XSD in this specification provides a base description of the file format. The text that introduces the XSD specifies additional restrictions that reflect protocol behavior. For example, the schema definition might allow for an element to be empty, null, or not present but the behavior of the protocol as specified restricts the same elements to being non-empty, present, and not null.

The following XML is an example of a CoAuthoringLocks element.

<CoAuthoringLocks xmlns="http://schemas.microsoft.com/word/2009/7/coauthoring">
    <Lock xmlns="" OwnerID="{38A992A1-8CDB-4D8B-B881-7D7E45E06B72}" OwnerName="Claus Hansen" OwnerSIPAddress="sip:claus@example.com" OwnerEmailAddress="claus@example.com" OwnerUserName="claus" LockId="76224563">
        <ParaId Val="4F2EB091"/>
    <Lock xmlns="" OwnerID="{33B5F63F-E6B4-41AA-B64E-552D8127DF2B}" OwnerName="Jeff Hay" OwnerSIPAddress="sip:jeff@example.com" OwnerEmailAddress="jeff@example.com" OwnerUserName="jeff" LockId="316786F3">
        <ParaId Val="4D3895E6"/>
        <ParaId Val="0EDB6FA0"/>
        <LockId Val="3F459ACD" TimeStamp="2009-05-14T00:18:14Z"/>

The first <Lock …/> element shows that an author named Claus Hansen is present within the region described by <ParaId Val="4F2EB091"/>. This region has the LockId value of "76224563".

The second <Lock …/> element shows that an author named Jeff Hay is present within the region described by the two <ParaId …/> entries. This region has the LockId value of "316786F3".

The <DeletedLocks …/> element indicates that a presence region with the LockId value of "3F459ACD" existed at one time, but that the author who was using it removed his or her presence as of the time given by TimeStamp.

© 2014 Microsoft