CircuitData Material Database V1 released
We are pleased to announce that we have released version 1 of the Material Database that will be compatible with the CircuitData standard. The project and it's documentation is stored under the github repository for CircuitData.org . You can find the project here:
At the moment we retrieve data from one source, COMMODITY.LIVE, but the project are open to accept any number of sources. The CircuitData board will be the approval instance for any new sources, addition to code and change requests.
This could be a very useful database. Thanks...
I do have some comments on the current implementation:
1) The circuitdata_version property is defined as a string. It should be a number, in order to better facilitate version control in a reader implementation.
2) The ipc_slash_sheet property is specified as an array of integers. How would one know if these slash sheets refer to IPC-4101 or to some other IPC standard (such as 4103)?
3) The material_attributes property is an array of attribute objects, where each attribute object consists of a name and an array of values, and each value object consists of a value (string) and a value_type (string). So far so good.
As far as I can see, the value_type is nearly always null, and therefore basically useless. It might make better sense to make the value_type a property of the attribute object, and then make the material_attribute_values property an array of values (of the type specified by value_type). It should not be permitted to set the value_type to null.
4) The ipc_slash_sheet property is specified as an array of integers. Sometimes this returns a single integer in the value object. However, in many cases what I get back is a JSON string which looks something like this:
"[\"21\", \"98\", \"99\", \"101\"]"
which without the escaped characters and string delimiting quotes would be:
["21", "98", "99", "101"]
Since this is passed as a JSON string it does not parse into an array of integers. As I understand the structure, this format is incorrect and not consistent with the documentation or with JSON conventions.Reply