RDF

Hi there! New to Drupal. I need help.

What module(s) or resources are best to help me enable triple tags, where:
1. Each tag is composed of a subject, predicate, and object.
2. The subject, predicate, and object can be chosen from specific nodes on my site. Each field can suggest nodes as you type.
3. Two nodes with the same name can be differentiated by an ID or something.

My goal is to link my nodes into a linked graph that can be queried by something like views. I want to display the relationships between nodes.

Thanks for your help!

Greg

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:

We (the Kendra team) are in a bit of a quandary. We need to implement our EU funded project (Kendra Signpost) using Drupal but we are unsure, given recent D7/RDF announcements, as to which direction to take, namely D6 or D7 and using which modules.

Here is a brief description of what we want to achieve with questions as how to proceed - given that we have developers that can contribute to collaborative efforts so long as there is mutual benefit and we get to build Kendra Signpost.

Overview

• Kendra is being paid by the EU to build Kendra Signpost which needs to launch middle of 2010. Let's put this EU money to good use.
• Initially we wanted to build this system using only Drupal 7 but there are a number of modules that are just not ready for us yet. But as soon as Drupal 7 is ready we want to move all projects to it. So, we need to have clear upgrade paths when we choose Drupal modules. And perhaps only work on and contribute to efforts that are both Drupal 6 and 7 simultaneously.

I know I'm late on this, but I just read "If She Can Do It, I Can Too" a few days ago and was inspired. Looking for suggestions (even if it is a module that already does this) and a mentor. Cheers!

Synopsis
With the inclusion of RDF in Drupal 7 core, Drupal is being widely hailed as the best upcoming tool for producing content for the Semantic Web. However, for people to understand the power of the Semantic Web, we need to help them use the data that all of these Drupal 7 sites will be producing. Proprietary tools—such as Microsoft Pivot and the Adobe Flex—provide sleek visualizations of datasets. With this project, I aim to bring this kinds of advanced data visualization—with zoomable, data rich user interfaces—to Drupal. With these kinds of interfaces, Drupal will not only be the best way to produce content for the Semantic Web, but also the best way to consume that content and turn the data into something really interesting and understandable.

I am working on a very exciting drupal/ symantic web project. Part of what I am doing will involve theming data which has come from an RDF triple store.

I was thinking about the possibility of using RDF data to help choose the theme function to use.

For example I may be trying to theme something which is a imdb:director, and have no idea how to theme that. But if I have something which I know can theme a foaf:person and my rdf says that an imdb:director is a foaf:person I can use that function to theme the item.

For those of you who have been following Drupal 7 core development, you might be aware that many RDF patches have already been committed. So, before it's old news: Drupal 7 will ship with RDFa enabled by default on nodes, comments, terms and users!

The first alpha release of Drupal 7 will be created next Friday Jan 15th. We've already incorporated most of the feedback we received from the semweb community so far, but I wanted to give the community a last chance to review the RDFa markup and the default RDF mappings we use before it's too late. I should emphasize that all the markup and default RDF mappings that we ship in core will be pretty much set in stone after the stable release of Drupal 7, hence this call for feedback. Site administrators who care about semantics will be able to alter these mappings by installing extra modules, but many people (read several 10K sites) will just install Drupal 7 and not care about the semantics it generates. Therefore we want to make sure the RDFa generated by Drupal out of the box is somewhat correct and does not make folks from the semantic/pedantic web community angry :) - we've tried to keep the semantics as generic as possible for that reason.

RDF mappings

I've created a diagram representing the default semantics of the core data structure which has been committed and I would appreciate feedback on the RDF terms we've used.

On Tuesday night at the Melbourne Drupal Meetup, there was some discussion on the relevance of meta tags in helping search engines classify content..

While RDF in core will move us a long way toward more relevant semantic data, the major search engines continue to work on their search algorithms...

The Apache Solr RDF module is now in a state, where it can already, theoretically, be used. However, there is much room for improvement, so I'd like to discuss some possible ways to do this.