W3C

- DRAFT -

RDFa Working Group Teleconference

25 Mar 2010

See also: IRC log

Attendees

Present
Jeff, Manu, Abhijit, Knud
Regrets
Chair
Manu Sporny
Scribe
Benjamin

Contents


<manu> trackbot, start meeting

<trackbot> Date: 25 March 2010

<Knud> hi

<Knud> better?

<Knud> zakim mute me

<Knud> oh, that's me?

<manu> ACTION: Shane to prepare RDFa Core 1.1 document for FPWD [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action01]

<trackbot> Created ACTION-16 - Prepare RDFa Core 1.1 document for FPWD [on Shane McCarron - due 2010-04-01].

<manu> ACTION: Jeff to prepare RDFa Cookbook document for FPWD for May 2010 [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action02]

<trackbot> Created ACTION-17 - Prepare RDFa Cookbook document for FPWD for May 2010 [on Jeffrey Sonstein - due 2010-04-01].

hi I am sorry for being so late

<manu> ACTION: Shane to prepare XHTML+RDFa 1.1 document for FPWD. [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action03]

<trackbot> Created ACTION-18 - Prepare XHTML+RDFa 1.1 document for FPWD. [on Shane McCarron - due 2010-04-01].

<scribe> scribenick: Benjamin

<manu> ACTION: Benjamin to prepare RDFa API document for FPWD [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action04]

<trackbot> Created ACTION-19 - Prepare RDFa API document for FPWD [on Benjamin Adrian - due 2010-04-01].

<manu> April 1st - Editors have a FPWD Editors Draft document published via

<manu> a W3C URL (though cvs.w3.org)

<manu> April 8th - Any Editors Draft corrections are made

<manu> April 15th - Notification to W3C Pubs to publish RDFa WG FPWDs

<manu> April 22nd - Slack time

Action Items

manu: create first drafts of FPWD drafts
... three documetns by April, 15

<jeffs> +1 on timeline & tasks

manu: any changes on the agenda?

<manu> http://doodle.com/uqe9pxru7eu8n7d8

manu: The proposals of the doodle call are going to be part of the RDFa specification

<jeffs> I can live with the external documents part, and I am very hesitant

manu: Toby and jeffs do not agree with having an external document
... it's more a hesitation than disagreement

<jeffs> expressed my concerns about having external document(s) and liking of namespace approach

manu: we discussed very much on this concern with having this external document. Let's see what the community responds.

<manu> http://www.w3.org/2010/02/rdfa/drafts/2010/ED-vocab-20100305/

manu: Ivan updated the document above
... a similar version is in the wiki

<jeffs> I see no consensus on the 'combination of prefixes and keywords into a single "list of mappings" concept' proposal

manu: we should keep prfixes and keywords in separate documents

@token proposal

manu: token proposal is not going into the rdfa 1.1 document

@prefix proposal

<manu> <div vocab="http://example.org/vocab#"><span property="foo">prop</span></div>

<manu> <> http://example.org/vocab#foo "prop" .

<Knud> vocab is good

<jeffs> vocab is simple and expressive

Shane: I really like vocab

manu: vocab is going to be in RDFa 1.1 spec

<jeffs> +1 to keeping sep until more discussion

manu: prefixes and keywords are kept separate

ShaneM: has no objections to keep them separate

<manu> RDFa 1.1 should have a mechanism to express mappings that does not depend on xmlns: (for example: @token, @vocab or @map)

manu: We haven't really talked about this

<manu> One option: prefix="foaf: http://xmns.com/.../" token="Person: http://xmlns.com/.../Person"

<manu> Second option: prefix="foaf: http://xmlns.com/.../" <--- prefixes can only be set, tokens are only set in RDFa Profile documents.

manu: explains options for defining prefixes and tokens

<manu> Third option: map="foaf: http://xmns.com/.../; Person: http://xmlns.com/.../Person;"

<jeffs> I do not think we have talked about this enough to do much of anything "on paper"

<jeffs> the previous stuff has an effect upon this issue

could you please summarize this for the scribe :)

scribe: Mapping mechanisms are not going into the core document

<ShaneM> /msg manu Characters in the "reserved" set are not reserved in all contexts. The set of characters actually reserved within any given URI component is defined by that component. In general, a character is reserved if the semantics of the URI changes if the character is replaced with its escaped US-ASCII encoding.

<ShaneM> oops

scribe: We have a tight schedule

<Knud> bye

Summary of Action Items

[NEW] ACTION: Benjamin to prepare RDFa API document for FPWD [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action04]
[NEW] ACTION: Jeff to prepare RDFa Cookbook document for FPWD for May 2010 [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action02]
[NEW] ACTION: Shane to prepare RDFa Core 1.1 document for FPWD [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action01]
[NEW] ACTION: Shane to prepare XHTML+RDFa 1.1 document for FPWD. [recorded in http://www.w3.org/2010/03/25-rdfa-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/03/25 14:43:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/jee/jeffs/
Succeeded: s/Topby/Toby/
Found ScribeNick: Benjamin
Inferring Scribes: Benjamin
Present: Jeff Manu Abhijit Knud
Found Date: 25 Mar 2010
Guessing minutes URL: http://www.w3.org/2010/03/25-rdfa-minutes.html
People with action items: benjamin jeff shane

[End of scribe.perl diagnostic output]