Re: [Animl-develop] Update to JCAMP Converter

[Burkhard S. <bur...@bu...>]

Stuart,

> 1) How does any converter appropriately identify that it did the 
> conversion?  Do we need a "Conversion" Action in the AuditTrail?

as it stands, the most appropriate Action to use would be "created", 
since (by performing the conversion) the converter creates the entries 
in the AnIML document.

> 2) Where should any JCAMP comments be put in the AniML file?

At the moment, we don't have an explicit facility for comments, but 
AnIML supports the standard XML comments format ( <!-- my comment --> ).

> 3) Instrument Vendor specific parameters should go where? (until the 
> vendors add their module)

You'd create and reference an AnIML Technique Extension document. If the 
parameters are known before the measurement (instrument settings, 
instrument info, ...), the data is stored as Parameters within the 
ExperimentStep. If the data was actually measured, it goes into Page 
Parameters.

> 4) If a piece of header information has no obvious place to go in the 
> AnIML file where should it be put?  (or does this suggest a change in 
> the ATID is needed?)

Four possibilities:
- create an Extension
- file a bug report with the appropriate Technique team ;-)
- use an XML comment
- ignore the data

> 5) If a value is required in an AnIML document but is not available in 
> the JCAMP file (or any other source file/datasystem) what should be put 
> there?
>      Default value?  No value (empty element)?

The value cannot be left blank. That's why it's required. If the data is 
not known, you'd have to take an informed guess.

> 6) To go along with 5)...if a required field is defined with enum list 
> what should be chosen if there is no data available?
>      Add an "Unknown" enum value to each such list?

Again, you need to take an informed guess.

Note: Data that is typically difficult to obtain will not be made a 
required entry in the Standard Technique Definitions.

Best regards,
Burkhard