Sunday, December 14, 2014

Daily Tag 12/15/2014

  • "6.3.1 The state of a LDPR can have triples with any subject(s). The URL used to retrieve the representation of a LDPR need not be the subject of any of its triples. 6.3.2 The representation of a LDPC can include an arbitrary number of additional triples whose subjects are the members of the container, or that are from the representations of the members (if they have RDF representations). This allows an LDP server to provide clients with information about the members without the client having to do a GET on each member individually. 6.3.3 The state of a LDPR can have more than one triple with an rdf:type predicate. 7. HTTP Header Definitions 7.1 The Accept-Post Response Header Feature At Risk The LDP Working Group proposes incorporation of the features described in this section. The addition of Accept-Post in this specification is pending advancement of an IETF draft [Accept-Post] that would fully include it, based on the Accept-Patch header's design from [RFC5789]. Once LDP is in Candidate Recommendation status, the LDP WG will make an assessment based on the status at IETF working with the W3C Director. This specification introduces a new HTTP response header Accept-Post used to specify the document formats accepted by the server on HTTP POST requests. It is modelled after the Accept-Patch header defined in [RFC5789]. 7.1.1 The syntax for Accept-Post, using the ABNF syntax defined in Section 1.2 of [RFC7231], is: Accept-Post = "Accept-Post" ":" # media-range The Accept-Post header specifies a comma-separated list of media ranges (with optional parameters) as defined by [RFC7231], Section 5.3.2. The Accept-Post header, in effect, uses the same syntax as the HTTP Accept header minus the optional accept-params BNF production, since the latter does not apply to Accept-Post. 7.1.2 The Accept-Post HTTP header should appear in the OPTIONS response for any resource that supports the use of the POST method. The presence of the Accept-Post header in response to any method is an implicit indication that POST is allowed on the resource identified by the Request-URI. The presence of a specific document format in this header indicates that that specific format is allowed on POST requests to the resource identified by the Request-URI. 7.1.3 IANA Registration Template The Accept-Post response header must be added to the permanent registry (see [RFC3864]). Header field name: Accept-Post"

    tags: w3 ldp link data Platform

  • tags: Stanford philosophy

  • tags: advanced programming language

  • tags: private docker azure

Posted from Diigo. The rest of my favorite links are here.

Tuesday, December 2, 2014

Daily Tag 12/03/2014

Posted from Diigo. The rest of my favorite links are here.

Tuesday, November 4, 2014

Daily Tag 11/05/2014

Posted from Diigo. The rest of my favorite links are here.