Add RDF information [#1029544]

Several points could use a RDF mapping

- the node view is not just any piece of content: it is a definition for the title
- a link from the title is a definition for it

First step: find if any ontology exists to support this and find whatever the mappings are. Second step: implement.

Issue fork g2-1029544

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

1029544-add-rdf-information compare
Check out this branch

About issue forks

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mlncn CreditAttribution: mlncn commented 17 January 2011 at 10:54

Issue tags:

+RDF

Hi, that's great!

The big ones are Dublin Core, Friend of a Friend (FOAF), Semantically-Interlinked Online Communities (SIOC), and Simple Knowledge Organization System (SKOS).

Comment #2

fgm

French

Paris, France

CreditAttribution: fgm commented 17 January 2011 at 13:07

I suspect SKOS and DC are the best bets for this.

- core already includes a small subset of DC information,
- skos:definition looks like a candidate for the "definition" pointer

Comment #3

scor CreditAttribution: scor commented 20 January 2011 at 14:31

What do you mean by "node view"? do you mean the node body?

Can you give an example of "link in the title" - how are these links in title generated? I'm obviously not familiar enough with g2 so these questions might sound stupid...

Comment #4

fgm

French

Paris, France

CreditAttribution: fgm commented 20 January 2011 at 17:20

The basic g2 node object contains:

- a g2 entry, typically either an initialism like "CSS" or normal word like "Drupal":
- an initialism expansion, like "Cascading Style Sheets" or "Content Scrambling System"
- a definition, like "A mechanism to provide style information [...]"
- a time period for when the term was current: from creation to end of mainstream use
- and it is usually complemented with taxonomy terms from various vocabularies

Then, when displaying the definition, <dfn> elements are converted by the input filter to <a href="...">...</a> links, which could likely be enhanced by a descriptive property saying, in effect, "this is the definition for that entry".

A G2 site also includes disambiguation pages for homonyms (as for the 2 CSS entries above), which is a very meaningful type of content, and per-initial pages, not so meaningful. But in both cases, each link goes to a definition for the link content, which is a specific type of relation, richer than just an anchor.

From D4.x to D6, expansion is a specialy use of the teaser, and definition is the node body. In D7, these are specific fields.

Comment #5

scor CreditAttribution: scor commented 20 January 2011 at 16:46

so each of these pieces of data is entered in separate fields by the user, right? as full blown text fields?

Comment #6

fgm

French

Paris, France

CreditAttribution: fgm commented 20 January 2011 at 17:22

Yes, this is how things stand currently.

In addition, I expect the 7.x version will have additional features on <dfn> elements in the definition, to qualify the definition by adding that a term is similar / related / antonym / (...) to the term on the current definition page.

Like, on the GPL page:

- expansion: General Public License
- somewhere in the definition

An equivalent for french jurisdictions is the <dfn qualify="similar">CeCILL</dfn>.

in the source, expanding to something like

An equivalent for french jurisdictions is the <a href="licence-cecill" rel="some_ns:equivalent" title="CEA CNRS INRIA logiciel libre">CeCILL</a>.

In which the G2 filter configuration would hold the namespace and attribute mapping, and the title on the href would be extracted from the target expansion field.