See also: IRC log
<shadi> http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20080526
SAZ: Changes from telecon on 05/21 have been
completed and are in latest editor's draft
... JK sent more comments and fixes are in place
... will clean up references and history sections
... work on 1) status of document and 2) are we willing to publish as is?
... any pubilcation show-stoppers?
<shadi> ACTION: SAZ remove "namespace" from table 2 (these are not namespaces) [recorded in http://www.w3.org/2008/05/28-er-minutes.html#action01]
scribe: note that we do not have 2/3 of group
present
... follow-up with CI and CV for any last-minute comments
<shadi> RESOLUTION: go ahead with publishing HTTP Vocabulary in RDF
SAZ: What are we looking for from public
feedback and status?
... how these documents relate to POWDR
... feedback from other semantic web groups
CV: no ojbections to publication
SAZ: in particular, how schema performs and is
evaluated by other semantic web groups and technologies
... Mobile Web group also interested in serialization of HTTP
... question for Mobile Web is how our XML representation would "play" with
their representation
<shadi> http://www.w3.org/WAI/ER/Content/WD-Content-in-RDF-20080327
SAZ: very well-written; many comments already
incorporated
... abstract too brief
definitely
scribe: merge section 1.3 use cases into itnroduction
Quick question - why is XMLContent not a sublcass of TextContent?
JK: separate classes bc they have different properties; e.g. XmlContent does not have chars but might be representation of in-memory DOM
ok - just curious from a new-commers perspective
JK: TextContent could be subclass of Base64Content since text could be represented that way
got it.
CV: too brief and possibly redundant
... content in RDF is a complementary document to Http in RDF so don't want
to spend too much time on it
no
SAZ: keep in mind that this a distinct
publication and needs a context
... people could randomly land on the document and abstract should spell out
relationships and context
agree - especially spelling out the rleationships to EARL and Http in RDF
SAZ: part of a suite
... mimick format of Http in RDF
third bullet says, "http://www.w3.org/WAI/ER/Content/WD-Content-in-RDF-20080327
SAZ: can we have a provisional relation to publish contingent upon discussion of abstract on mailing list?
third bullet implicitly refers to EARL - might be a good palce to actually repeat or reiterate the relationship once abstract/intro is redone
under use cases
<shadi> http://www.w3.org/WAI/intro/earl.php
SAZ: WAI web site lists all publications and
relationships betwen them
... who is each doc for, what is it used for, etc.
... is it worth pointing back to this URL
... to provide an overview for first-time readers
given our time-frame, +1 for working it out on list
<shadi> RESOLUTION: go ahead with publishing Representing Content in RDF, pending changes to the abstract and introduction sections
<shadi> ACTION: CV to provide an updated abstract and introduction section for Representing Content in RDF document [recorded in http://www.w3.org/2008/05/28-er-minutes.html#action02]
SAZ: publication of charter must occur in June
so little time left
... time line needs adjustment; far too agressive
... on the other hand, need to push as far as possible to get EARL out
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2008May/0006
SAZ: heading is missing bc missing in W3C-wide template
MS: test description language part of charter for a potential deliverable?
SAZ: need to recruit members and otehr
development/test organizations for feedback, requirements, and support
... part of TCDL is in Bentoweb project
CV: +1 for committing resources to effort
JK: +1
SAZ: believe CI was also interested so
unanimity in effort
... how does it look in teh charter?
... proposed an analysis and requirements document as a deliverable
... once completed, we can recharter with more specific deliverables
<JohannesK> RDFa test case descriptions: <http://www.w3.org/2006/07/SWD/RDFa/testsuite/xhtml1-testcases/rdfa-xhtml1-test-manifest.rdf>
SAZ: workging group note
... in parallel with completion of EARL, consider a reorientation of the
group
... test description languages
... how does EARL and supplementary docs fit into toher W3C work - RDFA,
POWDER, Content Transformation, Mobile web
... focus deliverable that describs how EARL fits into these other efforts
<EtnaRosso> hi all, hi shadi
<EtnaRosso> Is a meeting in progress here?
<shadi> yes
<CarlosV> Christophe's analysis: http://bentoweb.org/html/BenToWeb_D4.1.html (Test Suites' State of the Art and Quality Assurance Methods for W3C Recommendations)
<CarlosV> Date: 28 February 2005 (a little bit old)
<EtnaRosso> see you
SAZ: no meeting Jun 4