# Typos in ODIN specification
**URL:** https://discourse.openehr.org/t/typos-in-odin-specification/3753
**Category:** Specifications
**Created:** [27 March 2023 22:34 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753 "2023-03-27T22:34:46Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@richard.kavanagh](https://discourse.openehr.org/u/richard.kavanagh)
#### Post date: [27 March 2023 22:34 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753/1 "2023-03-27T22:34:46Z")
A few typos for the backlog…
- ‘funded in by the’ should be ‘funded by the’
- ‘identiers’ should be ‘identifiers’
- ‘in the this specification’ should be ‘in this specification’
- ‘informatoin’ should be ‘information’
- ‘optionally following by a version’ should be ‘optionally followed by a version’
- ‘grammaar’ should be ‘grammar’
- ‘comma-separated lists of item,’ should be ‘comma-separated lists of items,’
- ‘seriliased’ should be ‘serialised’
- ‘straighforward’ should be ‘straightforward’
- ‘The ODIN syntax maps relatively easily to XML instance.’ should be ‘The ODIN syntax maps relatively easily to XML instances.’
- 'and does not try take into account visual aesthetics of the XML. ’ should be 'and does not try to take into account the visual aesthetics of the XML. ’
thanks,
Richard
---
### Author:  [@DavidIngram](https://discourse.openehr.org/u/DavidIngram)
#### Post date: [28 March 2023 08:09 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753/2 "2023-03-28T08:09:01Z")
It is great to see your fresh eagle eyes combing the openEHR specifications, Richard. It is a common pattern that the eyes of those who have been heavily immersed in the development and writing, tend to skip past typos like these! I hope all is going well for you in your new roles. I am in regular touch still with Martin Severs and he has been carefully combing my new book’s manuscript! Best wishes, David
---
### Author:  [@richard.kavanagh](https://discourse.openehr.org/u/richard.kavanagh)
#### Post date: [28 March 2023 10:24 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753/3 "2023-03-28T10:24:16Z")
Hi David - absolutely, a fresh pair of eyes often sees what the author doesn’t. After years of reviewing specifications, these things just stand out to me. Plus, I am taking the time to read the specifications in some detail.
It has been a while since I dipped my toe in the openEHR world, but I am making a concerted effort to reacquaint myself.
As ever, the quality of the specification assets is one of the greatest assets of the openEHR product.
---
### Author:  [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)
#### Post date: [28 March 2023 13:37 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753/4 "2023-03-28T13:37:16Z")
Thank you for reporting this.
I made a ticket [[SPECLANG-10] - openEHR JIRA](https://openehr.atlassian.net/browse/SPECLANG-10) and will be fixed in next revision of that specification.
---
### Author:  [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)
#### Post date: [3 April 2023 07:59 UTC](https://discourse.openehr.org/t/typos-in-odin-specification/3753/5 "2023-04-03T07:59:13Z")
Well also, some of the texts are quite old and we (= me 😉 didn’t have a modern in-line dictionary available when editing. Anyway, all these fixes are going in, so thanks for making the effort.