W3C

- DRAFT -

RDF Web Applications Working Group Teleconference

21 Jun 2012

Agenda

See also: IRC log

Attendees

Present
niklasl, MacTed, manu1, scor, gkellogg, Ivan, ShaneM
Regrets
Chair
SV_MEETING_CHAIR
Scribe
MacTed

Contents


<trackbot> Date: 21 June 2012

I can fake it

Twitter Cards

<scribe> scribenick: MacTed

gkellogg: Twitter is using an RDFa-like syntax, with a Twitter namespace without an IRI mapping

<gkellogg> https://dev.twitter.com/docs/cards

gkellogg: if there were a default mapping to a Twitter IRI, it could be easily parsed/mapped across the board

manu: it's apparently kind of like Facebook's OGP, and mostly interoperable, but not quite

ivan: more than a namespace issue here

<manu1> MacTed: Just because somebody else has come up with something vaguely related, we should not try to map the new random syntax into RDFa.

<manu1> Niklas: I agree as well - maybe they have a reason... or they are just ignorant of standards.

manu: I will reach out to my contacts and see what might be doable...

<manu1> MacTed: We're not there yet, though - let's reach out first and see what they have to say about interoperability.

<manu1> MacTed: Yes, we need to educate Twitter first - let's see why they went against what all the other companies doing this stuff are doing.

<manu1> MacTed: They did finally move away from hash-bangs - maybe they will learn here as well...

<manu1> MacTed: The thing that they're just rolling out probably wasn't built in a week, so they may have had no idea that RDFa existed...

RDFa 1.1 launch post-mortem, wrap-up

manu1: applause for all involved...
... we know about some errata that must be addressed
... and some more press on RDFa 1.1 is needed
... maybe start an RDFa Community Group with monthly telecons to touch base and keep tutorials and such fresh

ivan: Community Group sounds like the best path forward.
... errata must be handled carefully so they don't give an impression of instability
... perhaps hold until end of summer or thereabouts

<Zakim> ShaneM, you wanted to mention an issue

RDF API and RDFa API publication timeline

<manu1> RDF Interfaces:

<manu1> http://www.w3.org/2010/02/rdfa/sources/rdf-interfaces/Overview-src.html

<manu1> RDF API:

<manu1> http://www.w3.org/2010/02/rdfa/sources/rdf-api/Overview-src.html

<manu1> RDFa API:

<manu1> http://www.w3.org/2010/02/rdfa/sources/rdfa-api/Overview-src.html

manu: has updated documents to make W3C Notes (some responses are still pending)

ivan: some interconnection references need minor correction updates...

<ivan> Work on this document represents unfinished work of the RDF Web Application Working Group. The work could not be finished due to a lack of manpower, and, at the time of publishing this document, it is not known whether W3C will continue this work on Recommendation track in another Working Group.

<ivan> While a significant amount of design work went into this document, at present there are no known implementations of the specification. A number of design issues have not been completely resolved. Developers wishing to implement this API should be aware of incomplete nature of the specification.

<ShaneM> Here is what we said for CURIEs: This document is a Working Group Note. The XHTML2 Working Group's charter expired before it could complete work on this document. It is possible that the work will be continued by another group in the future.

<gkellogg> Alex volunteered to help improve the API docs.

[... administrivia ...]

<manu1> PROPOSAL: Publish RDF Interfaces, RDF API, and RDFa API with Ivan's changes as W3C Notes on July 28th or July 5th (as a backup date).

<ivan> +1

<manu1> PROPOSAL: Publish RDF Interfaces, RDF API, and RDFa API with Ivan's changes as W3C Notes on June 28th or July 5th (as a backup date).

<gkellogg> +1

<manu1> +1

<ivan> +1

<niklasl> +1

+1

<ShaneM> +1

<scor> +1

<manu1> RESOLVED: Publish RDF Interfaces, RDF API, and RDFa API with Ivan's changes as W3C Notes on June 28th or July 5th (as a backup date).

HTML5+RDFa spec changes and publication strategy

<manu1> manu: I haven't had time to integrate the latest changes into the HTML5+RDFa spec, but I will integrate those changes after all these other documents have been published.

trackbot, end meeting

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/06/21 15:07:54 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: MacTed
Inferring Scribes: MacTed
Default Present: niklasl, MacTed, manu1, scor, gkellogg, Ivan, ShaneM
Present: niklasl MacTed manu1 scor gkellogg Ivan ShaneM
Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Jun/0017.html

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

Found Date: 21 Jun 2012
Guessing minutes URL: http://www.w3.org/2012/06/21-rdfa-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]