Why We Write Standards Proposals
Some of the software The JCArtes Foundation builds sits where several industry standards meet. Open PCB & IC Engineer, our 3D design tool for circuit boards and chips, reads and writes 3Dblox, the format that describes how chiplets are stacked into one package. It also uses the JEDEC JEP30 part models for materials, bonding methods and other part data. Standards like these let tools from different makers work on the same design, which is why we build on them instead of inventing formats of our own.
Standards are written by people, and they cannot foresee everything a real design will need. When we find something our software needs that a standard cannot yet carry, we have two choices. We can keep the data in a private format that only our software understands, or we can work with the committee that maintains the standard to fill the gap for everyone. We take the second road. Writing good software sometimes means helping to improve the standards it depends on.
Each proposal on this page describes a gap we found while building our software, the addition we suggest, and a working example from our own files. We send each one to the committee responsible, and we publish it here so that other engineers and tool makers can read it, comment on it and build on it.
Proposals
Comments on any proposal are welcome. Write to Support@JCArtes.Org.
Read more about Open PCB & IC Engineer, and see our other Software and Hardware projects.