inkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
> Date: Sun, 6 Jan 2013 16:51:00 +0100
> From: bert.verhees at rosa.nl
> To: openehr-technical at lists.openehr.org
> Subject: csingleattribute and existence
>
> Excus
prohibited - it is only as a constraint that it is binary.
Cheers, Sam
From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org]
On Behalf Of Thomas Beale
Sent: Monday, 7 January 2013 9:57 PM
To: openehr-technical at lists.openehr.org
Subject: Re: csingleattribute and existence
On 01/07/2013 01:27 PM, Thomas Beale wrote:
>
> Bert,
>
> one very useful thing you can do is to identify guidelines for use of
> the current specification. E.g. statements of the form
>
> if existence is set on a single-valued attribute, and there is only
> one child object, no occurrences shoul
Bert,
one very useful thing you can do is to identify guidelines for use of
the current specification. E.g. statements of the form
if existence is set on a single-valued attribute, and there is only one
child object, no occurrences should be set, since they can always be
inferred from the own
>> But besides that, suppose you have a CSingleAttribute with REQUIRED
>> set with more CObjects as alternatives in it.
>> All occurrences for the CObjects need then to be set to 0..1, every
>> other setting is erroneous.
>> Occurrences 0..0 is useless, why define a CObject if it may never occur
On 07/01/2013 09:32, Bert Verhees wrote:
> On 01/07/2013 02:40 AM, Thomas Beale wrote:
>>
>
> I think, Thomas, the logic is as follows, the CSingleAttribute can, as
> in the specs, have one or more then one children (CObjects).
> Only one can be chosen, the others are alternatives.
>
> The CSingle
On 01/07/2013 02:40 AM, Thomas Beale wrote:
> On 06/01/2013 20:29, Bert Verhees wrote:
>> On 01/06/2013 08:44 PM, Thomas Beale wrote:
>>>
>>> Hi Bert,
>>>
>>> existence is a property of CAttribute (multiple or single). It
>>> indicates if the attribute value (i.e. some object) must exists or
>>>
On 06/01/2013 20:29, Bert Verhees wrote:
> On 01/06/2013 08:44 PM, Thomas Beale wrote:
>>
>> Hi Bert,
>>
>> existence is a property of CAttribute (multiple or single). It
>> indicates if the attribute value (i.e. some object) must exists or
>> can be null.
>>
>
> How about this:
>
> Since its fun
On 01/06/2013 08:44 PM, Thomas Beale wrote:
>
> Hi Bert,
>
> existence is a property of CAttribute (multiple or single). It
> indicates if the attribute value (i.e. some object) must exists or can
> be null.
>
How about this:
Since its function in CSingleAttribute is also done by CObject-attrib
On 01/06/2013 08:44 PM, Thomas Beale wrote:
> Occurrences on an object under a CSingleAttribute can only indicate
> 0..0 or 1..1 (based on an original value of 0..1). In theory,
> occurrences on an object under a CSingleAttribute could conflict with
> existence on the CSingleAttribute. Tools can
Hi Bert,
existence is a property of CAttribute (multiple or single). It indicates
if the attribute value (i.e. some object) must exists or can be null.
occurrences is a property of a CObject, and indicates how many instances
of that object constraint can exist in the data.
It can be used on C
Excuse me the following question, maybe I am just looking over the
answer all the time
What is the use of both together existence and occurences in case of a
CSingleAtttribute.
And what if both have conflicting information?
For example, existence gives REQUIRED and occurrences gives minOccurs=
12 matches
Mail list logo
