[MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure

Transcription

1 [MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@microsoft.com. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit Fictitious Names. The example companies, organizations, products, domain names, addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, address, logo, person, place, or event is intended or should be inferred. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. 1 / 21

2 Revision Summary Date Revision History Revision Class Comments 04/04/ Major Initial Availability. 06/27/ Editorial Revised and edited 12/12/ Editorial Revised and edited 03/11/ Editorial Revised and edited 04/06/ Editorial Revised and edited 08/07/ Minor Updated 11/06/ Editorial Revised and edited 03/05/ Minor Updated 04/21/ Editorial Revised and edited 06/04/ Editorial Revised and edited 09/03/ No change No changes to the meaning, language, or formatting of 02/09/ No change No changes to the meaning, language, or formatting of 07/07/ Minor Clarified the meaning of 11/03/ No change No changes to the meaning, language, or formatting of 01/19/ Major Significantly changed 02/23/ No change No changes to the meaning, language, or formatting of 03/27/ No change No changes to the meaning, language, or formatting of 05/24/ No change No changes to the meaning, language, or formatting of 06/29/ No change No changes to the meaning, language, or formatting of 07/16/ No change No changes to the meaning, language, or formatting of 10/08/ No change No changes to the meaning, language, or formatting of 10/23/ No change No changes to the meaning, language, or formatting of 2 / 21

3 Date Revision History Revision Class Comments 03/26/ No change No changes to the meaning, language, or formatting of 06/11/ Major Significantly changed 08/08/ No change No changes to the meaning, language, or formatting of 12/05/ No change No changes to the meaning, language, or formatting of 02/11/ No change No changes to the meaning, language, or formatting of 05/20/ No change No changes to the meaning, language, or formatting of 3 / 21

4 Contents 1 Introduction Glossary References Normative References Informative References Overview Relationship to Protocols and Other Structures Applicability Statement Versioning and Localization Vendor-Extensible Fields Structures DiffGram Namespaces SharePoint DiffGram High-Level Structure SharePoint DiffGram Schema Element DataInstance Element Schema DataTable Element Schema Unique Element SharePoint DiffGram Data Element DataInstance Element Structure Examples Security Considerations Appendix A: Product Behavior Change Tracking Index / 21

5 1 Introduction The Windows SharePoint Services DataSet DiffGram structure is used to represent the results of a Windows SharePoint Services Search service web-service call. This structure is a subset of the full DiffGram structure that is used by the ADO.NET DataSet. The DiffGram structure is useful for serializing schema and data for transmission over a network or storage on disk. Windows SharePoint Services uses the DiffGram structure to encapsulate both the schema of the search results as well as the data that represents the search results. This document covers only the portion of the DiffGram structure that is used by the Windows SharePoint Services Search service. Sections 1.7 and 2 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC All other sections and examples in this specification are informative. 1.1 Glossary The following terms are defined in [MS-GLOS]: Hypertext Transfer Protocol (HTTP) User Datagram Protocol (UDP) XML The following terms are defined in [MS-OFCGLOS]: CDATA section child element root element SOAP (Simple Object Access Protocol) SOAP envelope web service web service method XML attribute XML document XML element XML namespace XML namespace prefix XML schema (1) The following terms are specific to this document: MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT. 1.2 References References to Microsoft Open Specifications documentation do not include a publishing year because links are to the latest version of the documents, which are updated frequently. References to other documents include a publishing year when one is available. 5 / 21

6 1.2.1 Normative References We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact dochelp@microsoft.com. We will assist you in finding the relevant information. [MC-ADONETDSSS] Microsoft Corporation, "ADO.NET DataSet Structure Schema", [MS-SEARCH] Microsoft Corporation, "Search Protocol Specification", June [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, [SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", May 2000, [XMLNS] Bray, T., Hollander, D., Layman, A., et al., Eds., "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, December 2009, [XMLNS3] See [XMLNS]. [XMLSCHEMA1] Thompson, H.S., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, [XMLSCHEMA2] Biron, P.V., and Malhotra, A., Eds., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, [XPATH] Clark, J. and DeRose, S., "XML Path Language (XPath), Version 1.0", W3C Recommendation, November 1999, Informative References [MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary". [MS-OFCGLOS] Microsoft Corporation, "Microsoft Office Master Glossary". [RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999, Overview The DataSet is the part of the.net Framework that provides in-memory representation of relational data. A DataSet consists of a set of named tables. Each table is defined by a collection of named columns with specified data types. A set of columns in the table can also represent a primary key. When a DataSet is populated, its tables are filled with rows of data, each of which contains a value for each column. The DataSet is a completely in-memory representation of the relational data, and maintains no knowledge of the original source of the data. In addition to storing data in the rows and columns of the DataSet, applications can attach additional data to the entire DataSet, or to particular tables or columns, via extended properties. Extended properties are name-value pairs that are exposed to consumers of the DataSet, but not interpreted by the DataSet in any way. For details on how extended properties are used in the context of a SharePoint search, please see [MS-SEARCH]. 6 / 21

7 In various scenarios, it is necessary to transfer a DataSet across application boundaries. This is usually accomplished by serializing the DataSet into a format suitable for transmission over the serialization substrate. Common patterns include returning a DataSet from a web service method and taking DataSets as input parameters to web service methods. The DiffGram structure is an XML serialized form of a DataSet that can be used in these scenarios. Any DataSet instance can be serialized into a DiffGram that can be transmitted over a service interface or written to persistent storage. The DiffGram structure encapsulates all of the information required to re-create the in-memory DataSet in the exact state it was in at the time it was serialized. This includes the schema information that defines the structure of the data in the DataSet and the actual values of the data. The DiffGram also contains serialized representations of any extended properties that have been defined on the tables and/or columns. 1.4 Relationship to Protocols and Other Structures The DiffGram structure is used by the ADO.NET Framework as a serialization format for the contents of DataSets. Whenever a DataSet is returned from or received by a web service method, the DiffGram structure is used as the default serialization format. When used this way, the DiffGram can be wrapped in other data structures (for example, as specified in [SOAP1.1], Section 4) that encapsulate other parts of the web service call. The services that exchange DataSets can use a variety of network protocols and encodings to transfer DiffGrams. For example, one web service can choose to use a plain-text encoding of a DiffGram within a Simple Object Access Protocol (SOAP) envelope, transmitted using Hypertext Transfer Protocol (HTTP) as specified in [RFC2616]. Another can choose a binary encoding for the SOAP envelope containing the DiffGram and transmit it via User Datagram Protocol (UDP). The network protocols and encodings that can be used to transmit DiffGrams are not covered in this document. 1.5 Applicability Statement The DiffGram structure can be used whenever a serialized representation of a DataSet is needed. More generally, the DiffGram can be used whenever it is necessary to serialize relational data. This document specifies the serialization of the relational data as used by the Windows SharePoint Services Search service, but it does not cover the general case of DataSet serialization. 1.6 Versioning and Localization None. 1.7 Vendor-Extensible Fields None. 7 / 21

8 2 Structures The SharePoint DiffGram is an XML document that encapsulates the following information: An XML Schema (1) that specifies the structure of the data in a DataSet The data in the DataSet Extended properties associated with tables and columns The following sections provide details on the particular representation used to capture this information. 2.1 DiffGram Namespaces The XML that comprises a SharePoint DiffGram MUST include required XML elements and XML attributes as specified in the following sections of this document. These XML elements and XML attributes are defined in various XML namespaces. The following table lists these XML namespaces and specifies the XML namespace prefixes commonly associated with them. Producers of SharePoint DiffGrams MUST ensure that the XML refers to these namespaces by using the mechanisms that are specified in [XMLNS], but they SHOULD use the prefixes shown in the table below. For clarity, when XML elements and attributes from these namespaces are referenced in following sections of this document, their fully-qualified names are used. Description Namespace URI Commonly used Prefix Reference XML schema (1) elements and attributes xs [XMLSCHEMA1] [XMLSCHEMA2] DiffGram elements and attributes urn:schemas-microsoft-com:xmldiffgram-v1 diffgr This namespace is internal to the DiffGram structure and is specified in SharePoint DiffGram Data Element. DataSet specific annotations urn:schemas-microsoft-com:xmlmsdata msdata [MC-ADONETDSSS] DataSet extended properties urn:schemas-microsoft-com:xmlmsprop msprop User and application-specific information SHOULD be annotated on the DataSet schema with extended properties. The extended properties are defined in this namespace. 2.2 SharePoint DiffGram High-Level Structure A valid SharePoint DiffGram MUST conform to the following rules: The SharePoint DiffGram MUST have a root element, hereafter referred to as the Root element. The Root element MUST have two child elements: 8 / 21

9 The first child element, hereafter referred to as the SharePoint DiffGram Schema element, MUST be a Schema element as defined by [XMLSCHEMA1] and [XMLSCHEMA2] and MUST contain a valid XML schema (1). The second child element, hereafter referred to as the SharePoint DiffGram Data element, MUST be a DiffGram element as defined in the namespace urn:schemas-microsoft-com:xmldiffgram-v1. The sections that follow define the SharePoint DiffGram Schema element and the SharePoint DiffGram Data element in more detail. At a basic level, the purpose of these elements can be explained as follows: The SharePoint DiffGram Schema element defines the XML Schema for the data representation in the SharePoint DiffGram Data element s content. The XML representation of the data in the SharePoint DiffGram Data element s content MUST conform to the XML Schema defined in the SharePoint DiffGram Schema element. The SharePoint DiffGram Data element encapsulates the values of the data in the DataSet. 2.3 SharePoint DiffGram Schema Element The Schema element in a SharePoint DiffGram MUST contain an XML Schema, as specified in [XMLSCHEMA1] and [XMLSCHEMA2], that defines an XML representation for the data in the DataSet. The SharePoint DiffGram Schema element is a representation of the shape of the DataSet that will be used for serialization purposes, with the tables, columns, and primary keys of the DataSet represented as anonymous complex types and unique elements, subject to various constraints specified in the following sections DataInstance Element Schema The DataInstance schema MUST define exactly one element that will encapsulate the representation of all data in the DataSet. This element is referred to as the DiffGram DataInstance element. In addition to being a valid XML schema (1), this schema MUST conform to the following rules: The DataInstance element MUST be defined using an anonymous complex type. The complex type MUST be defined as a choice of element content with zero minimum occurrence and unbounded maximum occurrence. Each element in the choice MUST conform to the rules of the element definition specified in section The DataInstance element definition MUST contain zero or more DataTable element definitions in the choice element. The DataTable element definitions are immediate children of the choice. The element with namespace that defines the DataInstance element MUST have the urn:schemas-microsoft-com:xml-msdata:isdataset attribute set to true (value of "true" or "1"). The DataInstance element MUST contain zero, one, or more Unique elements. The Unique element s definitions are defined immediately after the complex type element that defines a choice of DataTable elements. The DataInstance element complex type definition MUST NOT contain attribute definitions for the element with namespace 9 / 21

10 The element with namespace that defines the DataInstance element may contain the urn:schemas-microsoft-com:xmlmsdata:usecurrentlocale attribute. If this attribute is present, the value of the attribute MUST be set to true (value of "true" or "1") or false (value of "false" or "0"). The element with namespace that defines the DataInstance element may have the urn:schemas-microsoft-com:xmlmsdata:datasetname attribute. If this attribute is specified, then the name of the DataSet is equal to the value of the attribute. If this attribute is not specified, then the name of the DataSet is equal to the name of the DataInstance element. Each extended property MUST appear as an attribute in the declaration of the DataInstance element (for properties that apply to the whole DataSet). The attribute name MUST be the name of the extended property, and the attribute s namespace MUST be urn:schemas-microsoftcom:xml-msprop. The attribute s value MUST be the value of the extended property. Any attributes with a namespace other than urn:schemas-microsoft-com:xml-msprop are not extended properties DataTable Element Schema The DataInstance schema MUST define zero or more DataTable elements as children of the DataInstance element. A DataTable element MUST be defined using an anonymous complex type, and conform to the following rules: A DataTable element complex type definition MUST NOT contain attribute definitions. A DataTable element definition MUST allow only element content. A DataTable element definition MUST define zero or more DataColumn element definitions that are the immediate children of the sequence. The content model of a DataTable element definition MUST be specified as a sequence of elements, referred to as DataColumn elements, each of which represents a column in the table. The type of a DataColumn element definition MUST be specified as one of the following valid If the type is a string, the type can be a simple type restriction of the facets as defined by [XMLSCHEMA2] section , length, minlength, and maxlength. All other types MUST NOT be restricted. string Boolean unsignedbyte base64binary double float short int long 10 / 21

11 byte integer decimal date time unsignedshort unsignedint unsignedlong datetime The minimum occurrence of a DataColumn element definition MUST be zero or one and the maximum occurrence MUST be one. If the type of the DataColumn element definition is a string, then all data in the DataColumn instance MUST be interpreted as CDATA section, even if it contains data that could be interpreted as XML. Each extended property MUST appear as an attribute in the declaration of the DataColumn element (for properties that apply to columns). The attribute name MUST be the name of the extended property and the attribute s namespace MUST be urn:schemas-microsoft-com:xmlmsprop. The attribute s value MUST be the value of the extended property. Any attributes with a namespace other than urn:schemas-microsoft-com:xml-msprop are not extended properties. Each extended property MUST appear as an attribute in the declaration of the DataTable element (for properties that apply to tables). The attribute name MUST be the name of the extended property and the attribute s namespace MUST be urn:schemas-microsoft-com:xmlmsprop. The attribute s value MUST be the value of the extended property. Any attributes with a namespace other than urn:schemas-microsoft-com:xml-msprop are not extended properties. The following is a sample Schema element from a DiffGram: <xs:schema xmlns:xs=" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:msprop="urn:schemas-microsoft-com:xml-msprop"> <xs:element name="salesds" msdata:isdataset="true"> <xs:complextype> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:element name="customers" msprop:extprop1="usa"> <xs:complextype> <xs:sequence> <xs:element name="custid" type="xs:int" minoccurs="0"/> <xs:element name="custname" type="xs:string" minoccurs="0"/> </xs:sequence> </xs:complextype> </xs:element> </xs:choice> 11 / 21

12 </xs:complextype> <xs:unique name="constraint2" msdata:primarykey="true"> <xs:selector xpath=".//customers" /> <xs:field xpath="custid" /> </xs:unique> </xs:element> </xs:schema> In this sample, the element SalesDS defines the DataInstance element. It can contain Customers elements, which are known as DataTable elements, corresponding to rows in the Customers table in the DataSet. The columns of the Customers table (CustId and CustName), which are known as DataColumn elements, are represented as child elements of the Customers element. The primary key of the DataTable element is specified in the Unique element. The selector defines which DataTable element to reference. The field element defines what DataColumn element is part of the primary key. An extended property on the Customers table, ExtProp1 is manifested as an attribute on the Customers DataTable element declaration Unique Element A Unique element is specified as an XML element per [XMLSCHEMA1] and [XMLSCHEMA2] specifications. A Unique element MUST follow these rules: The element MUST have an urn:schemas-microsoft-com:xml-msdata:primarykey where the value is equal to true (value of "true" or "1"). The selector xpath attribute value MUST use './/data-table' XPath-abbreviated syntax described in section 2.5 of the [XPATH] specification where data-table is the name of a DataTable element. A field xpath attribute value MUST use the 'data-column' XPath-abbreviated syntax where datacolumn is the name of a DataColumn element. The following is an example of a Unique element: <xs:unique name="constraint2" msdata:primarykey="true"> <xs:selector xpath=".//customers" /> <xs:field xpath="custid" /> </xs:unique> 2.4 SharePoint DiffGram Data Element Conceptually, the SharePoint DiffGram Data element encapsulates the XML representation of the data in the DataSet. The SharePoint DiffGram Data element MUST have one child element: A DataInstance element, which MUST conform to the DataInstance element definition specified in the SharePoint DiffGram Schema element. This high-level structure is defined by the following XML Schema: <?xml version="1.0" standalone="yes"?> <xs:schema targetnamespace="urn:schemas-microsoft-com:xml-diffgram-v1" xmlns="urn:schemas-microsoft-com:xml-diffgram-v1" xmlns:xs=" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1" attributeformdefault="qualified" 12 / 21

13 elementformdefault="qualified"> <xs:attribute name="id" type="xs:string"/> <xs:element name="diffgram"> <xs:complextype> <xs:sequence minoccurs="0" maxoccurs="1"> <xs:any namespace="##other" processcontents="lax" minoccurs="0"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> However, it is not possible to write a single schema for the SharePoint DiffGram Data element that properly defines the DataInstance element, because the schema of the DataInstance element is defined by the SharePoint DiffGram Schema element (and varies per DataSet). Therefore, the schema specified previously in this section allows any content in the place of the DataInstance element. Producers and consumers of DiffGrams MUST ensure that the DataInstance element complies with the schema defined in the SharePoint DiffGram Schema element, as specified in section The following section defines the parts of the SharePoint DiffGram Data element in more detail DataInstance Element The DataInstance element may contain one child element named DocumentElement. The DocumentElement MUST contain zero or more first-level child elements, referred to as "row elements". If the DocumentElement is not present, then the DataInstance element MUST contain zero or more row elements. Each row element MUST conform to a DataTable element definition, as specified in section A row element MUST contain zero or more first-level child elements, referred to as "column elements". Each column element MUST conform to a DataColumn element definition. A column element s content represents a data value. A NULL data value is represented by the absence of a column element in a row element, or by using the attribute. The following is an example of a DataInstance element that can appear in a SharePoint DiffGram Data element: <SalesDS> <Customers diffgr:id="customers1" msdata:roworder="0" > <CustId>1</CustId> <CustName>C1</CustName> </Customers> <Customers diffgr:id="customers2" msdata:roworder="1"> <CustId>2</CustId> <CustName>C2</CustName> </Customers> <Customers diffgr:id="customers3" msdata:roworder="2" > <CustId>3</CustId> <CustName>C3</CustName> </Customers> </SalesDS> The following rules apply to the row elements within the DataInstance element: 13 / 21

14 Each row element MUST have an urn:schemas-microsoft-com:xml-diffgram-v1:id attribute. The string value of this attribute acts as the row identifier within the scope of the DiffGram Data element. The DataInstance element MUST NOT have two row elements with the same value for the urn:schemas-microsoft-com:xml-diffgram-v1:id attribute. Each row element MUST have an urn:schemas-microsoft-com:xml-msdata:roworder attribute whose value MUST be an integer that specifies the 0-based ordinal position of the row element. The DataInstance element MUST NOT have two row elements with the same value for the urn:schemas-microsoft-com:xml-msdata:roworder attribute. The value for the urn:schemas-microsoft-com:xml-msdata:roworder attribute MUST be less than the count of the rows in the DataInstance element. Each row element may have an urn:schemas-microsoft-com:xml-msdata:haschanges attribute. If this attribute is specified, the value MUST be "inserted", "modified", or "decent". 14 / 21

15 3 Structure Examples Consider a SharePoint Search with the keywords "Cool Bikes". The results consist of a DataSet containing one DataTable named "RelevantResults", which contains the results of the search. This DataSet is serialized into an XML document that consists of one DataTable element with the name RelevantResults, with a number of child DataColumn elements. Note that while the type of the HitHighlightedProperties DataColumn is a string, the contents appear to be XML. However, they are serialized by the DataSet as a string, not XML, and are not encoded as XML. The following XML is the DiffGram structure that encapsulates this search result: <?xml version="1.0" encoding="utf-8"?> <DataSet xmlns=" <xs:schema id="results" xmlns="" xmlns:xs=" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:msprop="urn:schemas-microsoft-com:xml-msprop"> <xs:element name="results" msdata:isdataset="true" msdata:usecurrentlocale="true" msprop:queryterms="cool Bikes;" msprop:ignorednoisewords="" msprop:keyword="" msprop:elapsedtime="938" msprop:definition="" msprop:spellingsuggestion=""> <xs:complextype> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:element name="relevantresults" msprop:totalrows="175" msprop:istotalrowsexact="false"> <xs:complextype> <xs:sequence> <xs:element name="workid" type="xs:long" minoccurs="0" /> <xs:element name="rank" type="xs:long" minoccurs="0" /> <xs:element name="title" type="xs:string" minoccurs="0" /> <xs:element name="author" type="xs:string" minoccurs="0" /> <xs:element name="size" type="xs:long" minoccurs="0" /> <xs:element name="path" type="xs:string" minoccurs="0" /> <xs:element name="description" type="xs:string" minoccurs="0" /> <xs:element name="write" type="xs:datetime" minoccurs="0" /> <xs:element name="sitename" type="xs:string" minoccurs="0" /> <xs:element name="collapsingstatus" type="xs:long" minoccurs="0" /> <xs:element name="hithighlightedsummary" type="xs:string" minoccurs="0" /> <xs:element name="hithighlightedproperties" type="xs:string" minoccurs="0" /> <xs:element name="contentclass" type="xs:string" minoccurs="0" /> <xs:element name="isdocument" type="xs:long" minoccurs="0" /> <xs:element name="picturethumbnailurl" type="xs:string" minoccurs="0" /> </xs:sequence> </xs:complextype> </xs:element> </xs:choice> </xs:complextype> </xs:element> </xs:schema> <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> <Results xmlns=""> <RelevantResults diffgr:id="relevantresults1" msdata:roworder="0"> <WorkId> </WorkId> <Rank>822</Rank> 15 / 21

16 <Title>New Metro Sport Equipment Bikes</Title> <Author>Ms.Kim Abercrombie</Author> <Size> </Size> <Path>file://PublicShare/BikesConference/postshow/NewModels.ppt</Path> <Description>Metro Sport Equipment Bikes is introducing Bikes for this model year - this slide deck shows the new models and options</description> <Write> T14:46: :00</Write> <SiteName>file://PublicShare/BikesConference</SiteName> <CollapsingStatus>0</CollapsingStatus> <HitHighlightedSummary>Metro Sport Equipment Bikes is introducing Bikes for this model year - this slide deck shows the new models and options</hithighlightedsummary> <HitHighlightedProperties> <HHTitle> Bike Retailers - Always ready to ride </HHTitle> <HHUrl> file://publicshare/bikesconference/postshow/newmodels.ppt </HHUrl> </HitHighlightedProperties> <IsDocument>1</IsDocument> </RelevantResults> <RelevantResults diffgr:id="relevantresults2" msdata:roworder="1"> <WorkId> </WorkId> <Rank>793</Rank> <Title>How to care for BB Ball Bearings</Title> <Author>Mr.GustavoAchong</Author> <Size>50004</Size> <Path> Pages/BB_Ball_Bearings.aspx</Path> <Write> T22:00:46-07:00</Write> <SiteName> <CollapsingStatus>0</CollapsingStatus> <HitHighlightedSummary> BB Ball Bearings are known for being hard to take care of, but actually they aren't too bad if you follow these simple directions. </HitHighlightedSummary> <HitHighlightedProperties> <HHTitle>How to care for BB Ball Bearings</HHTitle> <HHUrl> Pages/BB_Ball_Bearings.aspx</HHUrl> </HitHighlightedProperties> <ContentClass>STS_ListItem_WebPageLibrary</ContentClass> <IsDocument>1</IsDocument> </RelevantResults> <RelevantResults diffgr:id="relevantresults3" msdata:roworder="2"> <WorkId> </WorkId> <Rank>714</Rank> <Title>O14 PPS Build</Title> <Author>Mr. Samuel N. Agcaoili</Author> <Size>253623</Size> <Path> Changes.docx</Path> <Write> T15:03:43-08:00</Write> <SiteName> <CollapsingStatus>0</CollapsingStatus> <HitHighlightedSummary> No Summary available </HitHighlightedSummary> <HitHighlightedProperties> <HHTitle>O14 PPS Build </HHTitle> <HHUrl> 16 / 21

17 Changes.docx</HHUrl> </HitHighlightedProperties> <ContentClass>STS_ListItem_DocumentLibrary</ContentClass> <IsDocument>1</IsDocument> </RelevantResults> </Results> </diffgr:diffgram> </DataSet> 17 / 21

18 4 Security Considerations None. 18 / 21

19 5 Appendix A: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs: Windows SharePoint Services Microsoft Office system Microsoft Office SharePoint Server 2007 Microsoft Office 2010 system Microsoft SharePoint Foundation 2010 Microsoft SharePoint Server 2010 Microsoft Office 2013 system Microsoft SharePoint Foundation 2013 Microsoft SharePoint Server 2013 Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition. Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription. 19 / 21

20 6 Change Tracking No table of changes is available. The document is either new or has had no changes since its last release. 20 / 21

21 7 Index A Applicability 7 C Change tracking 20 D DataInstance element 13 DataInstance element schema 9 DataTable element schema 10 DiffGram namespaces 8 E Element schema DataInstance 9 DataTable 10 Examples overview 15 F Fields vendor-extensible 7 G References 5 informative 6 normative 6 Relationship to other protocols 7 S Security overview 18 SharePoint DiffGram Data element 12 SharePoint DiffGram high-level structure 8 SharePoint DiffGram Schema element 9 Structures high-level 8 overview 8 T Tracking changes 20 U Unique element 12 V Vendor-extensible fields 7 Versioning 7 Glossary 5 H high-level structure 8 I Informative references 6 Introduction 5 L Localization 7 N Namespaces 8 Normative references 6 O Overview 6 P Product behavior 19 R 21 / 21