Aracılığıyla paylaş

3.4.1.5 Sensitivity Label Information Part

  • Makale

Content Type

application/xml

Root Namespace

http://schemas.microsoft.com/office/2020/mipLabelMetadata

Source Relationship

http://schemas.microsoft.com/office/2020/02/relationships/classificationlabels

An instance of this part type contains sensitivity label metadata specific to this package.

A package is permitted to contain at most one Sensitivity Label Information part, and that part shall be the target of a relationship in the package-relationship item for the document.  If a file contains both a LabelInfo stream ([MS-OFFCRYPTO] section 2.6.4) and Sensitivity Label Information part in the encrypted package ([MS-OFFCRYPTO] section 2.3.4.4) then only the LabelInfo stream ([MS-OFFCRYPTO] section 2.6.4) is applied.  If a package contains a Sensitivity Label Information part and the file is not encrypted with Information Rights Management (IRM) ([MS-OFFCRYPTO]) then the Sensitivity Label Information part is applied.

[Example: The following package part-relationship item contains a relationship to a Sensitivity Label Information part, which is stored in the ZIP item /docMetadata/LabelInfo.xml:

 <Relationships xmlns="...">
 <Relationship Id="rId4" Type="http://schemas.microsoft.com/office/2020/02/relationships/classificationlabels" Target="docMetadata/LabelInfo.xml"/></Relationships>

end example]

The root element for a part of this content type shall be labelList ([MS-OFFCRYPTO] section 2.6.4.3).

Some workflows, for example advanced collaboration features using documents uploaded to Microsoft SharePoint Online, require that writers make the same change to the document. Different implementations can lead to subtle syntactic differences between the files. Even though the data represented in the parts are identical (and would resolve as such if read with a standard XML reader), the files would nonetheless fail to compare byte-for-byte. To solve this issue, the two writers involved must be written cooperatively to ensure stricter rules are followed to guarantee identical XML generation. These stricter rules are not a requirement of this schema, but rather in the cooperative generation of XML between two endpoints in this situation. The Microsoft Information Protection SDK version 1.7 ([MSFT-MIPSDK] see class PolicyEngine) implements these stricter writing requirements in order to implement the cooperative XML writing necessary to avoid false conflicts when SharePoint Online and a client implementation both need to make the same edit to the part in a file in parallel.