RFC 4918
E699617
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4918 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T7936167 — 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.
Target entity: RFC 4918 Context triple: [WebDAV, definedInRFC, RFC 4918]
-
A.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
B.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
C.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
D.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
E.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 4918 Target entity description: RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
-
A.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
B.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
C.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
D.
RFC 5849
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ WebDAV specification ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| definesConcept |
locking of resources
ⓘ
multi-resource operations ⓘ properties on HTTP resources ⓘ resource collections ⓘ |
| definesExtensionOf |
HTTP
NERFINISHED
ⓘ
Hypertext Transfer Protocol NERFINISHED ⓘ |
| definesHeader |
Depth
ⓘ
Destination ⓘ If ⓘ Lock-Token ⓘ Overwrite ⓘ Timeout ⓘ |
| definesMethod |
COPY
ⓘ
LOCK ⓘ MKCOL ⓘ MOVE ⓘ PROPFIND ⓘ PROPPATCH ⓘ UNLOCK ⓘ |
| definesStatusCode | 207 Multi-Status ⓘ |
| definesURINamespace | DAV: NERFINISHED ⓘ |
| focusesOn |
collaborative web content authoring
ⓘ
file management over HTTP ⓘ |
| intendedUse |
collaborative authoring
ⓘ
remote web content management ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2518 NERFINISHED ⓘ |
| partOf | WebDAV protocol suite NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
HTTP/1.1
ⓘ
RFC 3744 NERFINISHED ⓘ WebDAV Access Control Protocol NERFINISHED ⓘ |
| standardizes |
Web Distributed Authoring and Versioning
NERFINISHED
ⓘ
WebDAV NERFINISHED ⓘ |
| status | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) NERFINISHED ⓘ |
| updatesProtocol | HTTP/1.1 for authoring extensions NERFINISHED ⓘ |
| useCase |
content management systems
ⓘ
groupware applications ⓘ networked file systems over HTTP ⓘ |
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.
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.
Subject: RFC 4918 Description of subject: RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.