See also: IRC log
<trackbot> Date: 19 January 2012
<scribe> scribenick: MacTed
<scribe> scribe: Ted
Admin: Agenda review
<manu1> https://www.w3.org/2010/02/rdfa/track/issues/84
<ShaneM> The spec now says: In some of the examples below we have used IRIs with fragment identifiers that are local to the document containing the RDFa fragment identifiers shown (e.g., 'about="#me"'). This idiom, which is also used in RDF/XML [RDF-SYNTAX-GRAMMAR] and other RDF serializations, gives a simple way to 'mint' new IRIs for entities described by RDFa and therefore contributes considerably to the expressive power of RDFa. The precise meaning of IRIs which inclu
<manu1> PROPOSAL: Adopt the WWW TAG proposed language on fragment identifiers and place it into RDFa Core 1.1
<manu1> +1
<niklasl> +1
<ShaneM> +1
<ivan> +1
+1
<scor> +1
<ivan> RESOLVED: Adopt the WWW TAG proposed language on fragment identifiers and place it into RDFa Core 1.1
<manu1> https://www.w3.org/2010/02/rdfa/track/issues/125
manu: SPARQL & Turtle use a
different CURIE definition than current RDFa; request is that
RDFa be aligned to the others
... concern is that requested revision differs from Turtle and
SPARQL by explicitly disallowing http (and possibly some other
prefixes)
niklasl: not quite clear on
what's allowed and not, by these syntaxes... forward slashes
seem to require backslash-escaping
... Gavin appears to have misinterpreted some docs
ivan: sympathizes with goal of same syntax across RDFa, SPARQL, & Turtle; but if request is to put an extra restriction in RDFa, not sure that's needed
<manu1> http://www.w3.org/TR/2012/WD-sparql11-query-20120105/#rPN_PREFIX
manu: thinks group would agree that 1 syntax for CURIEs across all specs/languages would be good. concerned about ways that requested definition differs from Turtle and SPARQL.
<scor> does the current RDFa syntax definition for CURIEs allow http:// ?
<ShaneM> I am not in favor of making changes to this at this time.
<niklasl> scor: I'm afraid so
ivan: sees 2 concerns from Gavin. 1 = discrepancy between RDFa and SPARQL/Turtle CURIE def; 2 = prefix restriction(s)
(...discussion...) suggested (quoted?) syntax BNF in http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Jan/0025.html would disallow many currently acceptable CURIEs
<ShaneM> this BNF is making my eyes bleed
(...discussion...) schema.org extensions via '/' would be invalidated by this syntax
<ivan> http://schema.org/docs/full.html
<scor> ivan: not as far as I know
<scor> these are full types of their own
<niklasl> look at http://schema.org/docs/schemaorg.owl
<scor> ivan: it's only for external parties willing to extend these types
<ivan> http://schema.org/docs/extension.html
<scor> not on schema.org itself
<scor> we should bounce the / issue back to Gavin and the RDF WG
<scor> re the use of / in DBpedia and schema.org extensions
manu: we've confirmed a real-world use case requiring unescaped slashes in CURIEs, with third-party extensions of schema.org
<manu1> PROPOSAL: Reject the SPARQL 1.1 Query Language definition of PN_LOCAL and PN_PREFIX for CURIEs in RDFa 1.1
<manu1> -1
<scor> -1
<ivan> -1
<ShaneM> -1
<ShaneM> I am a big fan of dbpedia reference
<niklasl> +0
+0
<manu1> RESOLVED: Reject the SPARQL 1.1 Query Language definition of PN_LOCAL and PN_PREFIX for CURIEs in RDFa 1.1
<manu1> BIG MISTAKE - that was rejected!
(hm. doubled s/Accept/Reject/ sequence may have re-broken that in minutes. RESOLUTION is correctly to REJECT.)
<niklasl> .. http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Jan/0027.html
<ShaneM> BTW we published the CURIE spec as a note when the xhtml working group shut down: http://www.w3.org/TR/curie/
(...discussion...) colon as separation character is where the trouble lies, but fixing that is an enormous task touching many specs
<ShaneM> I am actually not opposed to preventing a slash as a first character
<ShaneM> (of a reference)
<ivan> 0
<manu1> PROPOSAL: Prevent a slash as the first character in the reference part of a CURIE.
<manu1> -1
<ivan> 0
(...discussion...) past specs allowed what we're considering disallowing... which means we're building backward incompatibility
(...discussion...) current refinement suggestions are further departure from CURIE specs in SPARQL and Turtle, not alignment
<ShaneM> 0
<niklasl> +1
<ivan> -0
+0
<scor> -0
<ivan> http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Jan/0031.html
<manu1> PROPOSAL: Change XML+RDFa such that RDFa attributes are defined in 'no namespace' and also caution authors that they must pay attention to XML-based languages where the RDFa attributes and Host Language attributes may overlap.
<ivan> +1
<manu1> +1
+1
<ShaneM> +1
<niklasl> +1
<scor> +1
<manu1> RESOLVED: Change XML+RDFa such that RDFa attributes are defined in 'no namespace' and also caution authors that they must pay attention to XML-based languages where the RDFa attributes and Host Language attributes may overlap.
trackbot, end meeting
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) Succeeded: s/Accept/Reject/ Succeeded: s/Accept/Reject/ Found ScribeNick: MacTed Found Scribe: Ted Default Present: scor, MacTed, +1.540.961.aaaa, manu1, niklasl, +1.612.217.aabb, ShaneM, Ivan Present: scor MacTed +1.540.961.aaaa manu1 niklasl +1.612.217.aabb ShaneM Ivan Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Jan/0024.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 19 Jan 2012 Guessing minutes URL: http://www.w3.org/2012/01/19-rdfa-minutes.html People with action items:[End of scribe.perl diagnostic output]