Drupal 7 port for Semantic CCK

Semantic CCK was actually born out of a discussion with the CCK module maintainers (see #670040: Semantic CCK?), but they seemed to be strongly against the idea so we decided to build this functionality as a separate module ourselves. If they were to change their minds in the future I would be happy to see this functionality in CCK core, but until then we'll continue to maintain it as a separate module.

As for a Drupal 7 port, yes that is something I intend to do. Assigning this to myself to work on.

Can't wait. I've become addicted to this module in D6 and am strongly feeling its absence in D7. I'll be happy to help test.

FYI, It's not true that Semantic Views is integrated in Views 3.x for D6/7.

See this issue: #1013876: Is Semantic Views module obsoleted by Views 3? in the Semantic Views issue queue. I like what views is doing, but it's not exactly making that module obsolete.

Changing the title for better differentiation in the dashboard.

Any updates on this Drupal 7 port ?

Maybe for Drupal 7 it should be a separate module called semantic_fields? I'm just saying because this will cause a little confusion since there is going to be CCK for Drupal7, but really the intention of the Drupal 7 port of this module is for it to work with fields and not have cck as a dependency. What do you guys think?

Yes, Rene (rhache) and I also thought that the Drupal 7 version should be a separate module, with a name that reflects the fact that fields are now in core in D7. To that end, I have just created a new project called Semantic Fields (http://drupal.org/node/1143458), which will be the Drupal 7 version of Semantic CCK. A dev release has been created and should be appearing on the project page soon.

We would greatly appreciate any help with testing the Semantic Fields module before we create a stable release. Please post any feedback, bugs, feature requests, etc. in the Semantic Fields issue queue.

Thanks,
Ryan

Great news !

Thanks Ryan, that's awesome news. Marking this issue as fixed since there is a notice in the project page already redirecting to Semantic Fields. Will start testing Semantic Fields next week and post any issues on the queue :)