SnakSerializer should have support for derived values. The extra DataValues would be placed next to the "datavalue". E.g. an extra value in the "normalized" slot would show up as "datavalue-normalized" in the serialization, like so:
"mainsnak":{"snaktype":"value","property":"P646","datatype":"string",
"datavalue":{"value":"/m/0g5n7","type":"string"},
"datavalue-normalized":{"value":"https://www.freebase.com/m/0g5n7","type":"string"},
}| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Invalid | None | T93747 [Story] Create infrastructure for optionally putting normalized values into JSON | ||
| Invalid | None | T102835 [Task] Implement service for placing derived values in PropertyValueSnak objects in the data model before serialization | ||
| Invalid | None | T102833 [Task] Implement serializer and unserializer for derived values in a PropertyValueSnak | ||
| Resolved | Addshore | T102791 Implement ExtendedPropertyValueSnak | ||
| Invalid | None | T102789 [Task] Unserializers should optionally allow derived data objects | ||
| Invalid | None | T102788 [Task] Serializers should optionally fail when encountering derived data | ||
| · · · |
Pull request on github: https://github.com/wmde/WikibaseDataModelSerialization/pull/162