Juri Leino

Regarding converting instances in different formats to XML and back there is recent activity https://www.w3.org/community/ixml/

@DrRataplan Yes there is something going on with predicates not being evaluated. [another playground link](https://xpath.playground.fontoxml.com/?mode=1&variables=%7B%7D&xml=%3Croot%3E%0A%3Cfx-instance+id%3D%22countries%22+as-json%3D%22true%22%3E%0A%5B%0A++%7B%22code%22%3A+%22en%22%2C+%22name%22%3A+%22England%22%7D%2C+%0A++%7B%22code%22%3A+%22de%22%2C+%22name%22%3A+%22Germany%22%7D%2C+%0A++%7B%22code%22%3A+%22au%22%2C+%22name%22%3A+%22Australia%22%7D%0A%5D%0A%3C%2Ffx-instance%3E%0A%3Cfx-instance+id%3D%22continents%22+as-json%3D%22true%22%3E%0A%5B%0A++%7B+%22name%22%3A+%22Australia%22%2C+%22countries%22%3A+%5B%22au%22%5D%7D%2C%0A++%7B+%22name%22%3A+%22Europe%22%2C+%22countries%22%3A+%5B%22en%22%2C+%22de%22%5D%7D%0A%5D%0A%3C%2Ffx-instance%3E%0A%3C%2Froot%3E%0A&xpath=declare+namespace+xforms%3D%22i-do-not-remember-the-uri%22%3B%0A%0Adeclare+variable+%24root+%3A%3D+%2F%3B%0A%0Adeclare+function+xforms%3Ainstance%28%24id%29+%7B%0A%09%24root%2F%2Ffx-instance%5B%40id%3D%24id%5D%0A++++%3D%3E+parse-json%28%29%0A%7D%3B%0A%0Adeclare+function+local%3Afilter+%28%24country%29+%7B%0A++%24country%0A%7D%3B%0A%0Adeclare+variable+%24selected-continent+%3A%3D+%22Europe%22%3B%0Adeclare+variable+%24continents+%3A%3D+xforms%3Ainstance%28%22continents%22%29%3B%0Adeclare+variable+%24countries+%3A%3D+xforms%3Ainstance%28%22countries%22%29%3B%0A%0Adeclare+function+local%3Acodes-by-continent%28%24continent%29+%7B%0A%09array%3Afilter%28%24continents%2C+function+%28%24c%29+%7B%0A++++%09%24c%3Fname%3D%24continent%0A++++%7D%29%3F1%3Fcountries%3F*%0A%7D%3B%0A%0A%0Aarray%3Afilter%28%24countries%2C+function+%28%24country%29+%7B%0A++%24country%3Fcode+%3D+local%3Acodes-by-continent%28%24selected-continent%29%0A%7D%29%2C%0A%27----%27%2C%0A%24countries%3F*%5B%3Fcode%3D%28%24continents%3F*%5B%3Fname%3D%24selected-continent%5D%29%3F*%5D%0A%0A%0A&context=) But that then also creates additional problems, if the sequence with predicate is a value...

@cwittern this is the number one item on our backlog (see https://github.com/orgs/eeditiones/projects/2). When time allows this is the first thing to work on.

There is however a possibility to preprocess an API definition with refs see https://faq.teipublisher.com/api/designingopenapi/

The steps in short are - `npm install -g swagger-cli` - `swagger-cli bundle --dereference -o api-with-inlined-references.json api-with-references.json `

There is a new module out that can not only validate your API definition but also `resolve` references. It's called [oad](https://github.com/eeditiones/oad)

@daliboris Hah! Funny, @DrRataplan just reported this error and we fixed it in the most recent release v1.8.3 :tada:

@daliboris please re-test with this version and confirm that this fixes it for you.

Public repo does support adding them as XML into repo.xml. - Add `changelog`-element to repo.xml - for each released version there should be one `change`-element with a `version`-attribute - each...

I just checked the current implementation of the public package repository. It can only read changelogs in repo.xml