ISO, "Product Data Representation and Exchange, Part 1: Overview and Fundamental Principles", No. 10303-1, International Organization for Standardization, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... The NIST PDES Toolkit: Technical Fundamentals 1 Introduction The NIST PDES Toolkit [Clark90a] provides a set of software tools for manipulating Express [Part11] information models and STEP [Part21] product models. It is a research oriented toolkit, intended for use in a research and testing environment. This document gives a technical introduction to the Toolkit, providing a programmer with basic knowledge of its structure. Also covered are the mechanics of building Toolkitbased ....

ISO CD 10303 -- 21, Product Data Representation and Exchange -- Part 21, Clear Text Encoding of the Exchange Structure, ISO TC184/SC4 Document N78, February, 1991.

....databases will yield better STEP implementations. SDAI does not specify details about concurrent access control and transaction management. These issues are to be handled by each database management system. It also does not support connections to remote repositories. The SDAI binding to CORBA IDL [14] addresses this problem. The integration of STEP and CORBA allows for network interoperable access to STEP data, described below. 5. Network interoperable databases Interoperability is defined as the effective interconnection of two or more different computer systems, databases, or networks in ....

....enable objects to make and receive requests and responses in a distributed environment. Objects made available through an ORB publish their interfaces using CORBA s Interface Definition Language (IDL) In order to integrate STEP and CORBA, ISO has released a draft standard of the SDAI IDL binding [14]. This will allow for STEP data models to be shared among applications and databases in a network interoperable environment. Figure 4 illustrates the network interoperable access to STEP data. End user applications and STEP databases may be in different locations and or networks, connected to ....

ISO TC184/SC4/WG7 Document N396, Product Data Representation and Exchange Part 26, Interface Definition Language Binding to the Standard Data Access Interface, ISO Working Draft, December 7, 1995.

....be unset. schema instance.change date for any modified or created schema instance shall be set to the current date. sdai model.change date for any modified or created sdai model shall be set to the current date. Figure 3 Specification of the SDAI operation End transaction access and commit [12] . Early binding, or code generation: the application is generated for a specific information model written in EXPRESS. Late binding, or data dictionary: the implementation is a general purpose software that is independent of information model, allowing access to data defined by any EXPRESS ....

ISO TC184/SC4/WG7 Document N382, Product Data Representation and Exchange Part 22, Standard Data Access Interface, ISO Committee Draft, May 31, 1995.

....technology. Any application whose data is modeled in EXPRESS can utilize SDAI, thereby making the actual database transparent. SDAI specifications are written in EXPRESS. Since EXPRESS is not intended to be implemented, SDAI has several bindings to programming languages, such as C [9] C [10], and Fortran. Implementations vary in binding style, i.e. the way in which the database software is structured [11] Input Transaction: sdai transaction; The transaction allowing access to entity instances which is to be terminated. Possible error indicators SS NOPN Session not open. ....

ISO TC184/SC4/WG7 Document N403, Product Data Representation and Exchange Part 23, C++ Programming Language Binding to the Standard Data Access Interface, ISO Committee Draft, December 25, 1995.

....data storage technology. Any application whose data is modeled in EXPRESS can utilize SDAI, thereby making the actual database transparent. SDAI specifications are written in EXPRESS. Since EXPRESS is not intended to be implemented, SDAI has several bindings to programming languages, such as C [9], C [10] and Fortran. Implementations vary in binding style, i.e. the way in which the database software is structured [11] Input Transaction: sdai transaction; The transaction allowing access to entity instances which is to be terminated. Possible error indicators SS NOPN Session not ....

ISO TC184/SC4/WG7 Document N394, Product Data Representation and Exchange Part 24, Standard Data Access Interface - C Language Late Binding, ISO Committee Draft, July 28, 1995.

....and level 3 has research and commercial implementations. Level 4 implementations are subject of basic research. The next sections discuss STEP implementation methods and their importance in the implementation of shareable engineering databases. 3. File exchange and working form STEP Part 21 [4] defines an application independent way of encoding product data for file exchange. Figure 1 presents an example of Part 21 usage, with EXPRESS schema definitions and an exchange file with data structures compliant to the schemas. The STEP implementation level 1 defines a static text file ....

