Issue 4027: allow "document type" to be the IdContext "kind" (pdm-rtf)
Source: NIST (Mr. Edward J. Barkmeyer, edbark(at)nist.gov)
Nature: Uncategorized Issue
Severity: 
Summary: The class "Document" is not necessarily a useful "object category" for name
scoping.  Documents have
company-standard or even industry-standard "types", e.g. "structures model" or
"piping model", and those are the types of the "business objects" inside the
PDM.  Company document naming conventions may focus on "document type".  E.g.
"Geometric-model, 12345-1" and "Type3-load-analysis, 12345-1" may be unique
names for different DocumentMasters, whereas "DocumentMaster, 12345-1" doesn't
name anything. But "PartMaster, 12345-1" does, because "Part(Master)",
"Geometry-model" and "Type3-load-analysis" are the "business objects".

Resolution: 
Revised Text: 
Actions taken:
November 8, 2000: received issue
Discussion: 
*Recommendation: not clear.  This might work for DocumentMaster, but it creates
problems for DocumentRevision and DocumentIteration.  (There is a related
"profiles" issue for PDME v2.) This might work for DocumentMaster, but it creates problems for DocumentRevision and DocumentIteration.  This is best considered with the whole IdentificationContext issue (4161).

But "document type" does not exist as a defined attribute in PDM Enablers v1.3.  And there is a v2 proposal for adding an "item_type" attribute to ItemMaster, which would relate directly to this issue.  

This issue is deferred, pending the handling of "item type" in PDM Enablers v2.

End of Annotations:=====
Date: Wed, 08 Nov 2000 12:42:04 -0500
From: Ed Barkmeyer <edbark@nist.gov>
Reply-To: edbark@cme.nist.gov
Organization: NIST
X-Sender: "Ed Barkmeyer" <edbark@mailhost.cme.nist.gov>
X-Mailer: Mozilla 4.51 [en]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,fr-FR,de-DE,nl,sv
MIME-Version: 1.0
To: Juergen Boldt <juergen@omg.org>
Subject: Re: Minor modifications to the PDM Enablers requested
byIntergraph
References: <4.2.0.58.20001108121822.0094def0@emerald.omg.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: i8i!!1UBe97Vnd9m4id9


*Issue:  allow "document type" to be the IdContext "kind"
*Source: Ed Barkmeyer, NIST
*Problem: 
The class "Document" is not necessarily a useful "object category" for
*name
scoping.  Documents have
company-standard or even industry-standard "types", e.g. "structures
*model" or
"piping model", and those are the types of the "business objects"
*inside the
PDM.  Company document naming conventions may focus on "document
*type".  E.g.
"Geometric-model, 12345-1" and "Type3-load-analysis, 12345-1" may be
*unique
names for different DocumentMasters, whereas "DocumentMaster, 12345-1"
*doesn't
name anything. But "PartMaster, 12345-1" does, because "Part(Master)",
"Geometry-model" and "Type3-load-analysis" are the "business objects".
*Recommendation: not clear.  This might work for DocumentMaster, but
*it creates
problems for DocumentRevision and DocumentIteration.  (There is a
*related
"profiles" issue for PDME v2.)