{ "version": "https://jsonfeed.org/version/1.1", "title": "chem-bla-ics", "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.", "home_page_url": "https://chem-bla-ics.linkedchemistry.info/", "feed_url": "https://chem-bla-ics.linkedchemistry.info/2007/06/25/test-file-repository-and-relaxng.json", "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png", "language": "en", "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286", "_orcid": "0000-0001-7542-0286" } ], "items": [ { "id": "https://doi.org/10.59350/a1np2-c3x03", "url": "https://chem-bla-ics.linkedchemistry.info/2007/06/25/test-file-repository-and-relaxng.html", "title": "Test File Repository and RelaxNG", "content_html": "

Last week I started the Blue Obelisk Chemical Test File Repository,\na repository of OSI-approved-licenced test files (from various sources) to improve interoperability between\nchemoinformatics software.

\n\n

Following a discussion on the mailing list earlier, a directory hierarchy has been set up, and each files contains an index.xml to describe\nthe content. In case of a directory with actual test files, it may look like:

\n\n
<dir name=\"asn/pubchem/valid\" xmlns:dc=\"http://purl.org/dc/elements/1.1/\">\n\n  <chemfiles>\n\n    <file name=\"cid1.asn\" valid=\"yes\">\n       <dc:format>chemical/x-asn-pubchem</dc:format>\n       <dc:source>PubChem</dc:source>\n       <dc:creator>Unknown</dc:creator>\n       <dc:rights>PublicDomain</dc:rights>\n       <test by=\"CDK\"/>\n    </file>\n\n  </chemfiles>\n\n</dir>\n
\n\n

As is clear, Dublin Core is reused for much of the meta data.

\n\n

To improve and ensure some quality, the XML must be valid in addition to just well-formed, so that I can set up XSLT stylesheets to create XHTML indices and\nsummaries. Therefore, I wanted to setup a schema for the index.xml files. My first thought was to use XML Schema\nwhich has XML Namespaces support and has well defined (and extensible) data types. I have hacked in it in the past my the details have slipped me.\nAlready in 1998 I worked with DTDs, around the time that the XML specification was declared a recommendation. Originating from the SGML year,\nit is not XML based, had no knowledge of namespaces, and only a limited amount of data types.

\n\n

Then there is RELAX NG. XML based, uses the same data types are XML Schema and has support for namespaces.\nSince I had to look up the specs for either DTD or XML Schema for the details anyway (e.g. on how to allow the DC namespace in the main namepsace),\nwhy not try something new. Well, I was amazed. RELAX NG has a syntax simplicity like that of DTD, but the functionality from XML Schema. So,\nI hacked up in 30 minutes a XML spec for the test file repository, including a (too short) list of recognized MIME types. Just a combination of some\n<element>, <attribute>, <oneOrMore>, etc elements. The results is available as schema.relaxng\nin SVN.

", "summary": "Last week I started the Blue Obelisk Chemical Test File Repository, a repository of OSI-approved-licenced test files (from various sources) to improve interoperability between chemoinformatics software.", "date_published": "2007-06-25T00:00:00+00:00", "date_modified": "2025-02-15T00:00:00+00:00", "tags": ["blue-obelisk","openscience"], "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ] } ] }