....REPRESENTATIONS FOR A TRIANGULAR EDGE LOOP WERE POSSIBLE. EACH REPRESENTATION MAY CARRY DIFFERENT SEMANTICS, WHICH MAY REPRESENT CHARACTERISTICS OF PARTICULAR APPLICATION SYSTEMS. ENDSEC; END ISO 10303 21; Figure 1 EXPRESS schema definitions (a) and an exchange structure example (b) [4] According to Fowler [5] implementation level 2 is an extension to Level 1, where the physical file is converted to a working form. Since most file based implementations use this approach, the distinction between levels 1 and 2 have disappeared. Part 21 files allow for data exchange and ....

ISO DIS 10303-21, Product Data Representation and Exchange Part 21, Implementation Methods, Clear Text Encoding of the Exchange Structure, Draft International Standard, May 28, 1993.

....information model specified in the application layer. A description of information models is given in [2] This paper focuses on STEP implementation, with an emphasis on shareable databases. Both information model and implementation method specifications are written in EXPRESS, STEP Part 11 [3]. The implementation methods define the mapping of an application schema onto a specific computer technology. Four progressive implementation levels were devised: Level 1: File exchange passive text file transfer . Level 2: Working form exchange software assisted, active file transfer ....

ISO TC184/SC4/WG5 Document N65 (P2), Product Data Representation and Exchange Part 11, EXPRESS Language Reference Manual, ISO International Standard, November 1, 1994.

....great strides taken in information technology in the past few decades. Achieving integration requires at least compatibility of data representations, communication paradigms, and system architectures. Advances have been made in each of these areas, such as product data exchange, e.g. ISO 10303 (ISO a 1995), communication protocols, e.g. TCP IP (Arnett et al. 1995) OSI 1 , and architectures, e.g. Computer Integrated Manufacturing (CIM) Framework (Eng et al. 1996) Common Object Request Broker Architecture (CORBA) Seigel 1996) One area of data representation that has received relatively little ....

.... (Catron and Ray 1991) MOSES (Model Oriented Simultaneous Engineering Systems) Molina et al. 1994) BPFL (Berkeley s Process Flow Language) CS CAPP TM process planning system (CS CAPP 1994) AP 213 (Application Protocol in STEP: Numerical Control process plans for machined parts) (ISO b 1995); MetCAPP TM (MetCAPP 1994) Workflow Management Coalition (WfMC) specifications (WfMC Members 1994) Knowledge Interchange Format (KIF) Genesereth and Fikes 1996) Microsoft Project TM 08 13 98 Requirements for Specifying Manufacturing Engineering and Business Processes 4 (Microsoft 1994) ....

ISO-b, 1995, Product data representation and exchange: Part 213: Application Protocol: Numerical Control process plans for machined parts, ISO Standard 10303-213.

....great strides taken in information technology in the past few decades. Achieving integration requires at least compatibility of data representations, communication paradigms, and system architectures. Advances have been made in each of these areas, such as product data exchange, e.g. ISO 10303 (ISO a 1995), communication protocols, e.g. TCP IP (Arnett et al. 1995) OSI 1 , and architectures, e.g. Computer Integrated Manufacturing (CIM) Framework (Eng et al. 1996) Common Object Request Broker Architecture (CORBA) Seigel 1996) One area of data representation that has received relatively little ....

.... (Catron and Ray 1991) MOSES (Model Oriented Simultaneous Engineering Systems) Molina et al. 1994) BPFL (Berkeley s Process Flow Language) CS CAPP TM process planning system (CS CAPP 1994) AP 213 (Application Protocol in STEP: Numerical Control process plans for machined parts) (ISO b 1995); MetCAPP TM (MetCAPP 1994) Workflow Management Coalition (WfMC) specifications (WfMC Members 1994) Knowledge Interchange Format (KIF) Genesereth and Fikes 1996) Microsoft Project TM 08 13 98 Requirements for Specifying Manufacturing Engineering and Business Processes 4 (Microsoft 1994) ....

ISO-a, 1995, Product data representation and exchange: Part 1: Parts Library - Part 1: Overview and Fundamental Principles, ISO Standard 10303-1.

