This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CMET Identifiers in Visio"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new page) |
|||
| Line 1: | Line 1: | ||
| + | [[Category:AboutCMETs]] | ||
There are two files that list the CMETs that can be used in Visio: | There are two files that list the CMETs that can be used in Visio: | ||
*cmetInfo.txt: contains the CMETs as defined in a universal edition | *cmetInfo.txt: contains the CMETs as defined in a universal edition | ||
*Any "local cmets" need to be listed in the cmetInfoExport.txt file that the current generator uses. Unlike the cmetInfo.txt file used by Visio, this file includes the "nn" following UV that is assigned when a CMET achieves normative status (either in a normative spec or a DSTU). The file was renamed in the Generator last year because we do NOT want these extensions used in the cmetInfo.txt file that drives the Visio CMETs. | *Any "local cmets" need to be listed in the cmetInfoExport.txt file that the current generator uses. Unlike the cmetInfo.txt file used by Visio, this file includes the "nn" following UV that is assigned when a CMET achieves normative status (either in a normative spec or a DSTU). The file was renamed in the Generator last year because we do NOT want these extensions used in the cmetInfo.txt file that drives the Visio CMETs. | ||
Latest revision as of 15:17, 8 October 2010
There are two files that list the CMETs that can be used in Visio:
- cmetInfo.txt: contains the CMETs as defined in a universal edition
- Any "local cmets" need to be listed in the cmetInfoExport.txt file that the current generator uses. Unlike the cmetInfo.txt file used by Visio, this file includes the "nn" following UV that is assigned when a CMET achieves normative status (either in a normative spec or a DSTU). The file was renamed in the Generator last year because we do NOT want these extensions used in the cmetInfo.txt file that drives the Visio CMETs.
