vamdc / processors Goto Github PK

Make one reusable app that can be used to provide any kind of xslt-transformation.

Maybe even make the name of the xsl be decided by the URL, so that one app can handle multiple styles, eg. /tools/xsams2sme.xsl?URL=...

Email from Tanya Ryabchikova, June 24, 2012:

In XSAMS VALD gives Lande-factors for the lower and the upper transition levels. In SME file we put effective Lande-factor which is a combination of the lower and upper Lande-factors and J-values:

g_eff=0.5(g_l + g_u)+0.25(g_l - g_u)(J_l(J_l+1) - J_u(J_u+1))

We calculate g_eff in PRESELECT stage and add it to VALD short output format which is eqiuvalent to SME format. It means that you have to calculate it, too , creating SME-output. It should be placed after Van der Waals constant, which is absent, too. The whole sequence is:

'Elem',Wavelength,Excit(eV),Vmic(0.0),log(gf),Rad,Stark,VdW,g_eff,Depth(0.0)'Comment'

Use the registry to allow only urls from vamdc nodes to be fetched.

The applyXSL service lacks the /info endpoint which must be there according to the standard.

Maybe put an info-string into the dictionary that holds the xsl-names and mime-types, then let /info display that string.

Services are synchronous by can be used asynchronically by accessing them with a HTTP HEAD request that skips the body reply but returns a header keyword with a URL that holds a static cache of the output.

This allows scripts to chain several consumer services together.

See Guy's email and our discussion, alternatively draft document.