[Idea] extend h-event with a microformat for Calls for Papers

[heiglandreas]

A lot of events have a call for papers/call for speakers/call for proposals/whatever the name is (CfP).

It would be amazing if we could find a standardized way of allowing website-providers to tag these informations for easier automated retrieval.

As maintainer of callingallpapers.com - which aggregates CfP informations from various websites such as sessionize.com, papercall.io or confs.tech - I am usually interested in these informations:

• Direct URL to the CfP (which is usually something different than the website of the event)
• date, time and timezone when the CfP closes

Additional nice-to-have information would be

• target-technologies, Audience etc in the form of tags to add some context what this CfP/Event is about
• date, time and timezone when the CfP starts as sometimes the information is already available but the event does not yet accept submissions.

So some addition to the h-event would be much appreciated.

Something like a h-cfp class to show that a CfP information is present and then something like a dt-end-cfp and a u-url-cfp. Or would class="h-cfp u-url" be sufficient?

Happy to discuss.

[gRegorLove]

First, welcome to microformats! If you haven't yet, check out the microformats process. We also have microformats chat if you have any questions about publishing or consuming microformats.

Thanks for opening this discussion. Before jumping to class names and a new root h-* microformat, we should document current real world publishing behavior and previous formats. There may be past exploratory discussions for similar ideas as well. The process page above has more details.

At first glance, a lot of the properties you described sound like a separate event. A CFP usually has: name, start datetime, end datetime, description, one or more URLs, and tags. These are all properties that could be in an h-event currently, so it's worth considering how existing microformats could be used to meet the use-case.