FBICS has a tool catalog with many features. The data is stored in a STEP Part 21 file.
IMO, it would be worthwhile to examine the features Tom envisioned even if Part 21 won't be used. I think there is at least some discussion of the catalog in the FBICS docs on Tom Kramer's NIST page. I could do some digging if there is interest beyond what is mentioned in those docs. On Jan 5, 2010 12:28 PM, "Michael Haberler" <mai...@mah.priv.at> wrote: Alex, I glossed over your references and am shocked, it's just a single *table* ;-) I'm proposing a much more moderate goal: to encode the current EMC tool table such that it can be reused by other programs, and with some self-description features (field names, types, version number, machine type, the like). The intent is to prevent breakage when the tool table is extended, that's all. Is that something useful enough to pursue? -Michael Am 05.01.2010 um 10:00 schrieb Alex Joni: > <snip> >> >> Since I assumed shareable tool information is an industry-wide >> problem >> I had... ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
