Re: Extension proposal for TouristAttraction class

+1

:-)


On 11/05/2016 09:55 AM, Martin Hepp wrote:
> I would also suggest to model the *role* of being a tourist attraction as either a single extra type and use MTEs, or define a property touristAttraction with a range of Boolean.
>
> Being a tourist attraction is IMO a secondary and more volatile (aka non-rigid) category of being as compared to essential type of the respective thing.
>
> Some things will be tourist attractions only temporarily, or for particular audiences (e.g. tourist from certain cultural spheres).
>
> By using a single TouristAttraction type, we would also have a container for such meta-data, e.g. validFrom, validThrough, targetAudience etc.
>
> Plus, we can apply it to any type in schema.org without hard-wiring which ones can be tourist attractions.
>
> Martin
>
>
> Note: Don't feel bad about shrinking the size of the contribution to schema.org. The less additional elements you need to cover your use-cases, the better is your modeling (as a general rule of thumb in this context).
>   
> -----------------------------------
> martin hepp  http://www.heppnetz.de
> mhepp@computer.org          @mfhepp
>