[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Temporal Type Selection

• From: "Timothy W. Cook" <timothywayne.cook@gmail.com>
• To: Mukul Gandhi <gandhi.mukul@gmail.com>
• Date: Thu, 27 Dec 2012 10:43:24 -0200

Right.  It is valid. This is the reference model that is a generic
structure for healthcare concepts.  Applications are developed on this
model.

The the actual plethora of healthcare concepts are defined in
restriction schemas called Concept Constraint Definitions (CCDs).
These are then easily referenced/exchanged by multiple applications to
establish semantic interoperability between healthcare apps.  The full
semantics of the concept are captured in the CCD.  Since there are
multiple instances of RM complexTypes in any given CCD, I use UUIDs to
name the complexTypes to guarantee uniqueness. This has the bonus
side-effect of creating very short paths for the instance data.

The CCD is where I need to constrain the actual temporal subtypes in a
complexType.
You can find multiple examples at http://www.hkcr.net/CCDs

I hope this is a good enough high-level explanation.

Cheers,
Tim

On Thu, Dec 27, 2012 at 10:33 AM, Mukul Gandhi <gandhi.mukul@gmail.com> wrote:
> Hi Tim,
>     Thanks for the information. I'll surely explore this topic further.
>
> Out of curiosity, I downloaded the schema file mlhim2.xsd from
> http://goo.gl/hQt9K and validated it with Xerces's XSD 1.1 validator. It's
> reported as valid.
>
>
> On Thu, Dec 27, 2012 at 4:58 PM, Tim Cook <tim@mlhim.org> wrote:
>>
>> Hi Mukul,
>>
>> On Thu, Dec 27, 2012 at 8:26 AM, Mukul Gandhi <gandhi.mukul@gmail.com>
>> wrote:
>> > you seem to be specifying a complexType restriction, wanting to reduce
>> > the
>> > items to choose from than available in the base type.
>> >
>> > I can say that, this is a valid XSD compleType restriction attempt.
>> >
>> > The following complexType restriction works fine with Xerces:
>>
>> Thanks for this.  At least my concept is correct. I'll work out the
>> details.
>>
>> >
>> > I'm also curious to see type definitions of your types like,
>> > mlhim2:DvDateType. For e.g, is this type's value space different than of
>> > the
>> > type xs:date?
>>
>> Yes, there are additional semantics (elements) to operate within the
>> system.
>> The entire Reference Model schema for MLHIM is here:
>> http://goo.gl/hQt9K
>>
>> If you are interested in exploring this further we have a community on
>> Google + where I am producing some short tutorials.
>> https://plus.google.com/communities/117032458601124539887
>>
>> Cheers,
>> Tim
>>
>>
>> ============================================
>> Timothy Cook, MSc           +55 21 94711995
>> MLHIM http://www.mlhim.org
>> Like Us on FB: https://www.facebook.com/mlhim2
>> Circle us on G+: http://goo.gl/44EV5
>> Google Scholar: http://goo.gl/MMZ1o
>> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
>
>
>
>
> --
> Regards,
> Mukul Gandhi

• References:
  • Temporal Type Selection
    • From: "Timothy W. Cook" <timothywayne.cook@gmail.com>
  • Re: Temporal Type Selection
    • From: Mukul Gandhi <gandhi.mukul@gmail.com>