Thanks for raising the issue. I see that the LocaliZoom content type is also missing other properties. Would it make sense to do a proper update of the content type or do you need the corrected content type available quickly?

Yes, I agree. We could add "description": "JSON specific file for LocaliZoom containing information about the reference atlas "target" and "target-resolution" and section image registration information for each section in the series."
I am not sure about the "dataType" and "displayLabel". Maybe Gergely can supply info here.

Just to clarify: Does LocaliZoom create one output format with file extension ".lz" (which may or may not be based on JSON format) or is there an additional one with ".json"?

The logic "application/vnd.localizoom.lz+json" as name combined with ".lz" as file extension does not work for our instances.

It can either be:
"application/vnd.localizoom.lz" (name) + ".lz" (file extension)
or
"application/vnd.localizoom+json" (name) + ".json" (file extension)

If both exist, both will be added of course.

Comparable to e.g.,
application_vnd.quicknii.flat with ".flat" as file extension
vs.
application_vnd.quicknii+json with ".json" as file extension

Historically both exists. As of now, LocaliZoom in the Collab creates .lz files, but from the past we have the same kind of files with .json extension, they may appear in datasets.

Hi @UlrikeS91 Could you create both please ?