50 seems to have broken serialization in cases where there are multiple blank node objects being serialized. The behavior makes me think the serializer stores '' as an "identifier" (scare quotes) that it has already handled, and then when it finds a new blank node, it thinks it's already done, so emits just the bare minimum.
In this example, the content of the second identifier just disappears upon serialization:
50 seems to have broken serialization in cases where there are multiple blank node objects being serialized. The behavior makes me think the serializer stores
''
as an "identifier" (scare quotes) that it has already handled, and then when it finds a new blank node, it thinks it's already done, so emits just the bare minimum.In this example, the content of the second identifier just disappears upon serialization: