The implementation notes used contentAvailability.bufferView where it should have been contentAvailability.bitstream. I think we went back and forth with the naming of bufferView and bitstream while writing this, and "bitstream" and "buffer view" are sometimes used interchangeably. I tried to adjust the wording to reduce the potential for confusion: The contentAvailability.bitstream is the index of a buffer view (and this buffer view is/contains a bitstream).
The main change here is that the word "content" is now differentiated more clearly to be "content" or "contents" when listing the cases. The issue originally only referred to the contentAvailability. But a similar (and similarly confusing) wording was used for the contentMetadata, so this is fixed here as well.
Fixes https://github.com/CesiumGS/3d-tiles/issues/766
The implementation notes used
contentAvailability.bufferView
where it should have beencontentAvailability.bitstream
. I think we went back and forth with the naming ofbufferView
andbitstream
while writing this, and "bitstream" and "buffer view" are sometimes used interchangeably. I tried to adjust the wording to reduce the potential for confusion: ThecontentAvailability.bitstream
is the index of a buffer view (and this buffer view is/contains a bitstream).Fixes https://github.com/CesiumGS/3d-tiles/issues/769
The main change here is that the word "content" is now differentiated more clearly to be "
content
" or "contents
" when listing the cases. The issue originally only referred to thecontentAvailability
. But a similar (and similarly confusing) wording was used for thecontentMetadata
, so this is fixed here as well.