Reified relationships in RM domain

Hi all, the previous version of the RM spec 
http://open-services.net/bin/view/Main/RmSpecificationV2#RM_Relationship_Properties says this:

RM providers MUST accept relationship properties, as described in OSLC Core Link Guidance. The following relationship properties are defined by this specification: …

Then the spec lists 5 properties, all with minimum cardinality 0 and therefore optional.

An equivalent statement does not appear in the new spec though the concept is discussed in this section

https://rawgit.com/oasis-tcs/oslc-domains/master/rm/requirements-management-spec.html#labels

 

Since all properties listed in the old spec are optional it’s reasonable that they are not explicitly included in the new spec. But why not include at least some examples in the non-normative guidance?

 

There is one word in the v2 spec above that seems confusing to me:
accept. This suggests that there must be a method for the client to specify the value of a property. Do we want the client to be able to specify properties on the relationship? If so, then how would that be done? Of the examples given, only one might
 make sense – the dcterms:title. All the others could be assigned automatically by the server though it’s not clear to me how the server could assign multiple creators if only the currently logged in person is creating the relationship. Anyway, maybe this is
 just a v2 issue but I’d like to clarify if possible.

 

Thanks, Martin