← Back to team overview

mlhim-owners team mailing list archive

Re: CCD Files

 

Nice soapbox.  I agree.  :-)
Surprised?

--Tim

On Sun, May 6, 2012 at 2:28 PM, Luciana Tricai Cavalini
<lutricav@xxxxxxxxx> wrote:
> Hi Tim and all,
>
> Although I am not the RM expert in this project, I am 'pro' every
> initiative that makes implementations easier to be achieved. We need to
> focus on demo development to get our point across, because we know that
> MLHIM is not very popular in the health informatics field. We might be
> breaking some hearts here and there with our minimalist, cost-effective
> and open source approach.
>
> If we were able to show a proof of concept soon, that would be a huge
> step forward for bottom-up acceptance of MLHIM. Because I don't believe
> that the academic world will stop doing what they are doing anyway, and
> governments and the industry are already sold out on other (much more
> expensive) solutions. Our only hope to be accepted is inside the world
> of small entrepeneurs that want to accomplish something but they can't
> fight against the big superstructures.
>
> [now stepping down from the soap box]
>
> -- Luciana
>
>
> Em 30/04/2012 18:12, Timothy Cook escreveu:
>> Hi All,
>>
>> While a CCD is an XML Schema that inherits from the reference model
>> and adds restrictions (constraints) in the process.  The metadata
>> about a CCD is really more of an XML instance containing information
>> describing the CCD.
>>
>> In attempting to make the metadata a part of the CCD itself it is
>> quite messy, if it is possible at all.
>>
>> The common way that many applications combine files when they are of
>> different types is to package them into a ZIP file.
>>
>> I am proposing here that we change to a different approach:
>>
>> A CCD will be a ZIP file that contains 2 files.  All three files will
>> have the same filename, derived from the UUID of the CCD.  Each file
>> will have a different extension.
>>
>> Metadata file - .xml
>> Schema file - .xsd
>> Zip file - .ccd
>>
>> For example, a CCD with the UUID of  "2nhje1t7k73e1fe556957ha7aq" will
>> be named 2nhje1t7k73e1fe556957ha7aq.ccd and will contain a metadata
>> file named 2nhje1t7k73e1fe556957ha7aq.xml with the constraints in the
>> file 2nhje1t7k73e1fe556957ha7aq.xsd
>>
>> Seems kind of a simple idea.  However, the downside (in my mind) is
>> that in one way it detaches the metadata from the schema.
>> Applications using MLHIM will need to be able to do this extra
>> processing step.  Though this may actually make implementations
>> simpler.
>>
>> I appreciate any feedback on this.  ESPECIALLY if you see a problem
>> that I have overlooked.
>>
>> Regards,
>> Tim
>>
>>
>>
>>
>
> --
> Esta mensagem foi verificada pelo sistema de antivírus e
>  acredita-se estar livre de perigo.
>



-- 
============================================
Timothy Cook, MSc           +1 713 254 3643
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook


References