I promised to stop repeating myself long ago but because people seem to think there’s some kind of concensus here we go again…
Nothing has convinced me that relationship attributes (for part-of) wouldn’t solve most of the problems. @Kid_Devine got 7 likes to this post (quoted partially):
For example if I got 2 works I could make one edit (part-of having movement-attribute set) which perfectly defines multiple things: we know there’s relationship between these 2 works (part), we know that one is a movement and another must be so called master work. 3 things with one edit! With work attributes we need to set work attribute “master work” for one of the works, then add another edit for relationship (part of) and then one more edit for work attribute “movement”. 1 edit vs 3 edits. Also on UI users would need to know where all of these fields are located. Or with webservice I would need to read multiple fields instead of one.
I guess we don’t fully understand each other. I believe I have demonstrated that there’s more work for editors, developers and basically to everyone with work attributes (see some earlier posts). Could someone explain why work attributes would be a better solution? I’m especially interested about real life use-cases.