Issue Details (XML | Word | Printable)

Key: MBS-1774
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Ian McEwen
Reporter: Aurélien Mino
Votes: 2
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
MusicBrainz Server

Webservice: expose UUID for AR type

Created: 22/Apr/11 09:12 AM   Updated: 11/Feb/13 11:40 AM  Due: 05/Dec/12   Resolved: 11/Feb/13 11:40 AM
Component/s: Web service
Affects Version/s: None
Fix Version/s: 2013-02-11


 Description  « Hide

Since an AR type name can change (e.g. "composer"), we should IMO also expose the UUID for the AR type (e.g. below as attribute 'type-id'):

<relation-list target-type="artist">
<relation type="composer" type-id="UUID">
<artist id="4c006444-ccbf-425e-b3e7-03a98bab5997">
[...]
</artist>
</relation>
</relation-list>



Sort Order: Ascending order - Click to sort in descending order
Paul Taylor added a comment - 22/Apr/11 02:12 PM

I dont know the history of composer changing, but I would think this happens very rarely ?


nikki added a comment - 22/Apr/11 02:36 PM

I didn't think composer had changed at all... I was told I should never change the name of the relationship, for this exact reason.



Oliver Charles added a comment - 17/Feb/12 04:13 PM

Seems trivial, but lets agree on the attribute name as this can always cause arguments


Aurélien Mino added a comment - 21/Feb/12 01:09 AM

Don't ask me, I'm very bad for naming stuff



Nicolás Tamargo added a comment - 17/Oct/12 11:18 AM

Moving to 3mo as per due date


Ian McEwen added a comment - 19/Oct/12 02:53 PM

We use 'id' for UUIDs elsewhere. Since this isn't an ID for the tag it's on, but rather for the type, I think type-id is perfectly fine. I'd suggest removing the '' except we've already specified we don't care about making things harder for people using languages that prefer a dot notation and see '' as an operator, so we should keep it for clarity in terms of separating the "namespace" (type) from the "element" (id) (roughly).

Likewise in the JSON. Just stick a "type-id" alongside wherever we currently put "type".


Ian McEwen added a comment - 28/Jan/13 09:01 PM

We decided that type-id was fine in the dev meeting. This can proceed.