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.

  • Windows Server 2003 operating system

  • Windows Server 2008 operating system

  • Windows Server 2008 R2 operating system

  • Windows SharePoint Services 3.0

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.7:  By default, Windows SharePoint Services 3.0 creates five implementation-specific Role Definitions with associated default Role Identifiers.

Role identifier value

Role definition

1073741825

Guest

1073741826

Reader

1073741827

Contributor

1073741828

Web Designer

1073741829

Administrator

<2> Section 2.2.1.10:  By default, Windows SharePoint Services 3.0 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).

<3> Section 2.2.2.8:  This flag is not used in Windows SharePoint Services 3.0.

<4> Section 2.2.8.3.3.2:  Windows SharePoint Services 3.0 allows a filtering user interface for fields with the aggregation attribute set to merge, but only in list views where Filter is equal to 1 occurs in the view's query parameter.

<5> Section 2.2.8.3.3.2:  Windows SharePoint Services 3.0 can include this attribute with a value of 0.

<6> Section 2.2.8.3.3.2:  Windows SharePoint Services 3.0 sets the value MinusSign for some fields.

<7> Section 2.2.8.3.3.3:  Windows SharePoint Services 3.0 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:  Windows SharePoint Services 3.0 sends 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:  Windows SharePoint Services 3.0 sends 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:  Windows SharePoint Services 3.0 sends this data if present in the underlying template definition, even if the field type is not of the specified type.

<11> Section 2.2.8.3.3.3:  Windows SharePoint Services 3.0 sends this data if present in the underlying template definition, even if the field type is not of the specified type.

<12> Section 3.1.5.39:  SharePoint Products and Technologies uses text based SQL queries to get the version number which are equivalent in functionality to proc_GetVersion.