Let all types has the https://schema.org/additionalProperty

[fishfree]

https://schema.org/additionalProperty supports arbitrary key-value pairs, so it's very suitable for extended description. Or is it only neccessary to add this property in the Thing type? Then all other types can inherit it.

[github-actions[bot]]

This issue is being nudged due to inactivity.

[MatthiasWiesmann]

Are you suggesting additionalProperty be a property of Thing?

[fishfree]

@MatthiasWiesmann Yes, exactly. It will add great extensibility to describe things.

[MatthiasWiesmann]

I would bring this to the larger community, as this would be a significant change.

[smrgeoinfo]

Thing seem like a pretty obvious domain for additionalProperty....

[github-actions[bot]]

This issue is being nudged due to inactivity.

[roblinksdata]

I've found that https://validator.schema.org does not complain about schema:additionalProperty on classes where it isn't defined, such as schema:Dataset.

I tested the following snippet in https://validator.schema.org and found that it passes validation, which seems curious to me since other non-schema-compliant properties appear to raise warnings or errors.

Is this expected behaviour?

{
    "@context": "https://schema.org/",
    "@type": "Dataset",
    "name": "HOT: Niskin bottle samples",
    "description": "Something, Something, Something, Something, Something, Something, Something, Something, Something",
    "additionalProperty": {
        "@type": "PropertyValue",
        "propertyID": "https://dbpedia.org/page/Spatial_reference_system",
        "value": "https://www.w3.org/2003/01/geo/wgs84_pos"
    }
}

[pbuttigieg]

+1 from IOC UNESCO's Ocean Data and Information System application case

[fthobe]

+1

[tahirawan077]

+1 Also if its allowed on purpose whats the reason behind it? How is addidtionalProperty different from the others?

[philbarker]

Also if its allowed on purpose whats the reason behind it? How is addidtionalProperty different from the others?

It allows you to include a property that is not part of schema.org (and therefore not guaranteed to be understood by tools and apps that use schema.org).

It may be useful for microdata or if you treat JSON-LD as just being JSON, but there are better ways of doing this for properties from RDF/Linked Data vocabularies---just include the relevant namespace and in JSON-LD add what you need to the context, see for example this on the JSON-LD playground https://tinyurl.com/2adv7z79 .

[github-actions[bot]]

This issue is being nudged due to inactivity.