Correspondence Between Definitions and Procedures: A Reply to Stokes, Osnes, and Guevremont

dc.contributor.authorCatania, A. Charles
dc.contributor.authorShimoff, Eliot
dc.contributor.authorMatthews, Byron A.
dc.date.accessioned2024-08-27T20:38:34Z
dc.date.available2024-08-27T20:38:34Z
dc.date.issued1987
dc.description.abstractStokes, Osnes, and Guevremont's (1987) implicit definition of correspondence classes appears dose to ours (Matthews, Shimoff, & Catania, 1987). Their definition, however, is fundamentally procedural and thus may have to be modified as experimental methodologies are refined. The advantage of our contingency-space analysis is that it is independent of specific procedures and focuses attention on problems inherent in some procedural definitions. Specifically, a contingency-space analysis addresses the issue of distinguishing specific instances from classes and reminds us that correspondence can be identified as a class only on the basis of observing a population of opportunities for say/do sequences in which the subject sometimes does not say.
dc.description.urihttps://www.ncbi.nlm.nih.gov/pmc/articles/PMC1286080/
dc.format.extent4 pages
dc.genrejournal articles
dc.identifierdoi:10.13016/m2brzp-po38
dc.identifier.citationCatania, A. Charles, Eliot Shimoff, and Byron A. Matthews. “Correspondence Between Definitions and Procedures: A Reply to Stokes, Osnes, and Guevremont.” Journal of Applied Behavior Analysis 20, no. 4 (1987): 401–4. https://doi.org/10.1901/jaba.1987.20-401.
dc.identifier.urihttps://doi.org/10.1901%2Fjaba.1987.20-401
dc.identifier.urihttp://hdl.handle.net/11603/35887
dc.language.isoen_US
dc.publisherWiley
dc.relation.isAvailableAtThe University of Maryland, Baltimore County (UMBC)
dc.relation.ispartofUMBC Faculty Collection
dc.relation.ispartofUMBC Psychology Department
dc.subjectcontingency-space analysis
dc.subjectcorrespondence training
dc.subjectgeneralization
dc.subjectresponse classes
dc.subjectverbal behavior
dc.titleCorrespondence Between Definitions and Procedures: A Reply to Stokes, Osnes, and Guevremont
dc.typeText

Files