Issue 2622:  PDM Enablers - cannot determine client type for file transfer                                                                                                                                          (pdm-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: In the PdmDocumentManagement module, the SecuredFile interface defines operations begin_put_buffer and begin_get_buffer to initiate file content transfers.  Each of these operation has a transfer_encoding parameter to determine whther the transfer should proceed in a straight "binary" mode, or in an "8-bit" character/text mode.  In 8-bit mode, between UNIX and MS Windows machines, the buffer transfer operations should adjust the end-of-line CR/LF bytes in the file according to the platform conventions.  However, there is no defined way for the server to know what type of platform the client is.
 
 The begin_put_buffer and begin_get_buffer operations should have a parameter to tell the server what type of platform the client is.
 

Resolution: resolved by 1.2 RTF
Revised Text: PdmProductStructureDefinition::PartMaster::part_type and part_classification: it is unclear what to do if a part has multiple classes or just doesn't mesh with AP203. Recommend clarifying and generalizing the definitions to support AP210 and 214.
Resolution:
The STEP AP203-specific value restrictions are removed from the specification.  Values of these fields must be general enough to support a variety of information models, depending on the PDM system implementation and business rules.
Revised Text:
Replace the attribute descriptions in the table in 2.7.3.10 PartMaster with following:

part_type	Indicates the type of the part.  Meaning and valid values may be determined by the site's business rules or by reference to another information model standard, such as a STEP application protocol.

part_classification	Provides a way to classify the part.  Meaning and valid values may be determined by the site's business rules or by reference to another information model standard, such as a STEP application protocol.

Actions taken:
April 27, 1999: received issue
April 27, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
From: David Flater <dflater@nist.gov>
Date: Tue, 27 Apr 1999 08:56:43 -0400 (EDT)
To: issues@omg.org
Cc: pdm-rtf@omg.org
Subject: PDM RTF Issue, part_classification
X-Public-Key: Available at
http://www.mel.nist.gov/msidstaff/flater/flater.htm
X-Keyserver: wwwkeys.pgp.net

PdmProductStructureDefinition::PartMaster::part_type and
part_classification:  it is unclear what to do if a part has multiple
classes or just doesn't mesh with AP203.  Recommend clarifying and
generalizing the definitions to support AP210 and 214.

DWF