mlhim-owners team mailing list archive

[Timothy Cook <timothywayne.cook@xxxxxxxxx>]

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




-- 
============================================
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