JSON Working Group
E754583
The JSON Working Group is an IETF standards body responsible for developing and maintaining the formal specifications for the JSON data interchange format.
All labels observed (1)
| Label | Occurrences |
|---|---|
| JSON Working Group canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8755943 — 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: JSON Working Group Context triple: [RFC 8259, workingGroup, JSON Working Group]
-
A.
W3C JSON-LD Working Group
The W3C JSON-LD Working Group is a World Wide Web Consortium group responsible for developing and maintaining the JSON-LD standard for linking data using JSON on the web.
-
B.
JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
-
C.
W3C JSON for Linking Data Community Group
The W3C JSON for Linking Data Community Group is a W3C community initiative focused on developing and promoting JSON-LD as a standard way to represent and link structured data on the web.
-
D.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- 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: JSON Working Group Target entity description: The JSON Working Group is an IETF standards body responsible for developing and maintaining the formal specifications for the JSON data interchange format.
-
A.
W3C JSON-LD Working Group
The W3C JSON-LD Working Group is a World Wide Web Consortium group responsible for developing and maintaining the JSON-LD standard for linking data using JSON on the web.
-
B.
JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
-
C.
W3C JSON for Linking Data Community Group
The W3C JSON for Linking Data Community Group is a W3C community initiative focused on developing and promoting JSON-LD as a standard way to represent and link structured data on the web.
-
D.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards body ⓘ |
| abbreviation | json NERFINISHED ⓘ |
| area | Applications and Real-Time Area NERFINISHED ⓘ |
| field |
Internet standards
ⓘ
application-layer protocols ⓘ data interchange formats ⓘ |
| goal |
ensure interoperability of JSON across platforms
ⓘ
provide a stable, well-defined JSON specification ⓘ |
| governedBy | IETF working group charter ⓘ |
| hasMailingList | [email protected] ⓘ |
| language | English ⓘ |
| meetsAt | IETF meetings ⓘ |
| oversees | errata for JSON RFCs ⓘ |
| parentOrganization | Internet Engineering Task Force NERFINISHED ⓘ |
| producedStandard |
RFC 7493
NERFINISHED
ⓘ
RFC 7493: The I-JSON Message Format NERFINISHED ⓘ RFC 8259 NERFINISHED ⓘ RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format NERFINISHED ⓘ |
| relatedStandard | ECMA-404 NERFINISHED ⓘ |
| relatedTechnology |
JavaScript
NERFINISHED
ⓘ
RESTful APIs ⓘ web services ⓘ |
| responsibleFor |
JSON data interchange format
ⓘ
development of JSON specifications ⓘ maintenance of JSON specifications ⓘ |
| scope |
best practices for JSON use
ⓘ
core JSON format ⓘ interoperability of JSON implementations ⓘ |
| standardCategory | Internet Standard track ⓘ |
| standardizes |
JSON array representation
ⓘ
JSON data model ⓘ JSON grammar ⓘ JSON number representation ⓘ JSON object representation ⓘ JSON string representation ⓘ JSON text format ⓘ JSON true/false/null literals ⓘ JavaScript Object Notation NERFINISHED ⓘ |
| status | IETF working group NERFINISHED ⓘ |
| topic |
Internet protocols
ⓘ
serialization formats ⓘ |
| usesProcess | IETF consensus process ⓘ |
| website | https://datatracker.ietf.org/wg/json ⓘ |
| workProductType |
Internet-Drafts
NERFINISHED
ⓘ
Proposed Standard RFCs ⓘ |
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: JSON Working Group Description of subject: The JSON Working Group is an IETF standards body responsible for developing and maintaining the formal specifications for the JSON data interchange format.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.