Justin Chu

I suspect they are stored in the metadata_props field. You may check `model.metadata_props` for them.

Could be that the branch rules for rel-* branches were not modified to remove the azure devop checks. @prasanthpul has the access to adjust the branch protection rules.

@cjvolzka you may also want to bring in https://github.com/onnx/onnx/pull/6075

@onnx/sig-operators

Absolutely. Contributions are welcome and appreciated

Following the discussion, I think it's reasonable to correct the spec. Out of curiosity, was there any reason you would expect the behavior to be different than the current one...

Very intriguing question. Do you have any suggestions or thoughts on how this can be done?

```yaml errors: - code: empty-graph-name explanation: The 'name' field of a GraphProto must not be empty. - code: duplicate-input-output-names explanation: Input and output names within a GraphProto must be unique....

```yaml errors: - code: empty-value-info-name explanation: The 'name' field of a ValueInfoProto must not be empty. - code: invalid-tensor-type explanation: The 'type' field of a TensorTypeProto in a ValueInfoProto must...

Based on the provided code, here are the possible errors that could occur during the model checking process: 1. **No Opset registered for domain**: This error occurs if there is...