For interoperability would it be useful/possible to assemble a language-agnostic collection of specs, and their expected stringified output given a test MARC record? The purpose would be to make sure that the MARCspec was parsed and interpreted correctly.
I was thinking of something in Markdown or JSON like:
{
"245$a": "Finnegan's Wake /",
"245$a$c": "Finnegan's Wake / James Joyce.",
...
}If I were to put something together would this be of interest? I guess an initial set could be derived fairly easily from TestMarcSpecTest?
For interoperability would it be useful/possible to assemble a language-agnostic collection of specs, and their expected stringified output given a test MARC record? The purpose would be to make sure that the MARCspec was parsed and interpreted correctly.
I was thinking of something in Markdown or JSON like:
{ "245$a": "Finnegan's Wake /", "245$a$c": "Finnegan's Wake / James Joyce.", ... }If I were to put something together would this be of interest? I guess an initial set could be derived fairly easily from TestMarcSpecTest?