RFC 2295: Transparent Content Negotiation in HTTP
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 2295: Transparent Content Negotiation in HTTP
Summary
RFC 2295: Transparent Content Negotiation in HTTP is a Request for Comments[1].
Key Facts
- RFC 2295: Transparent Content Negotiation in HTTP's instance of is recorded as Transparent Content Negotiation in HTTP — instance of (P31): Request for Comments[2].
- RFC 2295: Transparent Content Negotiation in HTTP's publisher is recorded as Transparent Content Negotiation in HTTP — publisher (P123): Internet Engineering Task Force[3].
- RFC 2295: Transparent Content Negotiation in HTTP's DOI is recorded as 10.17487/RFC2295[4].
- RFC 2295: Transparent Content Negotiation in HTTP's language of work or name is recorded as Transparent Content Negotiation in HTTP — language of work or name (P407): English[5].
- RFC 2295: Transparent Content Negotiation in HTTP's publication date is recorded as +1998-03-01T00:00:00Z[6].
- RFC 2295: Transparent Content Negotiation in HTTP's RfC ID is recorded as 2295[7].
- RFC 2295: Transparent Content Negotiation in HTTP's work available at URL is recorded as https://tools.ietf.org/html/rfc2295[8].
- RFC 2295: Transparent Content Negotiation in HTTP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2295.txt[9].
- RFC 2295: Transparent Content Negotiation in HTTP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2295.txt[10].
- RFC 2295: Transparent Content Negotiation in HTTP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2295.txt.pdf[11].
- RFC 2295: Transparent Content Negotiation in HTTP's number of pages is recorded as {'unit': '1', 'amount': '+58'}[12].
- RFC 2295: Transparent Content Negotiation in HTTP's title is recorded as Transparent Content Negotiation in HTTP[13].
- RFC 2295: Transparent Content Negotiation in HTTP's author name string is recorded as K. Holtman[14].
- RFC 2295: Transparent Content Negotiation in HTTP's author name string is recorded as A. Mutz[15].
- RFC 2295: Transparent Content Negotiation in HTTP's DBLP publication ID is recorded as journals/rfc/rfc2295[16].
Body
Designation and Status
RFC 2295: Transparent Content Negotiation in HTTP's instance of is recorded as Transparent Content Negotiation in HTTP — instance of (P31): Request for Comments[2].