Dennis Ried

@pe-ro I restored ``. What about ``? Is this another case because it can be used for transcription? I ask because a `` could also work. (see also #622 )

@pe-ro I noticed that `` is not documented in the GL at the moment what I like to change. I'm just thinking about the way. If we get rid of...

@pe-ro Sorry, but once again. What about getting rid of `` for the benefit of a ``? Or where is the current place to keep an information like this: `Dedicated...

> A couple questions arise: > > 1. Can a single `` have multiple entries for `@role`? > > 2. If I enter a `` inside a `` should I...

> Then the removal of has nothing really to do with -- it's simply being removed in favour of only using . Is that right? Yes, `dedicatee` will simply removed...

> I believe @ahankinson is correct. As currently defined, `@role` will only allow a single value. I believe > > ``` > > Used to specify further information about the...

> [...] As currently defined, `@role` will only allow a single value. [...] The pureODD solution for alowing multiple values is ``` ``` The rng-fragment `rng:ref/@name` should be switched to...

> > [...] As currently defined, `@role` will only allow a single value. [...] > > The pureODD solution for alowing multiple values is > > ``` > > >...

The "basic" group is more or less the roles the former semantic container elements have represented. The division was also made to support customizations with a smaller setup, e.g., MEI...

> @musicEnfanthen and I just gave it some more thought: As the list is also published at https://id.loc.gov/vocabulary/relators.html, we would prefer to point there, instead of https://www.loc.gov/marc/relators/relacode.html in general and...