....systems do not communicate much context information between each other; the context of the information exchanged was agreed upon by the system designers a priori and is implicit in the software. The exchange of a single property in STEP (STandard for the Exchange of Product model data) [ISO94] technology, on the other hand, includes several context setting references: references to the measurement units used (e.g. newton meters) the various representations of the property (e.g. as thermal 4 energy, as mechanical energy) the technical discipline it concerns (e.g. structural ....

.... ANSI Ad Hoc Group on Ontology Standards Representation [ANSI98] CYC [CYC98] Enterprise Ontology [ENT98] LOOM [LOOM98] MikroKosmos [MIKRO95] Ontolingua [ONTO96] 7 Sensus [SENS98] SPAR (Shared Planning and Activity Representation) SPAR98] STEP (Standard for the Exchange of Product model data) [ISO94] TOVE (Toronto Virtual Enterprise) TOVE98] Wordnet [WORD98] We then performed a high level analysis of each of the above ontological systems and eliminated a few due to their lack of appropriateness to this project. In general, the project analyzed these ontologies against the following three ....

ISO, 10303-1:1994, Product data representation and exchange: Part 1: overview and fundamental principles.

....between computer aided design systems. A new standard for product data exchange is being developed by the Technical Committee on Industrial Automation of the International Organization for Standardization (ISO) This new standard, called the Standard for the Exchange of Product Model Data, or STEP [7], goes far beyond defining a computer representation of blueprints. It is a new language for product specification, as different from drawings as Chinese is different from English. I have chosen the metaphor of language for more than its evocative power. I would like to analyze the current ....

ISO CD 10303-1, Product Data Representation and Exchange---Part 1: Overview and Fundamental Principles, Int. Org. for Std., 1992. Available from Secretariat, ISO/TC

....The first objective, when the APDES project began, was to demonstrate the feasibility of using STEP for apparel. The objective was accomplished by developing an information model for pattern data using STEP technology [Lee1] The information model was represented in the EXPRESS modeling language [ISO11]. The model was implemented in a computer program that exchanges pattern data between two proprietary industry formats [Moncarz] A neutral set of data structures, based on the information model developed, was used as the intermediary in this process. It was concluded that STEP APs can provide the ....

ISO DIS 10303-11, Product Data Representation and Exchange - Part 11: The EXPRESS Language Reference Manual, August 1992.

....of the reactive scheduling system need to be developed. The first step in this process is defining models of the information to be exchanged. This paper focuses on conceptual models for Factory Status information and Status Message information. Express G, which is a part of the STEP standard [3], is the language used to develop the models. FACTORY STATUS INFORMATION MODEL The Factory Status information model defines what is meant by status from the schedulers perspective. This status provides critical, dynamic information scheduling applications need to update their simulation models ....

ISO 10303-11:1994, Product Data Representation and Exchange -- part 11: Express Language Reference Manual, International Organization for Standardization, (Geneva, 1994)

....the information has become more complex, it has become much more difficult for software developers to provide translators between every pair of applications that need to exchange information. Standards based translation mechanisms, such as the Standard for the Exchange of Product Model Data (STEP) [1], have simplified translator development for some manufacturing software developers. By developing a single translator between an application that uses product model data and STEP, the application can inter operate with a wide variety of other applications that have a similar translator between ....

ISO, "Product data representation and exchange: Part 1: overview and fundamental principles," ISO Standard 10303-1, 1992.

