Default values for attributes in clrSchemeMapping do not exist

Regina Henschel 151

Look at 2.1.395 Part 1 Section 17.15.1.20, clrSchemeMapping (Theme Color Mappings) in [MS-OI29500]. It has a remark, that default values "t1" and "t2" do not exist. I think, that there should be similar remarks for the default values of attributes bg1, bg2, hyperlink and followedHyperlink because the elements "light1", "light2", "hyperlink" and "followedHyperlink" neither exist in <clrScheme> element.

Default for bg1 is "lt1", default for bg2 is "lt2", default for hyperlink is "hlink", and default for followedHyperlink is "folHlink".

And of cause the standard itself needs to be fixed.

KristianSmith-MSFT 31 Reputation points Microsoft Employee

2023-03-28T22:55:17.57+00:00

Hi Regina,

Thank you for your request. One of our team members will review this and follow-up with you soon.

Regards,

Kristian S
Support Escalation Engineer
Microsoft Open Specifications
Mike Bowen 1,276 Reputation points Microsoft Employee

2023-03-28T23:40:17.83+00:00

Hi @Regina Henschel ,

Thanks for bringing this to our attention. I will investigate this to confirm what you've found and let you know the results.

Best Regards,

Michael Bowen

Escalation Engineer - Microsoft Open Specifications
Mike Bowen 1,276 Reputation points Microsoft Employee

2023-04-03T18:59:51.12+00:00
Hi @Regina Hanschel,

While investigating this, I see that ISO-29500 17.15.1.20 clrSchemeMapping (Theme Color Mappings) is for WordpocessingML and the attributes' possible values are defined in 17.18.103 ST_WmlColorSchemeIndex (Theme Color Reference). In the enumeration for ST_WmlColorSchemeIndex (pasted below), as stated in MS-OI29500, there are no values for t1 or t2, but there are values for light1, light2, hyperlink, and followedHyperlink.

<xsd:simpleType name="ST_WmlColorSchemeIndex"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="dark1"/> <xsd:enumeration value="light1"/> <xsd:enumeration value="dark2"/> <xsd:enumeration value="light2"/> <xsd:enumeration value="accent1"/> <xsd:enumeration value="accent2"/> <xsd:enumeration value="accent3"/> <xsd:enumeration value="accent4"/> <xsd:enumeration value="accent5"/> <xsd:enumeration value="accent6"/> <xsd:enumeration value="hyperlink"/> <xsd:enumeration value="followedHyperlink"/> </xsd:restriction> </xsd:simpleType>

The element you refer to in your question, clrScheme is from DrawingML and is defined in ISO-29500 20.1.6.2 clrScheme (Color Scheme), which doesn't have definitions for light1, light2, hyperlink or followedHyperlink.

Is it possible you're looking at the wrong enumeration? If you still believe the definitions are missing from the enumeration, could you please specify which enumeration you are referring to. Mike Bowen Microsoft - Office Open Specifications
Regina Henschel 151 Reputation points

2023-04-05T21:22:40.61+00:00

Either way it is inconsistent:

(A) You are right, that 17.15.1.20 clrSchemeMapping uses enumerations from 17.18.103 ST_WmlColorSchemeIndex. But then texts "Word uses the tx1 theme color" and "Word uses the tx2 theme color" in [MS-OI29500] couldn't be right, because "tx1" and "tx2" do not exist in ST_WmlColorSchemeIndex.

(B) The texts "Word uses the tx1 theme color" and "Word uses the tx2 theme color" in [MS-OI29500] refer to enumerations in 20.1.10.54 ST_SchemeColorVal which has "tx1" and "tx2". But then the background and hyperlink values should be "bg1", "bg2"...

On second thought, I think the best solution to resolve the inconsistency is to use the values "dark1" and "dark2" that actually occur in ST_WmlColorSchemeIndex instead of "tx1" and "tx2" in [MS-OI29500].
Mike Bowen 1,276 Reputation points Microsoft Employee

2023-04-06T23:15:02.49+00:00

You're right, tx1 and tx2 are not in the enumeration, so that could be a problem. I think you're likely right about using "dark1" and "dark2", but I will need to investigate further to confirm.

Accepted answer

Mike Bowen 1,276 Reputation points Microsoft Employee

2023-04-14T17:36:24.38+00:00

Hi @Regina Hanschel, I have investigated this, and you are correct, t1 and t2 are replaced with dark1 and dark2 respectively. The error will be corrected in an upcoming release of MS-OI29500. Thanks for finding this, please keep bringing us the issues you find! Best Regards, Michael Bowen Escalation Engineer - Microsoft Open Specifications
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Default values for attributes in clrSchemeMapping do not exist

0 additional answers