Transform metadata to fix

[kevinyamauchi]

Some aspects of the current transform metadata is not compliant with the RFC-5 transformations:

• Multiscales - remove "axes" from top level

  ngff-transformations/examples/.zattrs

  Lines 3 to 17 in b78121e

  	{
  	"axes": [
  	{
  	"name": "c",
  	"type": "channel"
  	},
  	{
  	"name": "y",
  	"type": "space"
  	},
  	{
  	"name": "x",
  	"type": "space"
  	}
  	],

• input/output coordinate systems should not be inside transformation:

  ngff-transformations/examples/.zattrs

  Lines 40 to 75 in b78121e

  	"input": {
  	"axes": [
  	{
  	"name": "c",
  	"type": "channel"
  	},
  	{
  	"name": "y",
  	"type": "space",
  	"unit": "unit"
  	},
  	{
  	"name": "x",
  	"type": "space",
  	"unit": "unit"
  	}
  	],
  	"name": "cyx"
  	},
  	"output": {
  	"axes": [
  	{
  	"name": "c",
  	"type": "channel"
  	},
  	{
  	"name": "x",
  	"type": "space",
  	"unit": "unit"
  	},
  	{
  	"name": "y",
  	"type": "space",
  	"unit": "unit"
  	}
  	],

• intrinsic coordinate system should have path:

  ngff-transformations/examples/.zattrs

  Line 98 in b78121e

  "name": "cyx"

• [ ]

[jo-mueller]

Hi @kevinyamauchi , is this repository stalled? Or are you keeping working here? I saw that it's younger than the transformations code over at spatialdata and was thinking of "using" it towards a working implementation of RFC-5. Wanted to ask first what's the plan rn for this repo/this code. Thanks!

[jo-mueller]

Also, another compliance error: The Sequence transformation should have the "input/output" fields only once, not for all elements of itself.

[kevinyamauchi]

Hey @jo-mueller ! Yes, this repo is inactive. If I believe the code in the spatialdata repo should be more up to date, but you can ask @LucaMarconato for confirmation.

[jo-mueller]

Hi @kevinyamauchi , thanks for the info. Will continue the discussion there (see scverse/spatialdata#976) for further ideas about the transforms 👍