The current approach for modeling URI and lookup defaults was implemented before labels were correctly supported in the Sinopia Editor. As a result, defaults are modeled as a nested resource with separate URI and label properties:
It is proposed to change defaults to be a "plain-old" URI:
Sinopia will continue to load templates with legacy default URIs so the change will transparent for template users. However, when editing the template, the legacy default URIs would be dropped and need to be re-entered by the template author:
On stage, here are the templates that have URI defaults:
Yes, I think this is important enough that we should move ahead. Michelle & I can work with the template owners to both warn them and help them fix the templates in question.
The current approach for modeling URI and lookup defaults was implemented before labels were correctly supported in the Sinopia Editor. As a result, defaults are modeled as a nested resource with separate URI and label properties:
It is proposed to change defaults to be a "plain-old" URI:
Sinopia will continue to load templates with legacy default URIs so the change will transparent for template users. However, when editing the template, the legacy default URIs would be dropped and need to be re-entered by the template author:
On stage, here are the templates that have URI defaults:
Should we proceed with this change?