See also: IRC log
http://www.w3.org/2007/09/20-rdfa-minutes.html#ActionSummary
<scribe> ACTION: Manu draft some partitioning language that is technology-neutral [recorded in http://www.w3.org/2007/09/20-rdfa-minutes.html#action14] [DONE]
Manu: Is it worked in?
Mark: Yes, sort of
<scribe> ACTION: Ben to look into Science Commons use case [recorded in http://www.w3.org/2006/12/11-htmltf-minutes.html#action04] [PENDING]
<scribe> ACTION: Ben, Mark, Elias, and other implementors to add xml:lang support [recorded in http://www.w3.org/2007/08/23-rdfa-minutes.html#action11] [PENDING]
<scribe> ACTION: Michael look for a more semantically correct predicate for tests 42-45 [recorded in http://www.w3.org/2007/09/06-rdfa-minutes.html#action14] [PENDING]
<scribe> ACTION: Michael make sure to confirm a design for checking that the ASK SPARQL queries evaluate (yes/no) [recorded in http://www.w3.org/2007/09/06-rdfa-minutes.html#action07] [PENDING]
<scribe> ACTION: Michael to create "Microformats done right -- unambiguous taxonomies via RDF" on the wiki [recorded in http://www.w3.org/2007/08/23-rdfa-minutes.html#action06] [PENDING]
Ben: I'm working through some issues this week, but we're making progress
http://www.w3.org/2006/07/SWD/wiki/AmsterdamAgenda
<scribe> ACTION: Ben to remind the WG reviewers about review for FtF [recorded in http://www.w3.org/2007/09/27-rdfa-minutes.html#action07]
Ben: Mark will lead the discussion, it will be Monday morning
<benadida> agenda for f2f: http://www.w3.org/2006/07/SWD/wiki/AmsterdamAgenda
Ben: I hope you will demo some stuff
... Shane, you are joining by phone?
Shane: My plan, but I need to see a schedule
Ben: Ralph, going?
Ralph: Not sure yet
Manu: Mark, beware of live demos
Steven: Yes, I had a similar problem yesterday at a talk
Ben: Please demo my clipboard if you have time
[Discussion of current uses of RDFa]
Ben: We need this information to show that there is progress
Mark: My implementation is coming on nicely
... the RDFa part needs to be modularised still
... so that people could pick it up separately
Ben: Is it a part of Sidewinder?
Mark: No, it is 3 or 4 javascript files
... in libXH
... as I call it
Ben: Can it manage the test cases?
Mark: Yep
Ben: We have Ivan's Distiller, up to date
... Elias's Pythion implementation, not up to date
... there is Operator
Manu: Not up to date yet
... Operator will be in Firefox 3, and then in Songbird
... so RDFa will be just there
Ben: My Javascript implementation is not yet up
to date
... the bookmarklet
... then RDFa Monkey, I don't know the state
<RalphS> RDFa monkey
Ben: Fabien's XSLT, it is up to date, modulo a whitespace issue
<RalphS> (RDFa monkey home page cites Elias' test files, not the more recent ones)
<scribe> ACTION: Ben to add implementations page to RDFa.info [recorded in http://www.w3.org/2007/09/27-rdfa-minutes.html#action08]
<benadida> implementations -> http://esw.w3.org/topic/RDFa#head-681001ee6c73e87bd692e29693b3904e462fd9f2
Ben: there are some other implementations, Java and Python
Manu: How about IE? I heard they are adding microformats
Shane: How about Chris Wilson?
Ben: Do you want to talk to him?
<scribe> ACTION: Shane to contact Chris Wilson [DONE] [DONE] [recorded in http://www.w3.org/2007/09/27-rdfa-minutes.html#action09]
<RalphS> list of some RDFa implementations
Ben: Deferred till next time
... Isee your message about href everywhere Shane
... we did resolve to accept that
Shane: Yes, and I have today fixed that
Ben: Should we update the editor's draft and tell the reviewers?
Ralph: It would be good
Shane: I made a couple of editorial fixes too
<scribe> ACTION: Shane to send a link to new editor's draft to Ben [recorded in http://www.w3.org/2007/09/27-rdfa-minutes.html#action10]
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Sep/0216
Ben: There is a problem that the XHTML namespace doesn't end with a hash or slash
Mark: In the section on unprefixed values, I
say that it uses the XHTML namespace with a hash on the end
... but we should move away from the idea that these are namespaces
... so we are not talking about changing the XHTML namespace, but defining
the prefix
... but there is a problem with overlap with the role attribute
... they are so close, they ought to use the same system
Shane: There can't be multiple default prefixes for CURIES
Ben: But rel can have a magic property using reserved words
Steven: I would be happy if we could avoid special rules and magic
Ben: I think it is a special case because of
backwards compatibility
... rel="foobar" is not even allowed
Mark: It is if you have a @profile
... so there are docs with a profile, with non-HTML rels
... and quite valid therefore
Ben: So the specific issue
... we do need a default prefix URL, alsoi that ends in a hash or slash
Steven: Why does it matter?
Mark: Because of round-tripping, which strictly
RDF doesn't support
... but is a sort of standard practice
... in one case we would have the concept of xhtmlnext, as opposed to
xhtml:next
... it is only convention
Ralph: I like the idea of Shane's to use Apache redirecting to redirect xhtmlnext to something else
Mark: Why do we care; we can add a hash without
a problem
... We can add the relations to their own subnamespace
... otherwise just straight to the XHTML namespace
<benadida> example http://creativecommons.org/ns#
Ben: That is the CC namesapce
<RalphS> Shane: XHTML already has things under xhtml/ so I would expect objections to the simple concatenation xhtmlnext
<benadida> /1999/xhtml/ns#
Mark: In the Modularization schemas we have 1999/xhtml/datatypes
<benadida> /1999/xhtml/vocab#
<benadida> /1999/xhtml/?#
Mark: so we could have 1999/xhtml/vocab# or something
Ben: I like the word vocab as being general
... anyone object?
Shane: Mostly harmless
<benadida> PROPOSE that we use 1999/xhtml/vocab# as the prefix for next, prev, etc...
Ben: Deciding about nofollow is another issue
Ralph: Second
Ben: Opposed?
Mark: We can't speak for the whole XHTML2 WG,
but I think it is the best option
... +1 to it
RESOLUTION: that we use 1999/xhtml/vocab# as the prefix for next, prev, etc..
<ShaneM> New draft of rdfa-syntax is at http://www.w3.org/MarkUp/2007/ED-rdfa-syntax-20070927/
Ben: This doesn't solve the issue of whether we
should special-case the the legacy rels
... we'll treat that another week
ADJOURN