action 81

(sorry for this short notice before the telecon,
 I actually planned to posted that yesterday night,
 but for some reason, I didn't...)

Hi,

an demo implementation is available for you to play with at

  http://liris.cnrs.fr/~pchampin/wsgi/mawg/

It is very limited for the moment, but implements some of my proposals on:

  - API giving access to both simple and structured values
  - some kind of handling of abstraction layers (incomplete)

The page explains the basics.

A good example to play with are "date" and "createDate". "createDate" is
more specific, so its always has one value, whatsoever. "date", on the
other hand, has its default value the same as createDate (TDOR).

If you allow for multiple+structured values, you will see that the file
contains actually two more dates: the date of recording (TDRC) and the
time of encoding (TDEN). Now, if you switch on the "strict" flag, you
will only have the encoding date left (the other are not strictly
speaking properties of the file, but of more abstract resources that the
file encodes -- Manifestation, Expression, Work...).

My idea of slices of conformance is someting like that:
 - slice 1: no flags
 - slice 2: flag 'multiple' is available
 - slice 3: flag 'structured' is available (may be without 'inherited')
 - slice 4: flag 'strict' is available (and complete 'structured')

 regards

  Pierre-Antoine