RTC/RRC - Change default options for linking WI

It is very likely that RTC is just using OSLC to invoke a dialog provided by RRC to create a requirement, in which case the semantics of this operation are all defined by RRC.

Could you provide some details about the OSLC spec which defines this dialogue? I would have imagined that RTC makes an OSLC call for the Artifact Type model from RRC and is using this information to populate the dialogue independently, but is not using the rm:defaultFormat property to fill in the default format field correctly. However, if this is controlled by RRC then I'd be interested to see that.

Here is a pointer to the "delegated UI" approach, where the client effectively just says "I need a resource of a given type", and the requirements provider (such as RRC) does all the rest:
http://open-services.net/bin/view/Main/RmSpecificationV2?sortcol=table;up=#Delegated_UIs
So in particular, the requirements consumer (such as RTC) wouldn't have to know about details like whether RRC stores its requirements in folders, and whether a requirement has an Actor property or how it gets initialized.
Where is the "rm:defaultFormat" property defined?

 The "rm:defaultFormat" property isn't defined through an OSLC spec - my fault. It is part of the resource model for Artifact Types within the RRC type system. If this is handled by a delegated UI then this would need to be handled by RRC web development. Probably best to create a defect for development investigation.

Thank you Michael and Geoffrey for detailed discussion. It looks as the behavior which I described is working from RRC, however it does not work when users attempts to use RTC to create requirement.