File Structure
The relationship of product structure hierarchy to exported JT file structure is arbitrary. Any node in the hierarchy may be specified as the start of a new JT file. Thus, product structure may be represented in a variety of JT file configurations.
JT supports common product structure-to-file structure mappings. These include:
- Per part - All assembly nodes in a product structure hierarchy are stored in a single JT file, and each part node in the hierarchy is stored in an individual JT file in a subdirectory that is of the same name as the assembly JT file.
- Fully shattered - Each product structure node in the hierarchy is stored in an individual JT file.
- Monolithic - All product structure is stored in a single JT file.
- PLMXML - An open XML-based file format. A PLMXML-structure could link to the model data in another file (an External Representation), or the data can be embedded within the Representation element in the XML file (an InternalRepresentation).
Client applications may use these mappings, or choose to define their own custom mapping.
Read more about this topic: JT (visualization Format)
Famous quotes containing the words file and/or structure:
“I have been a soreheaded occupant of a file drawer labeled “Science Fiction” ... and I would like out, particularly since so many serious critics regularly mistake the drawer for a urinal.”
—Kurt Vonnegut, Jr. (b. 1922)
“There is no such thing as a language, not if a language is anything like what many philosophers and linguists have supposed. There is therefore no such thing to be learned, mastered, or born with. We must give up the idea of a clearly defined shared structure which language-users acquire and then apply to cases.”
—Donald Davidson (b. 1917)