RDFa Working Group Teleconference -- 25 Feb 2010

<manu> trackbot, start telecon

<trackbot> Date: 25 February 2010

<manu> Scribe: Shane McCarron

<manu> action-3 due in 1 week

<trackbot> ACTION-3 Get in touch with LibXML developers about TC 142 due date now in 1 week

<manu> trackbot, status

<Knud> hello

<Benjamin> hello everybody

<manu> hi Knud, Benjamin :)

<Knud> I'm totally in awe of how this irc/phone mapping works

<manu> trackbot, status

<Knud> I'm mute now

<manu> http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Feb/0073.html

<Steven> scribenick: markbirbeck

<Knud> really? I muted my phone from here, actually

<Steven> Knud, I think it your line, not your phone

Action items

<manu> action-3?

<trackbot> ACTION-3 -- Manu Sporny to get in touch with LibXML developers about TC 142 -- due 2010-02-24 -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/actions/3

<manu> trackbot, action-3 due in 1 week

<trackbot> ACTION-3 Get in touch with LibXML developers about TC 142 due date now in 1 week

<manu> action-4?

<trackbot> ACTION-4 -- Mark Birbeck to generate spec text for @token and @prefix -- due 2010-02-24 -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/actions/4

http://webbackplane.com/mark-birbeck/blog/2010/02/vocabularies-token-bundles-profiles-rdfa

<manu> trackbot, comment action-4 proposal at http://webbackplane.com/mark-birbeck/blog/2010/02/vocabularies-token-bundles-profiles-rdfa

<trackbot> ACTION-4 Generate spec text for @token and @prefix notes added

Ivan: Could we move the write-ups onto the wiki?

Mark: Don't mind. It was more that it didn't work as an email.

<manu> action-5?

<trackbot> ACTION-5 -- Mark Birbeck to generate spec text for pulling in external vocabulary documents -- due 2010-02-24 -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/actions/5

<manu> trackbot, action-4 due in 1 week

<trackbot> ACTION-4 Generate spec text for @token and @prefix due date now in 1 week

<manu> trackbot, action-5 due in 1 week

<trackbot> ACTION-5 Generate spec text for pulling in external vocabulary documents due date now in 1 week

<manu> trackbot, close action-7

<trackbot> ACTION-7 Send Invited Expert proposals to Ivan closed

Manu: Have proposed Toby Inkster and Benji.

