Semantic Web

Hi,

for all of you who are interested in (Open Source) Semantic Web Technologies:
I would like to invite you to the KiWi Release Party on 14. October 2010 in Vienna, Austria!!

KiWi is an open-source development platform for building Semantic Social Media applications. See: http://www.kiwi-community.eu.

KiWi Release Party - The Facts
Time: Thursday, October 14 · 6:30pm - 11:30pm

Location: Planetarium Vienna, Oswald Thomas Platz 1, 1020 Vienna, Austria

Whenever I try to import and external RDF library, I get this error:

* warning: Invalid argument supplied for foreach() in /home2/future/public_html/drupal/sites/all/modules/evoc/evoc.module on line 199.
* warning: Invalid argument supplied for foreach() in /home2/future/public_html/drupal/sites/all/modules/evoc/evoc.module on line 199.

Then it tells me the namespace has been created.

Should I worry about this? What does it mean?
Bruce

Please forgive the trivial nature of this question. I've been doing some background reading but not quite sure exactly where to begin.

I have a currently functioning Drupal 6 site. It works great with Views, CCK, and a few other modules. I want to add RDFa tags so content on my site can be found (and linked) from semantic web search engines. It seems like I would need to add three modules:

RDF
RDF CCK
RDF External Vocabulary Importer

Obviously, the title was created was designed to elicit discussion ... but I am seriously interested in the prospects for unintended consequences of D7's default use of RDF. D7 will be a great leap forward, and I'm genuinely excited about the prospects of D7's adoption of RDFa. Upon further reflection, I'm wondering if D7's embrace might actually make it easier for users to be tracked by organizations like Recorded Future. I understand, that today's default settings can be "undone" ... but it is the default that has me most concerned ... precisely because it is the novice end user who isn't particularly savvy that will be put at most risk ... and is unlikely to even know what is going on "under the hood" ... I know, I know ... probably an exaggerated concern, but I thought I'd throw it out there and see if anyone might want to comment.

Hi everyone,

I was wondering if anyone had any comments on the http://www.vivoweb.org project and it's relationship ship to Drupal. VIVO in a nutshell, is a web application provides a semantic database that can be searched that contains information about scientists, their research interests, affiliations, publications, grants, etc. VIVO is in deployment at several universities and is being expanded through a $12.2m stimulus grant from the National Center for Research Resources (NCRR) of the National Institutes of Health (NIH). see more at http://www.vivoweb.org/about/faq/about-project

Importing catalogues

We need to import arbritary catalogues (spreadsheets) into RDFable Drupal nodes.

We suggest the following as a way forward: before implementing this, we want to see if this would be useful to the broader Drupal RDF community, and whether it is compatible with other existing proposals:

Option 1: Dynamically create content types

For each import format dynamically create a node type that matches the field structure. Provide an RDF mapping for the created node type to enable the imported items to be tagged up with RDF.

Option 2: Define a generic content type for imports

Spreadsheets are imported into two node types. The 'header' includes the spreadsheet file and information about it's structure. A second content type is used to import each row. A row is a list of attributes taken from the column data for that row.

We also need to consider round-tripping issues, as follows: