# proposed small change to C\_QUANTITY

**URL:** <https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643>\
**Category:** Implementers (archive)\
**Created:** [20 December 2006 15:14 UTC](https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643 "2006-12-20T15:14:52Z")\
**Posts on this page:** 3\
**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:** [20 December 2006 15:14 UTC](https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643/1 "2006-12-20T15:14:52Z")

</div>

As part of the finalisation of fixes to the Archetype Editor, ADL and  
ADL parsers, Sam has proposed to add a precision attribute to  
C\_QUANTITY. This would be of type Interval\<Integer\>, although in the  
archetypes he is currently doing, only a single value is needed. The  
typical example is to allow/disallow decimals, such as for blood  
pressure values (where they are never used), so the precision would be 0.

I will add this to the Eiffel parser so that he can put it in the Ocean  
tool; I will also update the C\_QUANTITY definition to include it, so  
that Rong can change the Java parser, which should be easier, and  
Mattias can change the Archetype Editor. Lastly we will put in a CR for  
it, so it is indicated properly in the specs. All in the right order,  
just backwards 😉

Once this change is done, we intend to put up a "clean" set of  
archetypes onto the knowledge SVN repo, which should address the many  
issues Mattias and others have found over the last few months. When we  
have all done a bit of further checking and testing on this, we will tag  
the release in SVN so it becomes a reference baseline.

- thomas

---

<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:** [20 December 2006 15:25 UTC](https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643/2 "2006-12-20T15:25:14Z")

</div>

Thomas Beale wrote:

> As part of the finalisation of fixes to the Archetype Editor, ADL and  
> ADL parsers, Sam has proposed to add a precision attribute to  
> C\_QUANTITY. This would be of type Interval\<Integer\>, although in the  
> archetypes he is currently doing, only a single value is needed. The  
> typical example is to allow/disallow decimals, such as for blood  
> pressure values (where they are never used), so the precision would be 0.  
> &nbsp;&nbsp;

of course, I meant to say C\_QUANTITY\_ITEM - that is where the precision  
has to go...

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [24 December 2006 12:58 UTC](https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643/3 "2006-12-24T12:58:59Z")

</div>

> Thomas Beale wrote:
> 
> > As part of the finalisation of fixes to the Archetype Editor, ADL and  
> > ADL parsers, Sam has proposed to add a precision attribute to  
> > C\_QUANTITY. This would be of type Interval, although in the  
> > archetypes he is currently doing, only a single value is needed. The  
> > typical example is to allow/disallow decimals, such as for blood  
> > pressure values (where they are never used), so the precision would be 0.
> 
> of course, I meant to say C\_QUANTITY\_ITEM - that is where the precision  
> has to go…

> > I will add this to the Eiffel parser so that he can put it in the Ocean  
> > tool; I will also update the C\_QUANTITY definition to include it, so  
> > that Rong can change the Java parser, which should be easier, and

Will do (right now in the middle of fixing invariants support in the parser)

> > Mattias can change the Archetype Editor. Lastly we will put in a CR for  
> > it, so it is indicated properly in the specs. All in the right order,  
> > just backwards 😉
> > 
> > Once this change is done, we intend to put up a “clean” set of  
> > archetypes onto the knowledge SVN repo, which should address the many  
> > issues Mattias and others have found over the last few months. When we  
> > have all done a bit of further checking and testing on this, we will tag  
> > the release in SVN so it becomes a reference baseline.

That will be very nice to have indeed. Maybe we can collect a small set of archetypes created solely for testing parser purpose. I have some of them in the adl-parser package and will be happy to sync them with yous.

Cheers,  
Rong