daniel added a comment. Summary of some points brought up during a discussion among the Wikidata team, with respect to introducing a MediaInfo entity type:
- MediaInfo should live in a separate extension. The data model and serialization for MediaInfo could be split out into a separate library that doesn't depend on Wikibase or MediaWiki. A separate git repo would however be tricky to manage, especially at the beginning when things are still very unstable. Perhaps it should be a separate component managed in the same git repo. - Q: Do we want to / need to support filenames in for entity IDs, or do we want to manage numeric IDs for internal use? Can we (ab)use the id of the image description page? - Most things that are specific to an entity type are only needed on the repo. These can be managed by factory methods in a subclass of EntityHandler. - Entity-type specific things needed on the client: - serialization/deserialization - messages for localizing edit summaries - JS: for each entity type, we need to be able to defined additional resource loader modules. Such modules would then register themselves with the appropriate factories/registries in frontend JS code. TASK DETAIL https://phabricator.wikimedia.org/T75496 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: Bene, Ricordisamoa, Aklapper, adrianheine, GPHemsley, thiemowmde, JeroenDeDauw, JanZerebecki, aude, Lydia_Pintscher, daniel, hoo, Izno, Wikidata-bugs, Mbch331 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
