Report from Metadata Working Group

1
Report from Metadata Working Group

• ILDG7 (Dec.08,2005)
• T.Yoshie for MDWG CCS,Tsukuba

• ILDG6
• QCDml1.1 had been stable
• file format was proposed, and approved
• ILDG7
• propose an update of QCDml
• management, marked up new lattice actions
• summary of on-going discussions
• observables, validity of schemata
• other issues

2
Management of QCDml1.1

• strategy of QCDml1.1
• management section records all events of
  addition/removal of configurations in the
  ensemble/config XML ID

• ltrevisionsgt total number of revisions
• ltrevisiongt sequential number (ltrevisiongt in
  config XML)
• ltrevisionActiongt add/remove of configurations
• ltnumberConfiggt config processed in this
  revision
• ltelemgt includes other info (person, date,)

3
Management requirements

• new requirements we want to
• write an ensemble XML ID when config generation
  starts
• avoid frequent change of ID
• suppose we add configuration one by one. long
  list of archiveHistory
• store ID written by users to MDC without further
  changes
• for QCDml1.1, a tool to generate archiveHistory
  consistently has to be developed, and the user ID
  has to be processed by the tool.
• old properties we dont want to change
• configs belonging to an ensemble can be counted.
• replace/remove of configs can to be detected by
  users
• modification of ID can be detected by users
• a kind of time stamps is recorded
• change of existing IDs has to be minimal

4
Management solution (1)

• ensemble XML
• ltrevisionsgt and all ltelemgts in
  ltarchiveHistorygtare optional

numberConfigs
revision
revisionAction

• when one records optional archiveHistory elems
• ltrevisionActiongt refers to a revision of XML ID
• add addition of ID to MDC, replace replace
  of ID in MDC
• remove remove of ID from MDC
• ltnumberConfsgt is removed, i.e add/remove of
  configs from/to an ensemble is not recorded in
  the ensemble XML ID.

5
Management solution (2)

• configuration XML
• one ltelemgt in archiveHistory (generate) is
  mandatory
• others optional

elem
elem
elem
revision0
revisionAction generate
includes person, date info

• when optional archiveHistory elems are recorded
• ltrevisionActiongt add/replace/remove refer to
  either ID or config.

6
Management solution (3)

• New management section satisfies new
  requirements and keeps old important properties,
  even if optional elements are not marked up.
• write an ensemble XML ID before generation/submit
• avoid frequent change of ID
• coupling between ensemble IDs and config IDs was
  removed
• ID written by a user is not changed when it is
  stored in MCD
• configs belonging to an ensemble can be counted.
• count config IDs with markovChainURI as a key
• replace/remove of configs can to be detected by
  users
• when replaced, crcCheckSum and hence config ID
  will be modified
• modification of ID can be detected by users
• a kind of time stamps is recorded

7
Management more improvement

• ltensembleLabelgt is proposed by MILC collab.

Ensembles generated by a project are usually
classified by e.g. lattice spacing (coarse, file
superfine), lattice size (small, medium, large).
ltensembleLabelgt enables to mark up such
lower-level grouping
8
New action gluon

• Convention to mark up sixLink actions

iwasakiRG

• c3 was missing in QCDml1.1
• we mandate c3, though redundant

DBW2
LuescherWeisz
tpLuescherWeisz
treeLevelSymanzik
9
New action quark
Requests of marking up other actions, write to us
10
QCDml1.2.0

• it seems that modifications are minor
• the new one is not compatible with the previous
  QCDml1.1
• compatible if IDs written based on the old
  schema are still valid under the new one.
• strategy to name and treat new QCDml schema

• if not-compatible, count-up major/minor version
  number
• if compatible, count-up release number. All
  releases (with the same version number) belongs
  to the same name space, e.g. QCDml1.2.x has
  targetNamespace"http//www.lqcd.org/ildg/QCDml/en
  semble1.2"

11
On-going observables

• a request to markup observables e.g. lattice
  spacing
• useful for users to search configurations
• conceptually (qualitatively) different from what
  we have marked up.
• Ensemble ID how the ensemble was generated
• Observables properties (consequences) of the
  ensemble
• Thus, deliberate action is necessary
• summary of discussions up to now
• Some kind of observables are not property of
  ensemble. E.g. Lattice spacing, if it is
  determined by chiral extrapolations.
• Dimension-full quantities are dangerous. They
  depends on inputs.
• Values of observables change, when more
  configurations are added.
• what kind of observables are worth marking up.
  pion prop maynot be.
• candidate pi-rho ratio and sommer scale in
  lattice units
• plan to come to conclusions in a month or so.

12
Validity of Schemata

• current version of QCDml is not valid under W3C
  definition
• strategy to express hierarchical structure of
  lattice actions
• action complexType, derived action
  substitution of complexType
• content model of the new type has to be
  restriction/extension of that of the old one.
  Current QCDml violates this rule
• validation of schema does not work properly with
  XMLspy5
• causes no serious problem for usual use of QCDml
• validation of ID works correctly
• Xpath(1.0) query does not refer to schemata
• working to write a new schema which satisfies
• inheritance of actionTypes is valid (action
  hierarchical tree unchanged)
• elements in IDs are unchanged (users dont have
  to do anything)
• not completed yet, but we think prospects are
  good.

13
other issues and future works

• procedure to release new schemata (almost agreed
  by WG)
• when user wants to mark up a new action,
• write a request to the MDWG
• a MDWG member (or the user) marks up the new
  action and circulates it to the MDWG mail-list
• the proposal of change is automatically accepted
  if there is no objection circulated within a
  certain period of time (e.g. 2 weeks)
• Chris Maynard volunteers final editing of
  schemata
• we put the new release somewhere of the ILDG
  web-page
• and announce new schemata via ILDGNews blog of
  the ILDG web-page or other mail-list
• write glossary for marked-up actions
• write human readable documents (in addition to
  documents embedded in schemata)

14
Summary and Discussions

• New version of QCDml (QCDml1.2) was released
• Dirk Pleiter volunteered to write this version.
• Discussion is on-going on whether/how we extend
  QCDml to include observables.
• feedback of your opinions/comments are welcome
• Work is in progress to write schemata compatible
  with W3C definition
• Chris Maynard is tackling this issue
• Mail list qcdml_at_ccs.tsukuba.ac.jp is closed to
  members only.
• write to yoshie_at_ccs.tsukuba.ac.jp if you want
  your mail address be included, or you send your
  opinions/comments to members.
• mails are archived at http//www.ccs.tsukuba.ac.jp
  /ILDG/QCDML-MA/