STEP XML would be probably the closest here.
To be realistic, I might wrap a CLI to AdaShape first, then the user could query the model and have their LLM backport the model tree to something like CadQuery :D
STEP XML would be probably the closest here.
To be realistic, I might wrap a CLI to AdaShape first, then the user could query the model and have their LLM backport the model tree to something like CadQuery :D
And specifically ”whatever xml”, not, say STEP, or , openscad code, python code (via using cadquery) or anything like that?
Do you know your final output format?
Then, I would import that into my project, parse the geometry and instructions for processing it so as to create a 3D model, then I would work through the toolpaths necessary to cut the part thus described using G-code. Or, at least, that's what I would like to try to do. I'll have to give it a whirl w/ BlockSCAD if nothing else.
While https://xkcd.com/927/ is something to be avoided there really isn’t an existing format I would be aware off that fits the bill.
I’ll add this to the roadmap.
But to do this right it really needs to be a properly specified schema, with conformance test suite and versioning.
I appreciate your use case, but for users coming out of context, parsing underspecified XML files would be more of a curse than blessing :)