See also: IRC log
<trackbot> Date: 06 January 2011
<webr3> apologies/regrets, I'm going to have to miss todays meeting as I've just been called in to the kids school for a meeting in 15 mins
<scribe> scribenick: Benjamin
manu: let's start. Any updates, changes to agenda?
<manu> http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Jan/0001.html
manu: it covers January, February
and March
... Shane aggreed to handle the last call comments
... do we want to speak up before sending responses?
ivan: Shane should not be pushed with technical issues.
manu1: I created issues for all most incomming comments
<manu> http://www.w3.org/2010/02/rdfa/track/products/8
ShaneM: Some comments are more related to XHTML or HTML. I'll redirect these.
manu1: Next plan is to get the RDFa API and RDF API document into better shape.
<markbirbeck> belated apologies, I'm afraid.
<markbirbeck> can't make the call...sorry.
Manu1: In March we hope to have
first implementations of the RDFa API
... In March try to move to Porposed Recommendations for
current Working Drafts
ivan: let's talk about the
Primer
... what about the chartered optional cookbook?
... the cookbok should include RDFa API content. Therefore the
deadline should be later.
<tinkster> I started gathering some potential examples for the cookbook on the WG wiki.
ivan: maybe we could collect code
snippets from our discussion on a wiki page
... Toby began to play with an ATOM host laguage for RDFa
... we should publish that as anote
<tinkster> http://www.w3.org/2010/02/rdfa/wiki/Cookbook/Examples
<tinkster> http://www.w3.org/2010/02/rdfa/wiki/Atom_plus_RDFa
manu1: let's discuss it on the mailing list
<manu> http://www.w3.org/2010/02/rdfa/sources/rdf-api/
<manu> http://www.w3.org/2010/02/rdfa/sources/rdfa-api/
manu1: Is everyone OK with the current directions of these documents?
benjamin: i am ok, want to look deeper into the RDF API
Steven: OK
<manu> http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Dec/0054.html
manu1: toby was working on this
<manu> http://buzzword.org.uk/2010/xhtml-vocab-20101110.xhtml
manu: good you give an overview Toby?
tinkster: update is on mapping the XHTML vocabulary with other vocabluaries like Dublin Core
manu: This is a good thing to
do.
... Any concerns about this?
ivan: I have some comments.
... Many changes relate to core level rather than XHTML.
... We have to have a well documented process about how a
prefix gets into the profile
<Zakim> manu, you wanted to discuss core vs. xhtml profiles
ivan: It's tricky to add or not add vocabularies like Dublin Core, Foaf , SIOC or Google's.
manu: RDFa core is intended to cover abstract vocabularies
ivan: I disagree
ShaneM: The RDFa core does not concern about any other document formats
ivan: RDFa Core works with any
XML language
... I should be able to use the RDF distiller for any RDFa data
containing any RDF vocabulary
manu: should we add the document conformance into the RDFa Core document?
ShaneM: We could add a section
about XML conformance.
... Ivan you use case is a real use case. I have to think about
this issue. How about testing? Do we have a core test
suite?
ivan: For a given set of
vocabularies (SIOC, FOAF, ...) we should be able to use them
without a profile.
... An XHTML document should have two profiles, the default
profile and its own profile.
<tinkster> chances are you'd hardcode both.
ShaneM: We should not have two profiles
<ShaneM> define an XML+RDFa host language
<tinkster> I use media type.
ivan: How does a processor identify the host language?
<Zakim> manu, you wanted to discuss checking the vocabulary profile
<ShaneM> XHTML+RDFa says: XHTML+RDFa documents should be labeled with the Internet Media Type "application/xhtml+xml" as defined in [RFC3236]. For further information on using media types with XHTML Family markup languages, see the informative note [XHTML-MEDIA-TYPES].
manu: The HTML said that analysing the media type is not the right way to identify the host language
ivan: not all document formats have a doc type
<tinkster> HTML5 served as text/html can have xmlns="http://www.w3.org/1999/xhtml"
<Zakim> manu, you wanted to discuss selecting the default profile
manu: although you cannot count on it, as shown by Toby's example we should use the namespace to decide which profile to use
<ShaneM> I would prefer embedding rules for XML+RDFa in RDFa Core rather than a separate spec
manu: I don't know if we have a concensus about implementing the profile lookup for RDFa processors
<ShaneM> RDFa Core needs to have rules for discovery defined in section 4.1
ivan: We could add an XML profile section in the RDFA Core spec
manu: another XML spec is not much more work
ShaneM: We have to recharter when
publishing another specification
... I would add it into the conformance section
<ShaneM> We need to add these as specific last call issues so we can address them
<tinkster> There is a difference in terms of constructing the DOM from the byte stream.
ShaneM: A conformance should use
information form the higher level protocol to determine the
document format
... is it OK that I fix comments I absolutely OK with.
The group agreed.
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/mimetpye/media type/ Found ScribeNick: Benjamin Inferring Scribes: Benjamin Default Present: +1.540.961.aaaa, manu, Steven, Ivan, +63.12.057.5aabb, Benjamin, ShaneM, +44.785.583.aacc, tinkster Present: Ivan MarkB Steven Toby Nathan Manu Benjamin Regrets: Nathan Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Jan/0029.html Found Date: 06 Jan 2011 Guessing minutes URL: http://www.w3.org/2011/01/06-rdfa-minutes.html People with action items:[End of scribe.perl diagnostic output]