Instead of having a monolithic RdfBuilder with lots of modes and options, we should have separate builders for the different aspects of an entity: terms, sitelinks, statements (reified or simple), etc. The indirection should not be much of a problem, since each of the sub-builder would only be called once per entity.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T88728 Improve Wikimedia dumping infrastructure | |||
Open | None | T88991 improve Wikidata dumps [tracking] | |||
Open | None | T46581 Partial dumps | |||
Resolved | Smalyshev | T46580 Script for creating RDF dumps of all entities | |||
Duplicate | None | T211495 Dump(s) of Wikidata classes | |||
Duplicate | None | T211497 Dump(s) of Wikidata instances of Q5 | |||
Open | None | T162351 Create a "page prop" RDF dump for Wikidata entities ("pagePropertiesRdf") | |||
Open | None | T98320 [Task] Create dump of entity redirects (JSON or n-triples) | |||
Open | None | T285307 Create randomly split partial entity dumps | |||
Open | None | T44063 [Epic] Provide a plain linked data interface for accessing entities | |||
Resolved | hoo | T101837 [Story] switch default rdf format to full (include statements) | |||
Open | None | T50143 Implement complete RDF mapping for entities (tracking) | |||
Open | None | T94175 [Task] Split RdfBuilder | |||
Resolved | daniel | T92515 Implement each "flavor" of RDF in a separate class. | |||
Duplicate | None | T92517 [Task] Implement separate RDF generators for each value type |