see also #3 and #6
more information about features for a generic transformer in #12 and a bug thats connected to that in #13
connected to #13
implement "base event transformer", move event specific stuff there
For evaluation partners see #18
In #14, andre did already collect some of the organizers
after writing more of the tribe extractor, i think providing an easy way to create a setting page would be super useful. there are multiple (ap/mz:event) properties which could be set via custom…
There is an (unpolished) but nice looking tribe transformer now, can you give me feedback?
I agree with your opinion on adding common object types and i also like your idea of coupling the properties and the context via the PHP-docs
I think the transformer should be able to control it, but it should be easier to not control it (setting defaults somehow).
regarding the id: if i read [this](https://www.w3.org/TR/json-ld/#iris…
i mean, it can be used to write some of the tribe transformer nicer, because it documents how to extract information from tribe plugins.
context generation looks fairly boring
It looks like it's generated only for the purpose of SEO