Share via

6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft SharePoint Foundation 2010

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates 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.

<1> Section 2.2.1.10: For example, by default, SharePoint Foundation 2010 creates three implementation-specific site groups with default site group identifiers for use in role assignments when provisioning a new site collection: "Site Owners" (3), "Site Visitors" (4), and "Site Members" (5).

<2> Section 2.2.2.8: This flag is not used in SharePoint Foundation 2010.

<3> Section 2.2.8.3.3.2: SharePoint Foundation 2010 allows a filtering user interface for fields with the aggregation attribute set to merge, but only in list views where Filter=1 occurs in the view's query parameter.

<4> Section 2.2.8.3.3.2: SharePoint Foundation 2010 does include this attribute with a value of 0.

<5> Section 2.2.8.3.3.2: SharePoint Foundation 2010 sets the value MinusSign for this field.

<6> Section 2.2.8.3.3.3: SharePoint Foundation 2010 emits this data if present in the underlying template definition, even if the field type is not of the specified type.

<7> Section 2.2.8.3.3.3: SharePoint Foundation 2010 emits this data if present in the underlying template definition, even if the field type is not of the specified type.

<8> Section 2.2.8.3.3.3: SharePoint Foundation 2010 emits this data if present in the underlying template definition, even if the field type is not of the specified type.

<9> Section 2.2.8.3.3.3: SharePoint Foundation 2010 emits this data if present in the underlying template definition, even if the field type is not of the specified type.

<10> Section 2.2.8.3.3.3: SharePoint Foundation 2010 emits this data if present in the underlying template definition, even if the field type is not of the specified type.

<11> Section 3.1.5.20.10:  SharePoint Foundation 2010 sets this value to 4 when the SetupPath is relative to the install location of SharePoint Foundation 2010 on the front-end web server (for example, Program Files\Common Files\Microsoft Shared\Web Server Extensions\14).

<12> Section 3.1.5.20.11:  SharePoint Foundation 2010 sets this value to 4 when the SetupPath is relative to the install location of SharePoint Foundation 2010 on the front-end web server (for example, Program Files\Common Files\Microsoft Shared\Web Server Extensions\14).

<13> Section 3.1.5.21.14:  SharePoint Foundation 2010 sets this value to 4 when the SetupPath is relative to the install location of SharePoint Foundation 2010 on the front-end web server (for example, Program Files\Common Files\Microsoft Shared\Web Server Extensions\14).

<14> Section 3.1.5.21.15:  SharePoint Foundation 2010 sets this value to 4 when the SetupPath is relative to the install location of SharePoint Foundation 2010 on the front-end web server (for example, Program Files\Common Files\Microsoft Shared\Web Server Extensions\14).

<15> Section 3.1.5.44: SharePoint Foundation 2010 uses text-based SQL queries to get the version number which are equivalent in functionality to proc_GetVersion.