See also: IRC log
saz: merging earl:Content and http:Content?
[agreement]
RESOLUTION: merge earl:Content and http:Content classes
saz: separating http:Content from HTTP-in-RDF?
[agreement]
RESOLUTION: separate http:Content from HTTP-in-RDF into a different namespace and different document
saz: who does the work?
http://www.w3.org/WAI/ER/HTTP/WD-RFC822-in-RDF-20060502
http://lists.w3.org/Archives/Public/public-wai-ert/2007Aug/0003.html
cv: has nothing to do with RFC822 -just Content, Base64Content, TextContent, XMLContent, etc
http:Content
http:Base64Content rdfs:subClassOf http:Content
|- 1 http:bytes
http:bytes (rdfs:Literal, typed: xsd:base64Binary)
http:TextContent rdfs:subClassOf http:Content
|- 1 http:chars
http:chars (rdfs:Literal)
http:XMLContent rdfs:subClassOf http:Content
|- 0..1 http:xmlLeadingMisc
|- 0..1 http:docTypeDecl
|- 1 http:xmlRest
http:xmlLeadingMisc (rdfs:XMLLiteral)
http:docTypeDecl (http:DocTypeDecl)
http:xmlRest (rdfs:XMLLiteral)
http:DocTypeDecl
|- 1 http:dtdName
|- 0..1 http:publicId
|- 0..1 http:systemId
|- 0..1 http:internalSubset
http:dtdName (rdfs:Literal)
http:publicId (rdfs:Literal)
http:systemId (rdfs:Literal, typed: xsd:anyURI)
http:internalSubset (rdfs:Literal)
saz: anything else besides these classes and properties as part of the new document?
RESOLUTION: rfc822:Message (includes message headers and message body) is out of scope
<CarlosV> [RFC2616] Fielding R, Gettys J, Mogul J, Frystik H, Masinter L, Berners-Lee T (eds) (1999). Hypertext Transfer Protocol – HTTP/1.1. Request for Comments: 2616. IETF. Available at: http://www.ietf.org/rfc/rfc2616.txt
saz: need to clarify how this relates to the
TAG definitions (especially for URI)
... for example, "while URI define resources by the conceptual properties,
the Content Class focuses on the presentation instance" or such
... something to clarify the relationship between both pieces
cv: as testers we are only interested in the presentation of URIs
<scribe> ACTION: CarlosV talk with Johannes and Reinhard on working on the new "Content Class document" [recorded in http://www.w3.org/2007/09/05-er-minutes.html#action01]
saz: we should think about an appropriate name
saz: replacing earl:inferred with an aggregation logic
rr: semi-automatic is misleading in the current definition need mixed
cv: combination of 99 automatic and 1 manual test to become manual is also not logic
http://lists.w3.org/Archives/Public/public-wai-ert/2007Jul/0019.html
- earl:semiAutomatic
Where the test was partially carried out by the software tool, but where
human input or judgment was still required to decide or help decide the
outcome of the test.
for discussion:
#1. if all sub-tests were carried out in the same test mode, then the
test mode of the combined test is same.
#2. if the test mode of any of the sub-tests is "undisclosed", then the
test mode of the combined test is also "undisclosed".
#3. for all other test mode combinations of sub-tests, the test mode of
the combined test is "semi-automatic".
http://lists.w3.org/Archives/Public/public-wai-ert/2007Sep/0008.html
cv: would prefer a mixed mode
saz: as a value or modifier?
rr: you move the statement from one place to the other, why is it better
cv: agree
... inferred implies some logic but "aggregated" is more neutral