I work on an Interoperability Profile and found that it is impossible to specify more than one level nested PropertyRequirements statements because the Profile Schema does not allow that. Could you tell me, is there a way to improve the standard profile schema to allow more than one level nesting of the PropertyRequirements constructions?
The schema should support nesting two object levels deep from the root of a resource:
<Resource> <Object> <Object> <Property>
Can you show us those cases where you need to specify requirements beyond that level? We were hoping to avoid the need to nest more than two objects deep. And we may be able to offer some alternatives to accomplish the same goal in the profile.