....so chosen because it is an international standard data modeling language. The graphical representation of the model is in EXPRESS G, which is an extension of EXPRESS for graphical representation. Many entities of this model are dependent upon entities defined in ISO 10303 Part 41 [20] and Part 43 [21]. The text between ) and ( is the definitions of 8 the model constructs, which is a part of the model. Dimension schema The graphical representation of the schema in EXPRESS G is shown in Figure 1. Figure 1 Graphical representation of Dimension Schema 9 Types of this schema are defined ....

ISO/DIS 10303-43, "Product Data Representation and Exchange - Part 43: Integrated generic resources: Representation structure," International Organization for Standardization, Geneva, Switzerland, 1993.

....data are to be addressed in several areas: feature and product relationships, dimensioning needs, and tolerancing needs. Dimension information requirement and abstraction The most generic dimension consists of a magnitude and one or more dimensioned shape aspects. Shape aspect is defined in [20] as a physical portion of a product shape. For modeling dimensions and tolerances, the shape aspect and the feature as used in ANSI Y14.5 are equivalent and used interchangeably in this paper. A dimension defines a geometric characteristic of a feature, such as the diameter of a cylindrical hole, ....

....is in EXPRESS, so chosen because it is an international standard data modeling language. The graphical representation of the model is in EXPRESS G, which is an extension of EXPRESS for graphical representation. Many entities of this model are dependent upon entities defined in ISO 10303 Part 41 [20] and Part 43 [21] The text between ) and ( is the definitions of 8 the model constructs, which is a part of the model. Dimension schema The graphical representation of the schema in EXPRESS G is shown in Figure 1. Figure 1 Graphical representation of Dimension Schema 9 Types of this ....

ISO/DIS 10303-41, "Product Data Representation and Exchange - Part 41: Integrated generic resources: Fundamentals of product description and support," International Organization for Standardization, Geneva, Switzerland, 1993.

....NIAM [7] IDEF1x provides a method to document data used in processes such as design process and manufacturing process. IDEF0 [5] defines activities and the associated information which supports the processes. EXPRESS is an international standard data modeling language for modeling product data [8]. EXPRESS was developed as part of the STEP development effort. In addition to the language syntax itself, STEP has also established standard practice guidelines for using the EXPRESS modeling language. Since the dimension and tolerance data is part of 3 the product data that defines aspects of a ....

ISO/DIS 10303-1 "Product Data Representation and Exchange - Part 1: Overview and Fundamental Principles," International Organization for Standardization, Geneva, Switzerland,

....and semantics for defining data elements and the relationships between the elements. Most data modeling languages that are available today are used to describe a static view of data semantics. At least three data modeling languages are available and well known; they are IDEF1x [4] EXPRESS [6], and NIAM [7] IDEF1x provides a method to document data used in processes such as design process and manufacturing process. IDEF0 [5] defines activities and the associated information which supports the processes. EXPRESS is an international standard data modeling language for modeling product ....

ISO/DIS 10303-11, "Product Data Representation and Exchange - Part 11: The EXPRESS Language Reference Manual," International Organization for Standardization, Geneva, Switzerland, 1993.

....applications and systems. This paper describes a data model which was developed to provide a foundation for the development of STEP Part 47: Industrial automation systems and integration Product data representation and exchange Integrated generic resources Shape variation tolerances [2]. APPLIED DATA MODELING METHODS Data modeling methods provide fundamental rules and guidelines in the development of a data model using modeling tools. These methods should provide a full range of concepts of model building that will ensure a precise model with shareability, extensibility, and ....

ISO/CD 10303-47, "Product Data Representation and Exchange - Part 47: Shape Variation Tolerances," ISO/TC 184/SC 4 N222, 1993, available from the National Institute of Standards and Technology, Gaithersburg, Maryland.

....and the different inheritance relationships are challenges for object oriented systems as well. Data defined in EXPRESS need to be manipulated by application programs at the same level of abstraction. This is the objective of another part of STEP, namely SDAI (Standard Data Access Interface [14]) 3 Accessing and manipulating EXPRESS data via SDAI 3.1 Motivation for SDAI Only recently has SDAI been discussed as a database DML. Initially, the still prevalent technique of exchanging files pushed the development of an API (application programming interface) The STEP file import and ....

....operations The abstract, logical data store for EXPRESS data is called SDAI repository. 3 Again, we keep a database 3 This term is subject to change late in 1994, and storage system related aspects of SDAI repositories will also be addressed. Throughout this paper, we refer to the document [14]. implementation in mind, i.e. a DBMS that understands SDAI requests. Which operations on such a repository must be supported, then At first, we need to know that SDAI groups entity instances in so called SDAI models. Instances of a model belong to a particular EXPRESS schema. Since a ....

[Article contains additional citation context not shown here]

ISO. 10303-22: Product Data Representation and Exchange - Part 22: Standard Data Access Interface. editorially revised CD (N350), May 1994.

....measurements) Another property of objects specified by example 1 is the following: if a2 is provided, either a1 or a2 must be negative. From a DDL point of view, valid Ainstances do not violate the integrity constraint stated in the WHERE clause (see section 2. 3) 1 The official ISO document is [13]. A first text book on EXPRESS has been published only recently [24] Inheritance is expressed by the SUBTYPE clause which lists all inheriting supertypes. Ambiguities due to polymorphism must be syntactically resolved. ENTITY B SUBTYPE OF (A) x: BINARY; SELF A.a1: REAL(10) SELF A.a2: REAL; ....

