[TYPO3-dev] The state of support for the Semantic Web / RDFA / Web 3.0 in TYPO3

[Jochen Rau]

Hi Martin.

Martin Kutschker wrote:
> Jochen Rau schrieb:
>> Hi Martin,
>>
>> Martin Kutschker wrote:
>>> Jochen Rau schrieb:
>>>> The first step towards this goal will be to add Semantics to the
>>>> (Domain) Objects of the Extensions. So we can couple a Domain Object
>>>> like Tx_MyExtension_Domain_Model_Client to a semantic model "Person".
>>>> The semantic model holds all the invariants, like "A Person has a date
>>>> of birth. A Person has a father an a mother (which are also Persons).
>>>> ...".
>>> Could this be added to the TCA itself. At least some of the meta
>>> information?
>> The TCA is intended to configure tables in a database.
>
> Not completely true. It also defines for example the BE rendering in
> forms and lists. It has (had) rudimentary support

Yes, it defines the access to the database tables vie the backend.

> Anyway I agree that the TCA is not the very best place to add meta data.
> OTOH I can see that you want to push ExtBase, but why deny classic TYPO3
> extensions the powers of RDFa etc? Actually FLOW3/ExtBase will not do
> much with the semantics then to output a few tags.

Did I say Extbase? ;-) A generic Domain Model can be extended by any 
class. The key is to use meaningful Models (with or without Extbase). If 
anybody is interested to extend the marker based template engine he is 
able to do that. I stick to Fluid ;-)

There are several use cases for semantic integration in TYPO3:
- Facet browsing (a kind of aspect oriented browsing; see 
http://simile.mit.edu/potluck/ for an example)
- Export rich information (vCard for example)
- Query the content with SPARQL (http://en.wikipedia.org/wiki/SPARQL)
- More intelligent search (mashed up information from many sites)
- and, of course, enriched output generation.

Furthermore, adding "a few tags" makes the difference for GoogleYahooFoo 
to be able to "read" our content and wire it together with other resources.

Regards
Jochen



-- 
Every nit picked is a bug fixed