# Release 1.0.2 - SPEC-268 - Correct missing parentheses in dADL type identifiers.

**URL:** https://discourse.openehr.org/t/release-1-0-2-spec-268-correct-missing-parentheses-in-dadl-type-identifiers/16073
**Category:** Implementers (archive)
**Created:** [5 August 2008 13:32 UTC](https://discourse.openehr.org/t/release-1-0-2-spec-268-correct-missing-parentheses-in-dadl-type-identifiers/16073 "2008-08-05T13:32:20Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)
#### Post date: [5 August 2008 13:32 UTC](https://discourse.openehr.org/t/release-1-0-2-spec-268-correct-missing-parentheses-in-dadl-type-identifiers/16073/1 "2008-08-05T13:32:20Z")

</div>

Implementers of ADL/dADL and related XML software should have a look at  
this CR which has been accepted for the next minor release -  
[http://www.openehr.org/issues/browse/SPEC-268](http://www.openehr.org/issues/browse/SPEC-268)

Make sure you have a look at the 'Raise CR' and 'Analysis' tabs.

The main thing to consider is a time interval over which you would make  
this correction in your tools, and also allow the previous (quite  
common) non-parenthesised form of ADL archteypes to exist. Please post  
any reactions on this list.

I would encourage all implementers to have a look at the rest of the  
release as well, which you can see by clicking on Release 1.0.2 at  
[http://www.openehr.org/issues/secure/BrowseProject.jspa](http://www.openehr.org/issues/secure/BrowseProject.jspa)

thanks

- thomas beale