Remember my rant in chat about how the link plugin's data model is full with legacy stuff that makes it very hard to understand and use?
Well, I'm afraid this API will actually have to explicitly document that. Because if it doesn't use the exact same data structure, then it won't work.
Except… I could actually "ignore" link's data model and just use my own, as long as getLinkAttributes() returns the expected data structure ({set: {…}, remove: {}…}). Because the only thing that "actually" needs to be able to deal with parseLinkAttributes()'s return value, is getLinkAttributes(), right?
