Reusing properties within a template

[olufine]

Currently it is not allowed to resuse a property in the same template, unless the different occurrences are connected to nested templates instantiating different classes. This leaves a gap for the need of using the same property both for literal values and for uri/ookups.

Example:
In property templates for the http://rdaregistry.info/Elements/w/P10256 ("has subject") property, we would like to specify that both certain controlled term lists (not LD, so no URIs) as well as certain URI lookups are allowed as value sources.
This would be OK if we could specify 2 occurrences of the property, as literal and uri/lookup, respectively. Is there any problem with allowing that?

[michelleif]

The problem with allowing more than one property template to have the same property is that when Sinopia displays a resource, it doesn't know which field to display each object in, since both fields will have the same property -- more detail here

But as explained in the page linked to above, there are several disadvantages, including the one you just raised (which I should add to the page!) So this is something to look into in our next work cycle.

In fact, Sinopia used to allow a field to accept either a URI or a literal, but this became problematic, details here: #2887