Property dependency

For your first question, do you have an example of this? With the exception of properties marked as required, everything else is optional to support, so it's entirely dependent on what you're building and supporting for functionality.

For your second question, we don't necessarily have "high priority" schemas. The changes we add to the schemas over time come from user requests for new functionality, and it comes in at a fairly steady pace. Whoever asks the loudest tends to get the higher priority, but it's not really based on an individual schema file. Since we release updates every few months, we have a fairly quick turnaround time for adding new requests.

But in terms of functional areas that have been of interest in recent releases, certainly security-related topics, like with the new ComponentIntegrity model. SmartNIC representation has also been a new topic, which necessitated a white paper on the subject (https://www.dmtf.org/sites/default/files/standards/documents/DSP2063_1.0.0.pdf).

When we deprecate something, it's not because we don't need the functionality any more, but rather we've learned from usage over time that there's a more optimal way of doing something. Whenever we deprecate something, we add pointers in the notice to the preferred method of supporting something.