How do you know your monitor even provides this structure?
It's an evolutionary development of EDID. Which means there are new EDID blocks defined, which may or may not be transmitted by your display. And if parse-edid or xrandr --props have not already been updated to decode the blocks, you can always download the standard and parse the raw edid hexdump for yourself.
Edit
Here's what I get from my monitor use sudo get-edid | hexdump -C
00000000 00 ff ff ff ff ff ff 00 10 ac 7a a0 4c 41 39 32 |..........z.LA92|
00000010 33 16 01 03 80 34 20 78 ea ee 95 a3 54 4c 99 26 |3....4 x....TL.&|
00000020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 |.PT....@...@....|
00000030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 |......(<..p.#@0 |
00000040 36 00 06 44 21 00 00 1a 00 00 00 ff 00 30 46 46 |6..D!........0FF|
00000050 58 44 32 43 49 32 39 41 4c 0a 00 00 00 fc 00 44 |XD2CI29AL......D|
00000060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 00 00 00 fd |ELL U2412M. ....|
00000070 00 32 3d 1e 53 11 00 0a 20 20 20 20 20 20 00 2c |.2=.S... .,|
As you can see that's a single 128 byte block, and it matches the EDID 1.3 format as described on Wikipedia.
If your raw EDID is longer, then it will include additional information, possibly data provided by DisplayId. If it's just this single 128 byte block, it won't.
BTW, I just looked at VESA Standards page, and as a non-member it will cost you $350 to obtain the standard. And so it will everyone else who wants to provide a program to parse this information. So if you are that curious to decode your EDID data ...