W3C

- DRAFT -

SV_MEETING_TITLE

22 Sep 2010

See also: IRC log

Attendees

Present
Regrets
Chair
SV_MEETING_CHAIR
Scribe
sandro

Contents


<ChrisW> are we meeting today?

<ivan> well... I have not had the time to prepare an agenda or to prepare to the meeting

<ivan> (I was in France, my mother had a surgery a few days ago)

<ivan> but I think there are some issues we could/should discuss if there are enough people around

<ivan> and the right people, that is:-)

<ivan> sorry about the mess, it is one of those things that happen unexpectedly

<ChrisW> no problem. understandable.

<ChrisW> an ad hoc meeting is fine with me.

<ChrisW> be there in 5 mins

<Zakim> TomB, you wanted to express some concern about long-term preservation issues

<Zakim> mhausenblas, you wanted to note on requirements

<mhausenblas> http://www.w3.org/TR/2010/WD-rdfa-core-20100803/#s_profiles

<mhausenblas> http://data.jquery.com/

<TomB> -> We are sorry. We could not find the site "data.jquery.com":

<TomB> -> SearchAssist recommends dyndns.com or jquery.com

<manu1> http://jquery.com/

<manu1> or http://jquery.org/

<mhausenblas> yes, that's the point, TomB

<manu1> Who is using jQuery: Google, Dell, Bank of America, Major League Baseball, Digg, NBC, CBS News, Netflix, Technorati, Mozilla, Wordpress, Drupal, etc.

manu: if we implemented a standalone API, anyone could convert it into a jQuery plugin in about 4 days, it's really easy.

<manu1> http://www.w3.org/TR/2010/WD-rdfa-api-20100923/

<manu1> ha, published in the future.

<mhausenblas> http://www.w3.org/blog/SW/2010/09/22/new_drafts_of_the_rdfa_api_published btw ;)

ping

manu: our API is jQuery like (functional, compact), but not as out-there as jQuery.
... our RDF API is trying to be implementable in PHP and Python, not just Javascript.

(ohhhhh, I was thinking this was at least Javascript specific.)

<manu1> sesame

ivan: The community will probably be okay with us doing a javascript API, but doing an ALL-LANGUAGE RDF API ? That's a much bigger deal -- it competes with Sesame, Jena, Redland, etc.

manu: I think our goal should be all the modern languages.

PROPOSED: let the RDFa WG proceed as it is currently doing, developing an RDFa API, which just so happens to be yet another general RDF API. At some point in the future, we may do future standards work on an RDF API.

<manu1> +1

<TomB> bye!

<mhausenblas> bye

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/09/22 14:03:06 $

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)

No ScribeNick specified.  Guessing ScribeNick: sandro
Inferring Scribes: sandro

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: ChrisW Ivan P11 PROPOSED Sandro TomB aaaa manu manu1 mhausenblas
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 22 Sep 2010
Guessing minutes URL: http://www.w3.org/2010/09/22-swcg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]