Version 1.1.0 introduced a new geometry type "ball" in an ambiguous way:
This new XML element caused strict parsers of the beamlattice extension to reject files with balls, loose parsers simply ignored the ball geometry (#37).
Version 1.2.0 resolves this ambiguity by moving the ball-element into a separate XML-namespace http://schemas.microsoft.com/3dmanufacturing/beamlattice/balls/2020/07. Producers that require ball geometry can explicitly mark the ball-namespace as required. Strict parsers of 3MF with beamlattice extension can now ignore the balls if they are not required.