json ld - Adding a 'license' field to a schema.org Place record -
i have database of locations publish open data. each record can have 1 of several licenses depending on data sourced each record needs have license attached. i'm publishing data json-ld
. sample record:
{ "@context": "http://schema.org", "@type": "place", "name": "metropolitan museum of art", "address": { "@type": "postaladdress", "streetaddress": "1000 5th ave", "addresslocality": "new york", "addressregion": "ny", "addresscountry": "united states", "postalcode": "10028-0198" }, "hasmap": "http://www.openstreetmap.org/?mlat=40.7784&mlon=-73.9627#map=15/40.7784/-73.9627", "geo": { "@type": "geocoordinates", "latitude": 40.7784, "longitude": -73.9627 }, "description": null, "telephone": "+1 (212) 472-2764", "url": "http://www.metmuseum.org", "openinghours": null, "photo": { "@type": "imageobject", "contenturl": "http://127.0.0.1:8888/fsunhlajfsmnx55gnjee2-ykcge=/1000x1000/museums/logos/000/149/449/original/nyc_-_metropolitan_-_temple_of_dendur.jpg", "creator": "jean-christophe benoist", "license": "cc 3.0" } }
the schema.org place model doesn't have field 'license'. correct way add license type field record? want embed creativework field in there if possible.
it seems want provide license document about place
, not place
itself.
so go creativework
(or 1 of sub-types, webpage
if document web page) , make use of license
property.
to state creativework
place
, use about
property, , state place
primary entity described in document, use mainentity
property.
if want keep place
top-level node, use json-ld’s @reverse
about
property, , use mainentity
’s inverse property, mainentityofpage
.
Comments
Post a Comment