How does PSL compare to other process modeling languages (e.g., IDEF0)?
PSL’s primary role is not envisioned to be a process modeling language, see question 4. It can be used as an interchange language which would allow manufacturing applications to exchange discrete process data. For example, an IDEF3-based application could use PSL to exchange process models with a Petri net-based application, in the same way that STEP can be used to exchange product models among CAD systems. It can also be used to define the meaning of languages like IDEF3 and Petri Nets. This is due to its unique its underlying, formal ontology of process execution, see question 4. All processes concepts in PSL are formally defined, using the Common Logic Interchange Format (CLIF), To eliminate the ambiguity usually encountered when exchanging information among disparate applications. This ontology provides the backbone that enables and ensures correct translations. PSL can be thought of an ontology for the concepts of process execution.
Related Questions
- How does XAML relate to business process modeling languages (ebXML business process, BPML)?
- How does XAML relate to business process modeling languages (ebXML business process, BPML)?
- Can I use ParaMagic with UML, UPDM (DoDAF/MoDAF), or business process modeling languages?
- Can I use ParaMagic with UML, UPDM (DoDAF/MoDAF), or business process modeling languages?
- How does PSL compare to other process modeling languages (e.g., IDEF0)?
- How does AMPL compare to other modeling languages and systems?