1. ILDG8 2006-05-121 MDWG report Chris Maynard

2. ILDG8 2006-05-122 Status QCDml1.3  Issues outstanding at ILDG7 –Management –Ensemble observables –Valid schema  Further developments –Algorithms –Namespaces  Current issues –Normalisation of actions

3. ILDG8 2006-05-123 Management – ensemble OPTIONAL can update XML ID as ensemble evolves or Metadata remains constant

4. ILDG8 2006-05-124 Management - config Each cfg must have it’s own archive history New cfgs don’t have to change ensemble ID

5. ILDG8 2006-05-125 Observables (Ensemble) Dimensionless numbers only Useful for describing the ensemble {' ampi ', ' amrho ‘, ' mpi_mrho ', ' ar0 ', ' ar1 ‘} Glossary document for definition

6. ILDG8 2006-05-126 Valid Schema  QCDml1.1 not valid against –http://www.w3.org/2001/XMLSchemahttp://www.w3.org/2001/XMLSchema  Inheritance of actions is a complicated mix of and  This mixed model was invalid  QCDml1.3 inheritance greatly simplified  Change to XML IDs is almost trivial –One layer of elements is removed  Can now use validators to check QCDml1.3 XML IDs are valid!

7. ILDG8 2006-05-127 Algorithms  QCDml has limited algorithmic information –By design –To complicated for generic, hierarchical markup  Metadata is recorded in XML IDs –Want to record more algorithmic metadata in XML IDs  How to resolve? –Import namespaces

8. ILDG8 2006-05-128 Namespaces Allow another namespace to be imported here Application processing QCDml can ignore this namespace Can include all metadata into XML IDs Local applications can be alg schema aware, but ignore non-local ones

9. ILDG8 2006-05-129 Alg Namespace example Imported namespace has it’s own schema Imported schema is not in default namespace, so has a prefix All elements belonging to this namespace use this prefix

10. ILDG8 2006-05-1210 Current issue normalisation of actions  Six-link actions –Convention for coefficients –MDWG choose –This is not universal e.g. MILC use c 0 =1  No clean solution as cannot describe a unique scheme where none exist –Technical work-arounds will be a kludge

11. ILDG8 2006-05-1211 Suggested solutions  One action – one normalisation –Markup different normalisations as if different actions XML IDs appear with familiar numbers Difficult to compare  Normalisation element (Either/or) XML IDs appear with familiar numbers Still difficult to compare  Choose one normalisation Best technical solution Require community agreement