 |
 |
Hi Thomas, Thanks for raising this point. In fact Dan Brickley had raised that same question already regarding the RDF in Drupal [1], and you confirmed this was a good move at [2]. We've already integrated this in the Drupal code base, and since we only use sioc:User resources we're covered. Steph. [1] https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0909&L=DC-ARCHITECTURE&T=0&F=&S=&P=22615 [2] https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0909&L=DC-ARCHITECTURE&T=0&F=&S=&P=23695 On Tue, Nov 10, 2009 at 11:29 PM, Tom <[log in to unmask]> wrote: > > On Nov 10, 5:42 pm, "Evan Sandhaus <[log in to unmask]>" > <[log in to unmask]> wrote: > > As for the dc/dcterms name spacing issue, I can only say: good call. > > Look simplified Dublin core namespacing in version 3 of the data. > > > You are using both the dc: and the dcterms: namespace. The latter is > > > just an updated/improved version of the former. I think that you > > > should use dcterms: everywhere (which would make the dc: namespace > > > declaration unnecessary. Or you could use the dc: prefix, but with the > > > > dcterms URI.) > > Careful - the legacy "dc" properties (e.g., > http://purl.org/dc/elements/1.1/creator) > have no formally defined ranges. In practice, dc:creator is used > either with a > literal or non-literal value - i.e., a name or a resource. > > The updated/improved "dcterms" properties have ranges (e.g., > http://purl.org/dc/terms/creator has a range of > http://purl.org/dc/terms/Agent), > so it would be incorrect, for example, to use dc:creator with a > (literal) name > as value. > > I do not have the data before me to check directly... > > Tom