[Typo3-dev] JSR170

[Kasper Skårhøj]

> Since my reply to Kasper which was in cc to this list seems not to appear
> here, here are the generally relevant contents in short:
> 
> Scenario 2 is the one that is interesting for TYPO3 strategically at
> present.
> Scenario 1 could interest some organisations using TYPO3, if some of these
> will eventually sponsor such an API, we can make it a project..
> 

I'm puzzled why Scenario 1 is not of interest marketing wise. I thought
your argument would be that one day people will only choose TYPO3 if
they know the data inside of TYPO3 can be accessed through JSR-170 so
that it is not "proprietary" or locked to our CMS. No "vendor-lockin" on
content. This is what scenario 1 gives.

Scenario 2 is about what content sources TYPO3 can use when presenting
data and in any case where a specific resource is needed it is most
likely that a custom made plugin is needed anyway.

- kasper