15:14:27 <sandro> not seeing any mention of Domain Lead in http://services.w3.org/xslt?xmlfile=http://www.w3.org/2005/08/01-transitions.html&xslfile=http://www.w3.org/2005/08/transitions.xsl&docstatus=lc-wd-tr

15:20:54 <gkellogg> manu: pub date is for tomorrow, as we've said for over a week.

Manu Sporny: pub date is for tomorrow, as we've said for over a week.←

15:21:50 <manu> PROPOSAL: The RDF Working Group believes that there are no IPR commitment issues for the JSON-LD Syntax and the JSON-LD API FPWDs. Publication should commence tomorrow - July 12th, 2012.

PROPOSED: The RDF Working Group believes that there are no IPR commitment issues for the JSON-LD Syntax and the JSON-LD API FPWDs. Publication should commence tomorrow - July 12th, 2012.←

15:21:59 <gavinc> Also, the documents version control can be found at http://dvcs.w3.org/hg/json-ld/summary not in the rdf hg repository, in case anyone can't find them

15:26:54 <gkellogg> david: I've been involved in other groups with task-forces that met seprately.

David Wood: I've been involved in other groups with task-forces that met seprately.←

15:27:17 <gkellogg> … Any one in this group should be welcome to join. You've effectively changing from a CG to a task force of this group.

… Any one in this group should be welcome to join. You've effectively changing from a CG to a task force of this group.←

15:28:07 <AndyS> Suggestion ... JSON-LD changes (not API) go to the RDF-WG list because it's a wider group in CG. "Commit then review" (master doc is in RDF hg?)

Andy Seaborne: Suggestion ... JSON-LD changes (not API) go to the RDF-WG list because it's a wider group in CG. "Commit then review" (master doc is in RDF hg?)←

15:28:19 <gkellogg> manu: I think we need to be careful about how we get input in. We don't want to slow the group down by adding process, but if someone from the public joins this could create IPR issues.

Manu Sporny: I think we need to be careful about how we get input in. We don't want to slow the group down by adding process, but if someone from the public joins this could create IPR issues.←

15:37:14 <gkellogg> andy: I'd be sure that you get this checked by W3C. Unwinding this could be a problem, as it's talking about licensing, not release. Reassignment of IPR is impossible, and blocked in some con tries.

Andy Seaborne: I'd be sure that you get this checked by W3C. Unwinding this could be a problem, as it's talking about licensing, not release. Reassignment of IPR is impossible, and blocked in some con tries.←