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:
“A common and natural result of an undue respect for law is, that you may see a file of soldiers, colonel, captain, corporal, privates, powder-monkeys, and all, marching in admirable order over hill and dale to the wars, against their wills, ay, against their common sense and consciences, which makes it very steep marching indeed, and produces a palpitation of the heart.”
—Henry David Thoreau (1817–1862)
“It is difficult even to choose the adjective
For this blank cold, this sadness without cause.
The great structure has become a minor house.
No turban walks across the lessened floors.
The greenhouse never so badly needed paint.”
—Wallace Stevens (1879–1955)