Laurent Pugin
Laurent Pugin
This would be quite useful. However, it would be good to take the opportunity to have something in MEI to encode it properly. The current implementation relies on something homemade....
To some extend we can extract this automatically from the 690s in works. However, one advantage of having a 505 in Publications is that it would give the order of...
It is a rails thing - I think
Coming back to this, I think we should either remove the requirement on the `@func`, or alternatively adding something like `unspecified` or `unknown`.
I guess that then making optional would be acceptable? Something seems contradictory to me to make it required but then allowing something like `unspecified`. In other words, I would understand...
> One possibility is to have separate attributes dedicated for each data type. I think that would be a good idea. I makes typing and processing much easier. I also...
Sorry, maybe I was not clear. My proposal is simply to split the recommended values for `@type` into a distinct attribute so `@type` would be left exactly as it is...
What you say makes sense when looking at the values in the list essentially as input aid, for example when encoding MEI by hand in Oxygen. I am more interested...
There would be no open-ended value set in `@type`. Sorry if that was not clear.
> If this is to address durational ratios between staves, does it make sense to also have it on scordeDef? The most common use is quite likely to be on...