A reader asked if I could put together a single page of links for the Great JT Debate.
1. Dassault Systeme's Spatial division shocks with its announcement that InterOp R21 will not work with JT files from arch-rival Siemens PLM Systems. (First announced by me in a Twitter post.)
2. Spatial explains why no JT in InterOp Release 21.
3. A reader of this blog wonders why Spatial can reverse-engineer Inventor files, but not JT. In the battle over automakers, perhaps Dassault is no longer keen on giving Siemens a helping hand. "It doesn’t help that JT-based growth is always linked to TeamCenter growth, which is the bigger problem for Dassault in the long run."
4. Debankan Chattopadhyay of CADCAM-E reports that his company is able to write JT translators, but only with difficulty: "It is fair to say, however, that the effort to support the latest versions of JT format is neither straightforward nor easy as we expect it to be for a standard often mentioned as ‘open’."
5. upFront.eZine writes about Spatial ACIS and InterOp Release 21.
6. Siemens PLM responds to Spatial's complaint on JT .
7. A reader notes that Siemens publishes the JT file format as poorly as Dassault does of 3DXML.
8. JT import/export not a problem: Okino does it using the official JT Open Toolkit from Siemens.
- - -
It appears to me that Siemens is following the same route as Adobe: get an international body to certify PDF as a standard so that Adobe can call it "open."
This is only half-open; the other half of openness is missing in that only Siemens and Adobe decide what gets to be in their file formats.
JT and PDF are half-proprietary, half-open.
1. Dassault Systeme's Spatial division shocks with its announcement that InterOp R21 will not work with JT files from arch-rival Siemens PLM Systems. (First announced by me in a Twitter post.)
2. Spatial explains why no JT in InterOp Release 21.
3. A reader of this blog wonders why Spatial can reverse-engineer Inventor files, but not JT. In the battle over automakers, perhaps Dassault is no longer keen on giving Siemens a helping hand. "It doesn’t help that JT-based growth is always linked to TeamCenter growth, which is the bigger problem for Dassault in the long run."
4. Debankan Chattopadhyay of CADCAM-E reports that his company is able to write JT translators, but only with difficulty: "It is fair to say, however, that the effort to support the latest versions of JT format is neither straightforward nor easy as we expect it to be for a standard often mentioned as ‘open’."
5. upFront.eZine writes about Spatial ACIS and InterOp Release 21.
6. Siemens PLM responds to Spatial's complaint on JT .
7. A reader notes that Siemens publishes the JT file format as poorly as Dassault does of 3DXML.
8. JT import/export not a problem: Okino does it using the official JT Open Toolkit from Siemens.
- - -
It appears to me that Siemens is following the same route as Adobe: get an international body to certify PDF as a standard so that Adobe can call it "open."
This is only half-open; the other half of openness is missing in that only Siemens and Adobe decide what gets to be in their file formats.
JT and PDF are half-proprietary, half-open.
Comments