sdkname=IdObject The ApplicationRef element is meant to relate the parent element (Part, Representation, etc) back to the owning entity in the sending application. The attributes can be described as follows: - application : the context in which the contents of the label and version attributes make sense. Whether this field includes an application version number is up to the application, as long as it starts with something identifiable to the sending application. - label : the string which identifies the application entity - the value of this field is only meaningful to the sending/authoring application. The receiving application can compare the contents of the attribute to test if two entities are the 'same' entity. But the actual value is meaningless to the receiving application. - version : the optional string attribute which identifies the version of the application entity. This attribute can only be used to test if the versions of an entity are the same (i.e. the test is only meaningful if the label attribute values are the same). No version ordering can be deduced from the value. Similar to the label attribute, the version attribute contents are meaningless to the receiving application. sdkname=DescriptionObject The DescriptionBase type is an abstract base type for PLM XML types which have optional name, description and ApplicationRef. Sub-elements: Description Readable textual description of the element. ApplicationRef A means of uniquely identifying the element in terms understood by the sending system. output=ignore output=ignore output=ignore output=ignore output=ignore output=ignore The Attribute element is an abstract element. Useful attributes (ones that include fields) must be derived from the Attribute element defined within this schema. The derived attributes will define their data elements to represent data fields. The derived attributes also need to be set as 'equivalent' to the Attribute element. This enables the new derived attribute to be inserted into documents wherever the Attribute element is allowed. output=ignore sdkname=Entity3D output=ignore output=ignore sdkname=EntityObject Material definition that can be associated with a remote entity. This type describes whether the PLMXML reference is specifying a single entity or a set of entities. Base class for defining a reference to an entity. All entity reference elements should be based on this type and defined as a substitution class for EntityRef. Attribute: - name -(optional) Name of the reference - select -(mandatory) Type of the reference - single or multiple. It provides the application with additional information about what the reference is actually referencing : a set of entities or a single entity. - type -(mandatory) Type of the reference - body, face, edge or vertex. Locator reference format. Locator reference element. The reference is a URI based reference and the syntax of the URI must be pre-defined. Hence the only predefined type is currently eXTPointer. Attribute: - locationRef -(mandatory) The value of the URI reference. - type -(mandatory) Format of the locator reference. Attribute reference element. The reference is based on a user defined named attribute on the host representation. This type enables the author to note the attribute name, field name/index and the value of the attribute. Attributes: - name -(mandatory) The name of the attribute to query - field -(optional) The name of the field within the attribute - index -(optional) The index of the field within the attribute (if 'field' cannot be mapped). - value -(mandatory) The value of the attribute to match. GUID reference element. This simply specifies the GUID of the entity being referenced. Attribute: - guid - (mandatory) The GUID of the entity referenced, in the form of a string containing 32 hex digits, with arbitrary non-hex spacing characters. This abstract datatype describes a single feature within the feature tree hierarchy. The feature description contains basic information such as name and type, as well as information to link the feature to the originating application. Parameter descriptions can also be included in the feature description. Elements: - Type - (1) element describing the type of feature. This is an application specific type. The receiving application is not meant to deduce or interpret the type but could use it to classify or group the feature. - Parameter - (0 or many) elements to describe the parameters associated with the feature. It is up to the application to decide what parameters to exchange or describe within the feature description. - EntityRef - (0 or many) references to entities on another representation (eg. a BRep) expressed as PLMXML references. Attributes: - name - (required) display name for the feature - nextFeature - (optional) the XML id of the next feature in the feature hierarchy. - targetFeature - (optional) the XML id of the target feature that this feature relies on. The target feature defines which feature forms the resultant entity. - toolFeature - (optional) the XML id of the tool feature that this feature relies on. - suppressed - (default=false) TRUE if the feature is suppressed in the feature tree. - editable - (default=false)) TRUE if any parameters of the feature may be edited. Generic feature element which can be used to enumerate 'any' parameterised feature. No semantic or specialised information is exchanged via this schema. This datatype describes a feature hierarchy for feature based modelling system. The feature hierarchy is represented via a single linked list of set of feature elements that reference the next feature in the hieratchy. The linked list hierachy must describe the features in 'replay' order (ie. first operation first in the hierachy). There is scope to describe 'tree-like' dependencies via additional 'dependentFeatures' reference attributes. The feature tree is represented within PLMXML as an 'Internal Representation' of a part - the FeatureTreeType is based on InternalRepBase and the element FeatureTree is a substitution class for InternalRep. Elements: - Type - (1) element describing the type of feature tree. This is an application specific type. The receiving application is not meant to deduce or interpret the type but could use it to classify feature tree. - Feature - (0 or many) the list of features thaat make up the feature tree. Attributes: - name - (required) display name for the feature tree. - firstFeature - (optional) the XML id of the first feature in the feature hierarchy. - editable - (optional) TRUE if any features of the feature tree may be edited. Reference Point element Planar Coordinate system Geometry composition Top level construction geometry element Basic texture data format definition Determines the length of each data element in the hexBinary data element. RGBA = 4 bytes of red, green, blue and alpha RGB = 3 bytes of red, green and blue LA = 2 bytes of luminance and alpha A = 1 byte of alpha L = 1 byte of luminance Basic 1D texture data definition Basic 2D texture data definition Basic texture data definition Texture control definition Basic texture definition Texture coordinates Texture structures that can be associated with a remote entity. This class represents the <CompoundRep> element in an plmxml file. Part representations for the PLMXML Schema This class represents the <Representation> element in an plmxml file. The Representation element in an plmxml file refers to a model in some particular format, such as XT or jXT. It can refer 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). Applications can define derived classes of Representation (for example, XTRepresentation), to manage model data in different formats, and to load them into virtual memory. Model entities loaded in this way are referenced by a PLMXML_MODELLER_HANDLE (which might, for example, be a memory pointer). View definition for PLMXML Schema sdkname=PartType sdkname=Part Basic types that can be represented by user value entries and tables. int = Data entity is an integer ints = Data entity is a list of integers real = Data entity is a real reals = Data entity is a list of reals boolean = Data entity is a boolean (true/false) booleans = Data entity is a list of booleans reference = Data entity is a reference (anyURI) enum = Data entity is an enumeration. list = Data entity is a list item. Datatype that defines a single entry in the user list. The element will consist of a value attribute and an optional description attribute. The string 'value' attribute must contain data of the type specified by the 'type' attribute in the owning list. Datatype to define a list of user specified data items. Each item in the list is of the same type - as specified by the 'type' attribute'. Group of attributes to specifiy the valid range of a user value data item. Group of attributes for specifying the user data item. sdkname=UserValue The datatype specifying all the attributes and fields that will define a single user data item within a user data table. title - is the name of the entry in the data table value - is the current value of the data entry type - the type of the data enetry: - int : value = single integer - ints : value = list of integers - real : value = single real (double) value - reals : value = list of real (double) values - boolean : value = single boolean (true/false) value - booleans : value = list of boolean values - reference: value = single reference (anyURI) - enum : value = enumeration value - UserList or dataRef = List of string values that make up enumeration. - list : value = ignored - UserList or dataRef = List of values that make up data. The datatype for defining the table of user values. The type is based on the plm:Attribute base class so that it may be substituted wherever PLMXML attributes are permitted. The top level element for defining user values. It is a substitute class for plm:Attributes sdkname=UserEnum The datatype for defining a user defined enumeration. The element contains a single value for the enumeration and a reference to a table element (expected to be an element called 'UserList' defined above. The value must be one of values listed in the user list. This class represents the <XTData> element in an plmxml file, which is used to embed XT files in a Representation element, for example: <Representation ...> <XTRep> <XTData>T51 : TRANSMIT FILE created by modeller version 130021217 SCH_1300212_130060 12 1 63 2 3 0 0 0 0 1e3 1e-8 0 0 0 1 0 1 1 4 5 6 7 8 9 10 81 1 2 63 11 1 0 0 0 0 1 ... </XTData> </XTRep> </Representation> XT Representation component of the PLMXML Schema sdkname=GramsMillimetres sdkname=GramsCentimetres sdkname=KilogramsMetres sdkname=PoundsFeet sdkname=PoundsInches PLMXML attribute describing mass properties. ChildElementOccurrences=1 Request identifier. The abstract datatype and element for Query elements. The datatype describing the data context for PLMXML request. This effectively identifies the part or application context for the request. Elements: - Query - (required) the query itself. Note that this is an abstract element where a substitution element must be used. Attributes: - name - (optional) name of the data context or part. - format - (required) the format of the context. - context - (required) the location or identifier of the data context. sdkname=DocumentBase This class corresponds to a top-level element in an plmxml file. Document and RequestDocument are derived classes of this, which correspond to <plmxml> and <plmxmlRequest> elements, respectively. The main PLMXML data request element. This element must appear within it's own document. The element contains anumber of ields for describing the context of the request (eg. the part name, etc) and the type of data to be returned. The application making the request provides it's own context within the data request element via the 'requestId' attribute. This attribute value must be returned in the resultant PLMXML document. This enables the application to match PLMXML documents with the data request. Elements: - Description - (optional) Description of the data request. This data has no semantic. It is purely a user field. - Request - (optional) The application part context and request. Attributes: - schemaVersion - (fixed) The version of the schema with which the data request complies. - author - (mandatory) The author of the document, making the request. - application - (mandatory) Name of the application making the request. - requestId - (mandatory) Application supplied identifier for the request. This value will be returned in the resulting PLMXML document. - time - (mandatory) Time of the request. - date - (mandatory) Date of the request. - language - (optional) Language specifier. sdkname=RequestDocument This type gives the parameters which control the a facet generation operation. Attributes: curveAngularTol - max angular change between chords along edge curveDistanceTol - max edge/chord distance surfaceAngularTol - max angular change between facets surfaceDistanceTol - max face/facet distance tristripControl - whether tristrips allowed facetsetControl - whether facetsets are created per face, per material, or unspecified This datatype is used to describe a representation query. The element is defined as a substitution element for the abstract Query element. Attributes: - type - (required) The type of representation requested. Currently, this is : XT, JT, jXT or All - label - (optional) If a suitable application label is specified the request must return the representation matching the specified label. If no label is specified, then the request must return an PLMXML document that identifies all the appropriate representation in the specified context. This datatype is used to describe a product structure query. The element is defined as a substitution element for the abstract Query element. This datatype is used to describe a Feature/FeatureTree query. The element is defined as a substitution element for the abstract Query element. Attributes: - label - (optional) If a suitable application label is specified the request must return the feature matching the specified label. If no label is specified, then the request must return an PLMXML document that specifies the whole feature tree within the specified context. This datatype is used to describe an Annotation query. The element is defined as a substitution element for the abstract Query element. Attributes: - label - (optional) If a suitable application label is specified the request must return the annotation matching the specified label. If no label is specified, then the request must return an PLMXML document that specifies all the annotations within the specified context. The request return types. This datatype is used to return status information to the user within the resultant PLMXML document. The element is in the form of a PLMXML attribute. This implies that an PLMXML docuemnt could just be returned with one RequestInformation element in it - useful for returning errors and no data. Attributes: - requestId - (required) The application request identifier. - result - (default=Success) Indicates success or failure with a code. - description - (optional) textual description of failure, etc. The redline markup element for PLMXML - is a simple annotation type that describes its textual data via the xhtml spec. Thus the text can include format and font information as per a normal html document. The redline element(s) is defined via simple polyline geometric element and references to related entities can be made via the 'EntityRef' element. output=ignore V1.0 of the PLMXML Schema. This schema definition, in W3C format, can represent the following data in various combinations and permutations : - Product definition via instance graph and occurrence view representations - Part representation via facet representation and/or external refs to XT files - Attribute information output=ignore sdkname=Document