https://bugzilla.wikimedia.org/show_bug.cgi?id=71291
Daniel Kinzler <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Daniel Kinzler <[email protected]> --- The main problem seems to me that we require "qualified" GUIDs (with the entity ID as a prefix) to be stored in the Statements. That makes it hard to generate a correct GUID in the places where we'd need to do this (like in the deserializer, as a fallback). We use qualified GUIDs to allow us to identify the Entity the Statement belongs to just by looking at the GUID. That makes the API somewhat simpler. For consistency, it's nice to have the fully qualified GUID in the JSON blob, so people can just take the GUID from the blob and use it in an API call. That's why we have Q123$A2DC667C3... as GUIDs. I do not see a good way to fix the current situation in a backwards compatible way, without the serializer and/or deserializer for statements knowing about the "present" entity ID, so GUIDs can be generated (or amended to become "qualified" for output, in case we'd be storing unqualified GUIDs in the future). One thing we could do is using a fake prefix when generating GUIDs for broken/incomplete Statement serializations - e.g. BAD$DEAFBEEFDEADBEEF. That should at least allow us to deserialize and display the statements. They would not be editable using that GUID, though. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
