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: RE: [plcs-dex] Ballot comemnt about state


Title: Message

The response is still to change the module..

 

So the question is why do we need sets?

 

Looking at the model of State definition, how can a “State_transition” result in multiple states?

 

 

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

-----Original Message-----
From:
Magne.Valen-Sendstad@dnv.com [mailto:Magne.Valen-Sendstad@dnv.com]
Sent: 28 October 2004 09:20
To: rob.bodington@eurostep.com; david.price@eurostep.com;
plcs-dex@lists.oasis-open.org; Albert.Leyson@dnvps.com
Subject: RE: [plcs-dex] Ballot comemnt about state

 

I also agree.

 

Magne

 


From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 28. oktober 2004 09:46
To: 'David Price'; plcs-dex@lists.oasis-open.org; Leyson, Albert T.; Valen-Sendstad, Magne
Subject: RE: [plcs-dex] Ballot comemnt about state

 

I agree.

I am minded to reject this ballot comment.

The module reflects what is in Part 56. Part 56 is an IS standard.  We recommend that they raise a SEDS against the IR.

 

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

-----Original Message-----
From: David Price [mailto:david.price@eurostep.com]
Sent: 27 October 2004 16:37
To: plcs-dex@lists.oasis-open.org; 'Albert T. Leyson'; 'Magne Valen-Sendstad'
Subject: RE: [plcs-dex] Ballot comemnt about state

 

Assuming there is a business requirement for sets of state_definition, you cannot simply use composition_of_state_definition and meet the requirement, it's not the same thing as a generic a grouping mechanism to produce sets of state_definition.

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 27 October 2004 09:07
To: plcs-dex@lists.oasis-open.org; Albert T. Leyson; Magne Valen-Sendstad
Subject: [plcs-dex] Ballot comemnt about state

The following ballot comment was made against the state modules.

I am not sure that it was discussed in Seattle.

What do people think?

Should the state_transition subtypes be able to relate sets of state_definitions?

 

If this is a PLCS requirement, then I propose that we reject the comment.

 

 

Ballot comment DE-46, DE-45

The state_relationship attributes related and relating are SETs of states. This is very unusual in the overall STEP modeling (see also 10303-41 E.3 Relationship template: object_relationship). The semantic of subtypes of state_relationship becomes by this very questionable. Grouping of states can always be achieved by composition_of_state. We have to avoid redundant mechanisms to achieve things.(6) Proposal: Change attributes related and relating to be of type state (not SET of state).

 

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

 


**************************************************************
Neither the confidentiality nor the integrity of this message can be guaranteed following transmission on the Internet.
All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of computer viruses.
DNV acknowledges that SPAM email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted. DNV has disabled "out of office" replies to the Internet
**************************************************************



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