- From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
- Date: Thu, 16 Jan 2014 10:21:58 -0500
- To: Ivan Herman <ivan@w3.org>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, public-openannotation <public-openannotation@w3.org>, Gregg Kellogg <gregg@greggkellogg.net>, Manu Sporny <msporny@digitalbazaar.com>
- Message-ID: <CAFPX2kBd9aMCyNM=hqC+O43AqDt1pdbkaR+VDECZRAbOPVtGVw@mail.gmail.com>
Thank you Markus and Ivan! Rob, I understand your concerns. As developer the switch will require some additional work as well... and I am sure not everybody will be noticing the subtle change. Another option would be to delay the change until 'a next version of the spec' so that we have time to sort out the open issues and hopefully go down to one single namespace. Or even evaluate alternatives if we can't find a good fit. At that point I agree, the change would be a lot easier to detect. Tom, in order to evaluate using a single dc namespace, we need to better understand the intended use of MediaTypeOrExtent and LinguisticSystem in DC-TERMS. I can find lots of pages with the class definition but no actual instances or explanations on how to use those properly. Could you or somebody else close to the Dublin Core initiative help us out with understanding how to use these classes? In any case, I am not entirely sure about abandoning Literals for more complex artifacts. DC elements and even schema.org ( http://schema.org/inLanguage ) are pretty straightforward to be used for that purpose. So I would probably be inclined to keep two different namespaces.... In this case changing the prefixes sooner rather than later would avoid even more software using the old ones erroneously. Let's see if we can understand better the use of MediaTypeOrExtent and LinguisticSystem first. Best, Paolo On Thu, Jan 16, 2014 at 9:44 AM, Ivan Herman <ivan@w3.org> wrote: > > On 16 Jan 2014, at 15:24 , Markus Lanthaler <markus.lanthaler@gmx.net> > wrote: > > > > > On Wed, 15 Jan 2014 10:42:59 -0700, Robert Sanderson wrote: > >> That said ... if W3C were to issue a JSON-LD context for the RDFA core > >> mappings, then we could inherit it as a best practice. That would > provide > > a > >> substantive benefit, both in terms of understanding and reducing the > need > >> for dereferencing of resources. > > > > That has already been done. I've created the context a while ago at > > > > https://gist.github.com/lanthaler/5056140 > > > > and it has been uploaded to > > > > http://www.w3.org/2013/json-ld-context/rdfa11 > > > > It would probably be worth mentioning that directly on > > > > http://www.w3.org/2011/rdfa-context/rdfa-1.1 > > > > so that people will actually find it. Serving it directly at that URL > (using > > conneg) would be great as well. > > > > Actually, I did that as well. Both > > http://www.w3.org/2011/rdfa-context/rdfa-1.1.json > > and > > http://www.w3.org/2011/rdfa-context/rdfa-1.1.jsonld > > refer that file through redirection. > > Ivan > > > > > > > P.S.: Thanks Ivan for bringing this to my attention > > > > > > Cheers, > > Markus > > > > > > -- > > Markus Lanthaler > > @markuslanthaler > > > > > ---- > Ivan Herman, W3C > Digital Publishing Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > GPG: 0x343F1A3D > FOAF: http://www.ivan-herman.net/foaf > > > > > >
Received on Thursday, 16 January 2014 15:22:26 UTC