OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-dex message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Classification of View_definition_context


Hi

I have had a look at Capability (C002):— representing_parts

It talks about View_definition_context

However it implies that we should use strings for specifying the application_domain and life_cycle stage.

E.g.

 

#230=VIEW_DEFINITION_CONTEXT('product life cycle support', 'design', 'part definition');
 
I think that it would be better to use reference data. In other words create OWL sub classes of View_definition_context   – one for Application_domain and one for Life_cycle_stage as shown in the screenshot below.
I have also included the classes from AP214 and the PDM Schema. Apart from the obvious one (Product_life_cycle_support)
 
In the various pilots – what values have people used for these attributes?
Can we standardize on them?
 
It also raises a wider question. Where we have an EXPRESS entity which has a mandatory string attribute, e.g.
ENTITY View_definition_context;
  application_domain : STRING;
  life_cycle_stage : STRING;
  description : OPTIONAL STRING;
END_ENTITY;
 
And we use reference data. What String value should we use?
Should we set it to ‘’ or perhaps the name of the class?
 
If we use the name of the class AND classification then we will be compatible with other STEP parts (albeit at an ARM level)
 

 

 

 

 

Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Web Page:
http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]