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 been googling around on the issue but didnt find a obvious >> candidate for such a format, although a saw a manufacturer who makes >> tool geometry information available in XML. Maybe there is such a >> format, I just dont know. > > The only one I'm aware of is ISO 13399[1] part of STEP[2]. > > The 13399 uses a description language called EXPRESS[3] which is > encapsulated in STEP-XML[4]. > I am sure it's a PITA to implement it in emc2, especially since > buying/getting the standards is a pain. > OTOH NIST is working on some STEP related things, maybe they could > offer > some insight in that area. > > [1] - http://en.wikipedia.org/wiki/ISO_13399 > [2] - http://www.tc184-sc4.org/titles/STEP_Titles.htm > [3] - http://en.wikipedia.org/wiki/ISO_10303-11 > [4] - http://en.wikipedia.org/wiki/STEP-XML > Some more references on STEP: http://www.wikistep.org/index.php/Main_Page > > Regards, > Alex > ------------------------------------------------------------------------------ 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
