[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] How to handle product category hierarchy in an exchange file?
IMHO I believe that we should not use product_category_hierarchy at all. If we want to represent a classification hierarchy of products then we should use reference data.
I also intend to raise a SEDS asking for the where rule on Part to be removed so that we do not have to use product_category. As we have said in Annex I of the AP239:
Classification_assignment provides the principal mechanism for associating classes with items. However, an additional mechanism is provided for products, that is Product_category. See the Product categorization and Product identification modules. Product_category is used to distinguish between the different subtypes of Product defined in this part of ISO 10303. Examples are: Part, Requirement and Document. This approach is used by other ISO 10303 Application Protocol parts. More specific types of products, such as Oil filter as a type of Part should be specified by means of Classification_assignment, thus allowing the use of a class library via External_class.
The spreadsheet has not been reviewed.
Regards ------------------------------------------- -----Original Message-----
All.
1. Can the spreadsheet located at dexlib/docs/…/PLCS_attribute_usage.xls be considered as approved? 2.
How to handle product category hierarchy in an exchange file? Does this mean that the <entity>.id shall be replaced by identification_assignment and the role of the entity is classified by classification_assignment? Regards
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]