ISO. 10303-11: Product Data Representation and Exchange - Part 11: EXPRESS Language Reference Manual. as IS to be released in 1994.

....of the language. This means, we have defined the extension as small as possible in order to introduce no further complex concepts into the existing language which also keeps the language compliant with the existing EXPRESS concepts. As a further consequence, EXPRESS P is compatible with ISO 10303 21, the exchange format for product data representation (ISO 10303 21, 1993) This means, that an EXPRESS P specification is instantiated by an ISO 10303 21 STEP File. The remainder of this paper is organized as follows. Section 2 gives an overview of the related approaches, i.e. languages we ....

....as small as possible in order to introduce no further complex concepts into the existing language which also keeps the language compliant with the existing EXPRESS concepts. As a further consequence, EXPRESS P is compatible with ISO 10303 21, the exchange format for product data representation (ISO 10303 21, 1993) This means, that an EXPRESS P specification is instantiated by an ISO 10303 21 STEP File. The remainder of this paper is organized as follows. Section 2 gives an overview of the related approaches, i.e. languages we inherited our concepts from. In Section 3 we introduce the basic ....

[Article contains additional citation context not shown here]

ISO 10303-21, 1993, "Product Data Representation and Exchange - Part 21: Clear Text Encoding of the Exchange Structure," ISO DIS 10303-21, National Institute of Standards and Technology, Gaithersburg, USA.

.... Project 8370 ESIP EDA Standards Integration Promotion Prepared by Wolfgang Mueller, Cadlab, Winfried Felser, Heinz Nixdorf Institut, Frank Buijs, Cadlab The Process Modelling Language EXPRESS P ESIP Extra Deliverable ESIP UPAD 002.1 March 8, 1995 (c) Copyright 1995 Bull S.A. International Computer Ltd, Siemens Nixdorf Informationssysteme AG, Nederlandse Philips Bedrijven B.V. Racal Redac Ltd. Siemens AG, Technologia Grupo INI, Thomson CSF, Universitaet GH Paderborn. This document and the information contained herein may not be copied, ....

.... Project 8370 ESIP EDA Standards Integration Promotion Prepared by Wolfgang Mueller, Cadlab, Winfried Felser, Heinz Nixdorf Institut, Frank Buijs, Cadlab The Process Modelling Language EXPRESS P ESIP Extra Deliverable ESIP UPAD 002.1 March 8, 1995 (c) Copyright 1995 Bull S.A. International Computer Ltd, Siemens Nixdorf Informationssysteme AG, Nederlandse Philips Bedrijven B.V. Racal Redac Ltd. Siemens AG, Technologia Grupo INI, Thomson CSF, Universitaet GH Paderborn. This document and the information contained herein may not be copied, used or disclosed ....

[Article contains additional citation context not shown here]

ISO 10303-21, "Product Data Representation and Exchange - Part 21: Clear Text Encoding of the Exchange Structure," TC184/SC4/WG7, National Institute of Standards and Technology, Gaithersburg, USA, 1995.

....and complete inference rules for covering is given. However, all of the above models consider covering only on entity classes, whereas covering on properties has not been studied. Regarding disjointness, the information that two entity classes are disjoint is represented in many data models [37, 31, 18, 23]. However, the information that two properties are disjoint is represented in very few data models, e.g. NIAM [37] In our data model, we support both kinds of disjointness, i.e. disjointness of entity classes and disjointness of properties. Regarding Isa and Risa, all data models support Isa on ....

ISO DIS 10303-11, Product Data Representation and Exchange - Part 11: The EXPRESS Language Reference Manual, TC184/SC4 N151, (1992).

....Therefore, there must exist an instance x of a whose from object is o. As a is a subclass of a 0 , it follows that x is an instance of a 0 . Therefore, a 0 is necessary on c. A similar proof can be given for the case of possible arrows. In some object oriented data models, such as EXPRESS [21], every arrow of a class is supposed to be meaningful , for each instance of the class. In terms of our data model, this means that every arrow of a class must be necessary or possible. For example, the declaration of the arrow maiden name is not allowed on the class Person, as it is ....

