Cited by 141Business Process Modeling and AnalysisManufacturing Process and OptimizationDigital Transformation in Industry

The Process Specification Language (PSL) overview and version 1.0 specification

Open access
Schlenoff, Craig, Gruninger, Michael, Tissot, Florence, Valois, John, Lee, Jintae·2000

Abstract

This document describes Version 1.0 of the Process Specification Language (PSL). PSLis an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools.These tools would interoperate by translating between their native format and PSL.Then, any system would be able to automatically exchange process information with any other system via PSL.This document focuses specifically on PSL's rationale, semantic architecture, informal documentation, and the vision of how one would translate in and out of PSL.expanded to incorporate the concepts introduced in various manufacturing software applications when PSL was used to exchange process information among these packages.As more software applications become "PSL-compliant," PSL will be continually expanded to ensure that ALL process-related concepts are capable of being represented within the language.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.6028/nist.ir.6459

Cites

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • halSynteny implements a DAG-based algorithm for identification of synteny blocks directly from HAL alignment and reporting synteny blocks in PSL format.

    “Here we present halSynteny, a tool that implements a DAG-based algorithm for identification of synteny blocks directly from HAL alignment and reporting synteny blocks in PSL format [19].”

    From halSynteny: a fast, easy-to-use conserved synteny block construction method for multiple whole-genome alignments (2020) · cites this paper as [19]

    The cited paper’s Section 1.3 identifies PSL as a language for exchanging manufacturing process specifications, not a format for reporting genomic alignments. Its Appendix D defines the syntax of that process language. The citation therefore does not substantiate the sentence’s reference to synteny blocks in “PSL format”; the paper also says nothing about halSynteny or its algorithm. (LLM, conf=0.87)

    Checked by a reasoning model — may be wrong.

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

No references could be resolved yet.

Research works printed but not linked: 10

  1. Catron, B., Ray, S., ALPS: A Language for Process Specification, Int. J. Computer Integrated Manufacturing, 1991, Vol. 4, No. 2, 105-113.
  2. Fox, M., et al, An Organization Ontology for Enterprise Modeling: Preliminary Concepts," Computers in Industry, 1996, Vol. 19, pp. 123-134.
  3. Uschold, M., et. al., 'The Enterprise Ontology," The Knowledge Engineering Review, Vol. 13(1), pp. 31-89, Special Issue on "Putting Ontologies to Use," (eds.
  4. Uschold, M. and Tate, A.), Cambridge University Press.
  5. Tate, A., "Roots of SPAR -Shared Planning and Activity Representation," The Knowledge Engineering Review, Vol. 13(1), pp. 121-128, Special Issue on "Putting Ontologies to Use" (eds.
  6. Lee, J., et al, "The PIF Process Interchange Format and Framework," The Knowledge Engineering Review, Vol. 13(1), pp. 91-120, Special Issue on "Putting Ontologies to Use" (eds.
  7. Uschold, M. and Tate, A.), Cambridge University Press.
  8. Uschold, M. and Gruninger M., Ontologies: Principles, Methods, and Applications, Knowledge Engineering Review, 1996, Vol. 11, pp. 96-137.
  9. Reiter, R., The frame problem in the situation calculus: a simple solution (sometimes) and a completeness result for goal regression. Artificial Intelligence and Mathematical Theory of Computation: Papers in Honor of John McCarthy, 1991, pages 418-440, Academic Press, San Diego.
  10. Smith, S J.J., at al.. Integrating Electrical and Mechanical Design and Process Planning, Proceedings of the IE IP Knowledge Intensive CAD Workshop, 1996, Camegie-Mellon University (CMU).

Cited by

Sorted by citations

Authors
Schlenoff, C., Gruninger, M., Tissot, F., Valois, J., & Lee, J.
Affiliations
  • National Institute of Standards and Technology (US)
  • Knowledge Based Systems (United States) (US)
Published
2000
OpenAlex
W4249203004
Cited by
141
References
0
Citations by year
2026: 5 · 2025: 4 · 2024: 4 · 2023: 2 · 2022: 1 · 2021: 3 · 2020: 7 · 2019: 4 · 2018: 4 · 2017: 4 · 2016: 3 · 2015: 2 · 2014: 4 · 2013: 1 · 2012: 9
Type
report
Language
en
Open access
Funders
National Institute of Standards and Technology
Topics
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Business Process Modeling and Analysis
  • Physical Sciences › Engineering › Industrial and Manufacturing Engineering › Manufacturing Process and Optimization
  • Physical Sciences › Engineering › Industrial and Manufacturing Engineering › Digital Transformation in Industry
Keywords
Process Specification Language, interchange format, process modeling, process planning, scheduling, workflow, business process reengineering, semantic architecture, data translation

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review