- From: Sarven Capadisli via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jun 2016 16:40:24 +0000
- To: public-annotation@w3.org
csarven has just created a new issue for https://github.com/w3c/web-annotation: == Fragment Specification for RDFa == At the moment, I think the `dcterms:conformsTo` for an `oa:FragmentSelector` for (X)HTML+RDFa could go either way; HTML or RDF/XML, i.e., namedSection or a namedResource. In cases where the fragment has a IRI with an RDF description behind it (i.e., the triple through the RDFa markup), my understanding is to use the RDF/XML's fragment specification. If the fragment is an HTML @`id` with no IRI used in RDFa (with base + fragment), then the HTML fragment specification makes sense. I think there is an alternative to above which is specific for RDFa IRIs, given that [RDFa Core 1.1 CURIE and IRI Processing](https://www.w3.org/TR/rdfa-syntax/#s_curieprocessing) refers to [RFC3987](https://tools.ietf.org/html/rfc3987). RFC3987 is also listed under http://w3c.github.io/web-annotation/model/wd2/#terminology Am I looking at this right? Should RFC3987 be added as a fragment specification for (X)HTML+RDFa? Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/295 using your GitHub account
Received on Thursday, 9 June 2016 16:40:26 UTC