<manu> ACTION: Manu to get Toby to fill out Invited Expert form. [recorded in http://www.w3.org/2010/02/25-rdfa-minutes.html#action01]

<trackbot> Created ACTION-10 - Get Toby to fill out Invited Expert form. [on Manu Sporny - due 2010-03-04].

Manu: Benji says he is too busy to take up the Invited Expert position. Also, he says that he wants large changes to RDFa, and doesn't see that happening.

Ivan: Toby needs to fill in the IE form.

Manu: Will chase.

Ivan: What should we do with the issues that Benjamin raised?

<manu> ISSUE-12?

<trackbot> ISSUE-12 -- Analyze Benji's wishlist and determine if there are suggestions that will improve RDFa -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/issues/12

Manu: Think we should keep the issues. Any other views on that?

<ivan> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2010Jan/0065.html

<manu> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2010Jan/0065.html

Manu: Can we discuss this on the list?

Ivan: Some of them are pretty substantial; change attribute names, harmonise with Microdata.

Manu: Agree, but the action is to look at the suggestions and see what might be used from there.

<manu> Mark: Maybe we should re-visit ISSUE-12 in a couple of weeks.

<manu> action-8?

<trackbot> ACTION-8 -- Shane McCarron to coordinate with the PFWG on @role and how @role integrates with RDFa -- due 2010-02-26 -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/actions/8

<Knud> (did we talk about Action-6?)

<manu> ISSUE: Coordinate with PFWG on @role and how @role integrates with RDFa

<trackbot> Created ISSUE-17 - Coordinate with PFWG on @role and how @role integrates with RDFa ; please complete additional details at http://www.w3.org/2010/02/rdfa/track/issues/17/edit .

Shane: RDFa needs a way for other groups to be able to add attributes and elements to the list of supported attributes.

<manu> trackbot, drop action-8

<trackbot> Sorry, manu, I don't understand 'trackbot, drop action-8'. Please refer to http://www.w3.org/2005/06/tracker/irc for help

<manu> trackbot, close action-8

<trackbot> ACTION-8 Coordinate with the PFWG on @role and how @role integrates with RDFa closed

<manu> trackbot, comment action-8 Closed action in favor of creating as ISSUE-17

<trackbot> ACTION-8 Coordinate with the PFWG on @role and how @role integrates with RDFa notes added

<Steven> Yay! RDFa stylesheets!

<manu> action-6?

<trackbot> ACTION-6 -- Shane McCarron to identify the requirements for html2ps and see about getting reSpec to support them -- due 2010-02-24 -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/actions/6

Shane: Will write up a proposal on how other people might indicate in documents that other attributes are supported.

<manu> trackbot, close action-6

<trackbot> ACTION-6 Identify the requirements for html2ps and see about getting reSpec to support them closed

<manu> trackbot, comment action-6 it works.

<trackbot> ACTION-6 Identify the requirements for html2ps and see about getting reSpec to support them notes added

Review High-level Work Plan

<manu> http://www.w3.org/2010/02/rdfa/wiki/Work-plan

Manu: Very high level proposal on the wiki.
... On the API document we have Benjamin Adrian.
... We probably need other editors -- anyone?

Steven: Ben has experience of working on APIs -- would seem an obvious choice.

<manu> Mark: I was going to offer my services - I've been working on a Javascript library, so I'm interested.

<manu> Mark: Jeni Tennison has a slightly different API that is related - sits on top of SPARQL. We may try to harmonize with that work.

<manu> Mark: Do we want this in a separate document?

Mark: Experience of XForms WG is that if we have 'owners' of work, it tends to create a little fragmentation in the spec.

Ivan: True that it's separate in the charter, but might not be a problem to change our minds later. So can defer this.

Mark: Fine.

Manu: Could move this to the mailing-list.

<Zakim> Manu, you wanted to discuss taking the discussion to the mailing list.

Steven: How were people assigned to issues? Randomly?

<Knud> I'm muted

Manu: No. I tried to look at issues and who had the skills to address them.
... I may have failed, so please comment on whether you think you should be dealing with an issue (and of course, if not).

Knud: What is the Triple Store API about?

Manu: I assigned you because I thought your name came up on that.

Ivan: The idea is that rather than having an RDFa-specific API, we could look at something more generic.
... but it's not a required piece of work.

Knud: So it's not a generic API, but a JavaScript one?

Ivan: Yes, that's right.
... If there are documents that we'd like to be involved in, but not as lead editor, what should we do?

Manu: Go ahead and add yourself to the end of the list.

ISSUE-2: Extend RDFa to allow URIs in all RDFa attributes

<manu> http://www.w3.org/2010/02/rdfa/track/issues/2

<manu> ISSUE-2?

<trackbot> ISSUE-2 -- Extend RDFa to allow URIs in all RDFa attributes -- OPEN

<trackbot> http://www.w3.org/2010/02/rdfa/track/issues/2

Manu: The RDFa TF discussed and voted to support 'URIs anywhere'.
... We need to decide whether we will bring that proposal in.

Ivan: Might be worth setting the context.

<manu> http://www.w3.org/MarkUp/2010/ED-rdfa-syntax-20100113/

<manu> That's the latest text.

<inserted> scribenick: manu

Mark: The key thing is that
... realization that after working on CURIEs and URIs is that you could tell the difference between a CURIE and a URI
... basically, if there is a prefix, it's a CURIE
... if there isn't a prefix, it's a URI.
... The motivation for this is that for small pieces of markup, it allows one to just use URIs instead of defining a ton of namespace prefix mappings.
... It also allows easy cut-and-paste, which is a more overstated problem than it really is, but if you're concerned about that, this goes toward solving that issue.

Ivan: This is a fairly trivial implementation.

<markbirbeck> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Nov/0081.html

Ivan: separate issue, how will this change affect values for @resource and @about?
... @resource and @about are defined to have URIs or Safe CURIEs, but with the same logic, we can unify all attributes.
... let me explain with some markup

<ivan> xmlns="a:xxxxx" resource="a:something"

Mark: We were warned off of doing that in @href, so that's why we don't support it in @resource.

<ShaneM> http://htmlwg.mn.aptest.com/rdfawg/rdfa-core/

Ivan: We shouldn't touch @href and @src

<Steven> lol

<markbirbeck> Mark: We now use the token 'URIorCURIEs' in the spec, which means it will be everywhere.

<markbirbeck> Shane: Yes, it's already done.

<markbirbeck> Manu: We don't need to agree the solution here, we just need to vote on whether we want this.

<ShaneM> ACTION: Shane to suggest short names for each working group deliverable by 1 March 2010 [recorded in http://www.w3.org/2010/02/25-rdfa-minutes.html#action02]

<trackbot> Created ACTION-11 - Suggest short names for each working group deliverable by 1 March 2010 [on Shane McCarron - due 2010-03-04].

<markbirbeck> ...Any other questions on this? Would people feel comfortable doing a staw-poll now?

PROPOSAL: Add support for full URIs in RDFa attributes where CURIEs are allowed.
... Add support for full URIs in RDFa attributes..
... Add support for full URIs in RDFa attributes, barring @href and @src.

<Steven> href has full URIs alrady

<markbirbeck> PROPOSAL: Allow both URIs and CURIEs in all RDFa attributes, except @href and @src.

<ivan> PROPOSAL: for all attributes, except @href and @src, both CURIE and URI-s can be used, with priority to the former

PROPOSAL: Allow both URIs and CURIEs in all RDFa attributes, except @href and @src.

<ivan> +1

<Steven> +1

<ShaneM> +1

<markbirbeck> +1

<RobW> +1

<mgylling> +1

<Benjamin> +1

<Knud> +1

RESOLUTION: Allow both URIs and CURIEs in all RDFa attributes, except @href and @src.

- DRAFT -

RDFa Working Group Teleconference

25 Feb 2010

Attendees

Contents

Action items

Review High-level Work Plan

ISSUE-2: Extend RDFa to allow URIs in all RDFa attributes

Summary of Action Items

Scribe.perl diagnostic output