Proposal for Http Request Headers in State
Problem: There is a need to annotate/encode Http headers into an annotation. How should hasState be represented?
Solutions: Ranging from simple strings that carry the headers to inline graphs and structured resources.
The first option is to have properties for each of the five Http headers (accept, user-agent, accept-charset, accept-language, accept-encoding) that are accepted by (RFC?). This option would be comparable to the oa:when property.
Option 2 is to have the headers defined like fragmentSelectors or svgSelectors. The rdf:type of oa:State would be for example oax:HttpRequestState. The rdf:value would include the headers and the corresponding values (Example 1a). Example 1b shows how the http information would look formatted as a ContentAsText property like an svgSelector.
Option 2 pros-
- Most of the solution is already implemented within the core/extension spec
Option 2 cons-
- (can't negotiate - Tom's comment)