|
Post by xiaozhangseu on Aug 16, 2024 6:13:51 GMT
|
|
|
Post by jautor on Aug 20, 2024 16:48:04 GMT
There is an `Oem` object within each element in the `Assemblies` array. Since an Assembly resource can hold multiple assemblies, you'd want to add assembly-specific OEM properties there, not at the root (because that would imply those properties apply to all of the included assemblies).
Jeff
|
|
|
Post by mraineri on Aug 20, 2024 18:05:15 GMT
One thing to keep in mind is to understand why you want to surface those fields. Is there really a use case for an end user to specifically look for fields like "FRU File ID"? Could you limit this exposure to users accessing the data via the BinaryDataUri property?
As Jeff said, you can certainly use the Oem property inside each object in the Assemblies array, but I would add caution about adding information that might confuse users.
|
|
|
Post by xiaozhangseu on Aug 22, 2024 2:53:13 GMT
Got it. Thanks. Sorry for the confusion. I am to add OEM field inside the OEM property, not at the root. Like below:
"@odata.type": "#Assembly.v1_3_0.Assembly", "Assemblies": [ { "Name": "Card1/Assembly0", "Oem": { "Nvidia": { "@odata.type": "#NvidiaAssembly.v1_0_0.NvidiaAssembly", "VendorData": [ "1.0.0" ] } }, "ProductionDate": "2023-02-16T06:21:00Z" },
|
|
|
Post by jautor on Sept 12, 2024 14:00:40 GMT
Correct!
|
|