....c is optional in a, if not every instance of c must have an a value in the database. Many data models can express that c is total in a, following different approaches. For example, 19, 39, 16, 28] use a keyword (such as, not null, or necessary) to denote that c is total in a. Other data models [27, 21], use a keyword (such as, optional) to denote that c is optional in a; these models interpret the absence of the keyword as c is total in a . Finally, in several data models [35, 6, 34, 26] it is possible to specify the minimum number min of a values that an instance of c can have. If min 1 ....

[Article contains additional citation context not shown here]

ISO DIS 10303-11, Product Data Representation and Exchange - Part 11: The EXPRESS Language Reference Manual, TC184/SC4 N151, (1992).

....to perform full conformance checks by batch checkers which run their validation on an existing set of instances. There are two possibilities to define instances in terms of lexical descriptions. The first format is the so called Physical File Format which has already been accepted as a DIS [ISO10303 21]. The second format is called EXPRESS I [Wilson92] which has been introduced to ISO 10303 as a Working Document in 1992. The main difference between both is that ISO 103033 21 presumes a flattened super subtype relationship. Additionally, in this format the attribute names are omitted in order to ....

.... d1; hair e1; children ( p4, p5, p6) Figure 2: ISO 10303 21 vs. EXPRESS I In the following sections we briefly introduce EXPRESS especially dedicated to the evaluation of super subtype relationships. Additionally, we introduce the STEP physical file format as it is defined in [ISO10303 21]. Thereafter we identify the different classes of validation checks which have to be performed by a full conformance test. These tests are explained giving EXPRESS and ISO 10303 21 instances presuming an already flattened super subtype structure. Finally we give some preliminary outlines on the ....

[Article contains additional citation context not shown here]

ISO/DIS 10303-21, Product Data Representation and Exchange - Part 21: Clear Text Encoding of the Exchange Structure, ISO TC184/SC4/WG5, January 13, 1993.

....support of these process modeling concepts opens the application of EXPRESS P to other domains like telecommunications, protocol specification, and general systems design. We have designed EXPRESS P as a language fully compatible to the EXPRESS IS and its instantiations by STEP Physical Files [14]. The remainder of this paper is organized as follows. Section 2 gives an overview of the related approaches and introduces the languages we inherited our concepts from. In Section 3 we introduce the language EXPRESS P including the graphical means for EXPRESS P (System and Process Diagrams) ....

....DEFAULT: ENDINPUT; ENDREPEAT; ENDPROCESS; interface1.s1 v1 interface2.s2 DEFAULT v1 : v1 1 ENTITY: ETYPE2 TRUE true false PD 3. 6 Instantiating an EXPRESS P Model In order to be compatible to ISO 10303 21 an instance of an EXPRESS P specification is defined by the STEP Physical File Format [14]. In the context of EXPRESS P a Physical File represents a set of data the processes and the systems are initialized with. Each intermediate state of the system can be represented by another Physical File which in the general case is different from the initial one. This is outline by an example ....

ISO 10303-21, "Product Data Representation and Exchange - Part 21: Clear Text Encoding of the Exchange Structure," ISO DIS 10303-21, National Institute of Standards and Technology, Gaithersburg, USA, 1993.

....lot of needed semantics have to be embedded in the application program. The ISO STEP community, on the other hand, emphasizes the development of standards for product modeling and product data exchange. One of its major efforts is the development of an information modeling language named EXPRESS [ISO92]. EXPRESS provides a rich set of constraint specifications by using keywords, functions, procedures and constraint rules. It is a powerful information modeling language. The language has been widely accepted and used by a number of product design and manufacturing communities. Although EXPRESS is ....

....results. LOGICAL operators (e.g. AND, OR, NOT, XOR) receive LOGICAL operands and produce LOGICAL results. BINARY operators receive BINARY operands and produce BINARY results. It is used to manipulate images which are stored in the BINARY data format. For more information on these, please refer to [ISO92]. 2.5.1 Context Expression High level database manipulations can also be specified as expressions in NCL. Database manipulations in NCL is a combination of those in EXPRESS and in K.3. An expression in K.3 can be a complex pattern of object interconnections in multiple object classes or a ....

ISO Technical Committee, "Product Data Representation and Exchange - Part 11: The EXPRESS Language Reference Manual," ISO Document, ISO DIS 10303-11, August 1992.

