The current specification mentions that the attribute "format" of the element content in the manifest file is mandatory. Its values have to be an identifiers.org
URI or an Internet Media Type. However, we also want to use the archive to store any type of relevant content, for instance open formats that are not part of COMBINE such as PharmML, but also widely used proprietary format such as MatLab or NMTRAN. So we are a bit in a pickle.
Possible solutions forward:
1a) We ban files that do not have an identifiers.org
or Media Type URI
1b) We files that do not have an identifiers.org
or Media Type URI are not listed in the manifest
1a and 1b are very close actually. I think 1b is pragmatic while 1a does not bring anything
2a) We accept the value unknown for the attribute format
2b) We accept other URIs as values for the attribute format and we develop quickly the MAMO branch that was discussed in HARMONY 2014
3) We make the attribute format optional
I believe 1) is compatible with the current version of the specification, and IMHO we should use 1b.
As for the future, there is not much difference between 2a and 3, except that 2a does not require a change of schema. 2b is nice but doomed to be incomplete.
I wonder if this is not a case of OMEX being the basis of the COMBINE archive, the latter being more restrictive.
What do you think?
Nicolas LE NOVERE, Babraham Institute, Babraham Campus Cambridge, CB22 3AT
, ORCID: 0000-0002-6309-7327