R6RS I/O system
E571518
The R6RS I/O system is the standardized input/output framework defined by the Revised⁶ Report on the Algorithmic Language Scheme, providing a rich, port-based model for text and binary data handling.
All labels observed (2)
| Label | Occurrences |
|---|---|
| R6RS I/O system canonical | 1 |
| R6RS port I/O system | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6145057 — 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: R6RS I/O system Context triple: [Chez Scheme, supportsFeature, R6RS I/O system]
-
A.
R7RS (small) (partial)
R7RS (small) (partial) is a subset of the Revised⁷ Report on the Algorithmic Language Scheme standard that defines a core, lightweight version of the Scheme programming language.
-
B.
R4RS
R4RS is the fourth revised report on the Scheme programming language standard, defining its core syntax, semantics, and standard procedures.
-
C.
Scheme R5RS
Scheme R5RS is the fifth revised report of the Scheme programming language standard, defining its core syntax, semantics, and standard libraries.
-
D.
MIT Scheme
MIT Scheme is a long-standing, feature-rich implementation of the Scheme programming language developed at the Massachusetts Institute of Technology, often used for teaching and research in computer science.
-
E.
PLT Scheme
PLT Scheme is the original name of the programming language and environment that later evolved into Racket, known for its powerful support of functional and language-oriented programming.
- 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: R6RS I/O system Target entity description: The R6RS I/O system is the standardized input/output framework defined by the Revised⁶ Report on the Algorithmic Language Scheme, providing a rich, port-based model for text and binary data handling.
-
A.
R7RS (small) (partial)
R7RS (small) (partial) is a subset of the Revised⁷ Report on the Algorithmic Language Scheme standard that defines a core, lightweight version of the Scheme programming language.
-
B.
R4RS
R4RS is the fourth revised report on the Scheme programming language standard, defining its core syntax, semantics, and standard procedures.
-
C.
Scheme R5RS
Scheme R5RS is the fifth revised report of the Scheme programming language standard, defining its core syntax, semantics, and standard libraries.
-
D.
MIT Scheme
MIT Scheme is a long-standing, feature-rich implementation of the Scheme programming language developed at the Massachusetts Institute of Technology, often used for teaching and research in computer science.
-
E.
PLT Scheme
PLT Scheme is the original name of the programming language and environment that later evolved into Racket, known for its powerful support of functional and language-oriented programming.
- F. None of above. chosen
Statements (77)
| Predicate | Object |
|---|---|
| instanceOf |
R6RS specification component
ⓘ
Scheme language feature ⓘ input/output system ⓘ |
| alsoKnownAs |
R6RS port I/O system
ⓘ
linked to:
R6RS I/O system
|
| basedOn | port model ⓘ |
| definedIn | Revised⁶ Report on the Algorithmic Language Scheme ⓘ |
| designedFor | R6RS-compliant Scheme implementations ⓘ |
| hasFeature |
configurable character encodings
ⓘ
custom user-defined ports ⓘ exception-based I/O error reporting ⓘ line-buffered output ⓘ port positioning operations ⓘ separate binary and textual ports ⓘ |
| hasGoal | to provide a rich, standardized I/O framework for Scheme ⓘ |
| improvesOn |
binary data handling
ⓘ
character encoding support ⓘ error handling in I/O ⓘ port abstraction flexibility ⓘ |
| introducedIn | R6RS ⓘ |
| partOf |
R6RS standard library
ⓘ
linked to:
R6RS
|
| providesProcedure |
call-with-input-file
ⓘ
call-with-output-file ⓘ close-port ⓘ eof-object ⓘ eof-object? ⓘ flush-output-port ⓘ get-bytevector-n ⓘ get-bytevector-n!. ⓘ get-char ⓘ get-line ⓘ get-string-all ⓘ lookahead-char ⓘ make-custom-binary-input-port ⓘ make-custom-binary-output-port ⓘ make-custom-textual-input-port ⓘ make-custom-textual-output-port ⓘ make-transcoder ⓘ native-transcoder ⓘ open-bytevector-input-port ⓘ open-bytevector-output-port ⓘ open-file-input-port ⓘ open-file-input/output-port ⓘ open-file-output-port ⓘ open-string-input-port ⓘ open-string-output-port ⓘ port-has-port-position? ⓘ port-has-set-port-position!? ⓘ port-position ⓘ put-bytevector ⓘ put-char ⓘ put-string ⓘ set-port-position! ⓘ transcoded-port ⓘ with-input-from-file ⓘ with-output-to-file ⓘ |
| replaces | R5RS I/O model ⓘ |
| supports |
binary I/O
ⓘ
binary ports ⓘ blocking I/O ⓘ buffered I/O ⓘ bytevector I/O ⓘ custom ports ⓘ end-of-file detection ⓘ exception-based error reporting ⓘ file I/O ⓘ lookahead operations ⓘ positioning in ports ⓘ string ports ⓘ text I/O ⓘ textual ports ⓘ transcoded text I/O ⓘ unbuffered I/O ⓘ |
| usesConcept |
binary blocks
ⓘ
bytevectors ⓘ conditions ⓘ ports ⓘ transcoders ⓘ |
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: R6RS I/O system Description of subject: The R6RS I/O system is the standardized input/output framework defined by the Revised⁶ Report on the Algorithmic Language Scheme, providing a rich, port-based model for text and binary data handling.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: R6RS I/O system