No context found.

ISO, "Product Data Representation and Exchange, Part 1: Overview and Fundamental Principles", No. 10303-1, International Organization for Standardization, 1994.

No context found.

ISO TC184/SC4, Product Data Representation and Exchange Part 202, Application Protocol: Associative Draughting, ISO Draft International Standard, August 8, 1995.

No context found.

ISO TC184/SC4/WG3 Document N436, Product Data Representation and Exchange Part 214, Application Protocol: Core Data for Automotive Mechanical Design Process, ISO Committee Draft, August 8, 1995.

No context found.

ISO TC184/SC4/WG3 Document N125a, Product Data Representation and Exchange Part 42, Integrated Resources: Geometric and Topological Representation, ISO proposed Committee Draft, July 31, 1992.

No context found.

ISO TC184/SC4/WG5 Document N65(P2), Product Data Representation and Exchange Part 11, EXPRESS Language Reference Manual, ISO International Standard, November 1, 1994.

No context found.

ISO 10303-42. Product Data Representation and Exchange - Part 42: Integrated Resources: Geometric and Topological Representation. Document TC184/SC4/WG3 N125a. ISO Committee Draft, July 31, 1992.

No context found.

ISO 10303-41. Product Data Representation and Exchange - Part 41: Integrated Resources: Fundamentals of Product Description and Support. ISO International Standard, 1994.

No context found.

ISO 10303-26. Product Data Representation and Exchange - Part 26: Implementation Methods: Interface Definition Language Binding to the Standard Data Access Interface. Document ISO TC184/SC4/WG11 N019. Committee Draft, 17 March 1997.

No context found.

ISO 10303-24. Product Data Representation and Exchange - Part 24: Implementation Methods: Standard Data Access Interface - C Language Late Binding. Committee Draft, July 28, 1995.

No context found.

ISO 10303-23. Product Data Representation and Exchange - Part 23: Implementation Methods: C++ Programming Language Binding to the Standard Data Access Interface. Committee Draft, December 25, 1995.

No context found.

ISO 10303-22. Product Data Representation and Exchange - Part 22: Implementation Methods: Standard Data Access Interface. Committee Draft, May 31, 1995.

No context found.

ISO 10303-214. Product Data Representation and Exchange - Part 214: Application Protocol: Core Data for Automotive Mechanical Design Process. Document TC184/SC4/WG3 N436. Committee Draft, August 8, 1995.

No context found.

ISO 10303-21. Product Data Representation and Exchange - Part 21: Implementation Methods: Clear Text Encoding of the Exchange Structure. Draft International Standard, May 28, 1993.

No context found.

ISO 10303-204. Product Data Representation and Exchange - Part 204: Application Protocol: Mechanical Design Using Boundary Representation. ISO Draft International Standard, as accessed at SOLIS, ftp://ftp.cme.nist.gov/pub/subject/sc4, July 17th, 1996.

No context found.

ISO 10303-203. Product Data Representation and Exchange - Part 203: Application Protocol: Configuration Controlled Design. ISO International Standard, 1994.

No context found.

ISO 10303-202. Product Data Representation and Exchange - Part 202: Application Protocol: Associative Draughting. ISO Draft International Standard, August 8, 1995.

No context found.

ISO 10303-201. Product Data Representation and Exchange - Part 201: Application Protocol: Explicit Draughting. ISO International Standard, 1994.

No context found.

ISO 10303-11. Product Data Representation and Exchange - Part 11: EXPRESS Language Reference Manual. Document TC184/SC4/WG5 N65(P2). ISO International Standard, November 1, 1994.

No context found.

ISO 10303-1. Product Data Representation and Exchange - Part 1: Overview and Fundamental Principles. Committee Draft, September 15, 1992.

No context found.

ISO , Product data representation and exchange : Part 213 : Application Protocol: Numerical Control process plans for machined parts, ISO Standard 10303-213, 1995.

No context found.

ISO CD 10303-213, Product Data Representation and Exchange --- Part 213: Numerical Control (NC) process plans for machined parts, International Organization for Standardization, Geneva, June, 1994.

No context found.

ISO CD 10303-207, Product Data Representation and Exchange --- Part 207: Sheet Metal Die Planning and Design, International Organization for Standardization, Geneva, 1993.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC