linked data

Hi everyone.

I just joined this group and wanted to let you know about an effort of ours to create a module to fetch taxonomy terms from external sources. This would mean no more free hand tags and instead the autocomplete field keyword searches a bunch of providers through their open apis.

The providers are modular in nature, so anyone can make a new provider for the base module, which is called Yild (Yild - integrator for Linked Data).

Good morning,

I've cross-posted this to both Semantic Web and Libraries because I think there are elements that appeal to both.

I'm going to give a bit of background on the project I'm working on and hopefully I can get some confirmation as to whether or not this is the "best" way to go about doing this. This is Drupal 7, of course. So far, I've been moving in the most obvious direction and using the tools that are most readily available.

Back-story:

Hello,
I was wanting to produce RDF files for each member of a large online community of writers. It is using Drupal 7, so it has RDFa and many vocabularies "out of the box." I might want to add doac (description of a career), vcard RDF vocab, and perhaps bio.
I don't know if it is possible to go in now and create a file structure for holding data files that relate to each person. For example, starting with FOAF, I'd want to have a folders structure such as:
[username]/foaf.rdf
or better yet:
[user's real name/foaf.rdf

Are there any guidelines/best practices for assigning URIs for Drupal Linked Data?

I've got the various modules publishing RDF just fine, and can get RDF from URIs like http://hostname/node/xyz/rdf, but this sort of URI is really an implementation detail, and therefore not in the spirit of linked data URIs. It would seem to be much more appropriate to have URIs that might read something like http://hostname/content-type/title.

I've tried using Pathauto, which rewrites the URLs well-enough, but doesn't provide the RDF as expected.