Martin Hepp

# Solution and Conclusion **1. The best solution is to install `Podman`,** which is super-simple, and to use the `--userns=keep-id` option. As the additional uid/gid parameters described in the current...

> @mfhepp thanks for the detailed investigation and clear recommendations. I am certainly in support of increasing our documentation in this area. Do you have any interest in putting together...

First, note that schema.org only needs a more specific type IF the consumers of the data need this level of detail for their processing of the data. If it is...

If the Google Validator fails on external types (like http://www.productontology.org/doc/Condominium in the example above), then you can always use the more abstract schema.org type in the @type place and use...

Why don't use simply use this? ``` { "@type": "Accommodation", "additionalType" : "http://www.productontology.org/id/Condominium", "name" : "ACME Condos", "description" : "Luxury at its finest, lorem impsum...", "address": { "@type": "PostalAddress", "addressLocality":...

Can we please avoid using "Quotation" for this and use e.g. "quote"? Quotation is also used in the commercial world and me might want to extend schema.org lateron to support...

ok, no more objections against "Quotation" for the liberal arts and "Quote" for the business worlds ;-)

@danbri I am looking forward to the quotation ;-)

Hmm :-) As the person who initially proposed this modeling approach in GoodRelations, I would like to raise a few points: Yes, having types for offers by the type of...

**Addendum:** I am not in general against adding a few selected offer subtypes so that the markup for typical sell and lease offers gets simpler in terms of markup, as...