Handle-Body pattern
E679868
The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Handle-Body pattern canonical | 1 |
| Handle/Body pattern | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7665299 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Handle-Body pattern Context triple: [Bridge, alsoKnownAs, Handle-Body pattern]
-
A.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
B.
"Apprenticeship Patterns"
"Apprenticeship Patterns" is a software craftsmanship book that offers practical guidance and patterns for developers to grow their skills through apprenticeship-style learning and deliberate practice.
-
C.
Chain of Responsibility
Chain of Responsibility is a behavioral design pattern that decouples senders and receivers by passing a request along a chain of potential handlers until one of them processes it.
-
D.
NeXTSTEP Workspace Manager for attachment handling
NeXTSTEP Workspace Manager for attachment handling is the NeXTSTEP desktop file and application manager component responsible for managing and interacting with file-based email attachments in the NeXT environment.
-
E.
Component Object Model
Component Object Model (COM) is a Microsoft software architecture and binary-interface standard that enables interprocess communication and reusable software components across different programming languages.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Handle-Body pattern Target entity description: The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
-
A.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
B.
"Apprenticeship Patterns"
"Apprenticeship Patterns" is a software craftsmanship book that offers practical guidance and patterns for developers to grow their skills through apprenticeship-style learning and deliberate practice.
-
C.
Chain of Responsibility
Chain of Responsibility is a behavioral design pattern that decouples senders and receivers by passing a request along a chain of potential handlers until one of them processes it.
-
D.
NeXTSTEP Workspace Manager for attachment handling
NeXTSTEP Workspace Manager for attachment handling is the NeXTSTEP desktop file and application manager component responsible for managing and interacting with file-based email attachments in the NeXT environment.
-
E.
Component Object Model
Component Object Model (COM) is a Microsoft software architecture and binary-interface standard that enables interprocess communication and reusable software components across different programming languages.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
object-oriented design pattern
ⓘ
software design pattern ⓘ |
| addressesConcern |
binary compatibility across library versions
ⓘ
compile-time coupling ⓘ information hiding ⓘ |
| canUseMechanism |
copy-on-write semantics
ⓘ
indirection via pointer or reference ⓘ reference counting for shared bodies ⓘ |
| enables |
changing implementation at runtime in some designs
ⓘ
reducing compilation dependencies ⓘ stable public API ⓘ |
| hasAlternativeName |
Cheshire Cat pattern
ⓘ
linked to:
The Cheshire Cat
Envelope-Letter pattern ⓘ Handle/Body idiom ⓘ Handle/Body pattern ⓘ
linked to:
Handle-Body pattern
|
| hasComponent |
body
ⓘ
handle ⓘ |
| isCategoryOf |
encapsulation pattern
ⓘ
interface-implementation separation pattern ⓘ |
| isSimilarTo |
Bridge pattern
ⓘ
Pimpl idiom ⓘ |
| isUsedIn |
C++
ⓘ
object-oriented languages ⓘ |
| relatedConcept |
encapsulation principle
ⓘ
interface segregation ⓘ opaque pointer ⓘ |
| separates |
internal implementation
ⓘ
internal state ⓘ public interface ⓘ |
| supports |
binary compatibility
ⓘ
easier maintenance ⓘ encapsulation ⓘ evolution of implementation without changing interface ⓘ flexibility ⓘ implementation hiding ⓘ |
| tradeOff |
adds level of indirection
ⓘ
increases implementation complexity ⓘ may introduce runtime overhead ⓘ |
| typicalBodyRole |
implements actual behavior
ⓘ
is hidden from clients ⓘ stores internal state ⓘ |
| typicalHandleRole |
exposes public methods
ⓘ
forwards calls to body ⓘ manages lifetime of body ⓘ |
| usedFor |
allowing ABI-stable libraries
ⓘ
hiding private data members ⓘ reducing header file exposure in C++ ⓘ supporting plugin-like replaceable implementations ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Handle-Body pattern Description of subject: The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Handle-Body pattern