Schema.org extension proposal

[myroslav]

The idea is to propose OCDS-based extension for schema.org, to enable web sites to mark up procurement information in HTML pages for data extraction by search engines and buildup of semantic web.

The closest initiative is schemaorg/schemaorg#448. The other issues that are already there and hosted by schema.org are:

• http://auto.schema.org/ - auto: Auto Extension, adds following childs to Vehicle: BusOrCoach, Motorcycle, MotorizedBicycle objects
• http://bib.schema.org/ - bib: Bibliographic Extension adds a lot of childs, grandchilds and other descendants to CreativeWork object.

Extension after adoption becomes part of the full hierarchy, select "Core plus all extensions" (note blue terms, they are from extensions).

The OCDS extension would allow search engines (and other data extraction and linking tools) extract information from sites publishing public procurement information. The stretch goal is to organize the extracted information into DBpedia, Freebase, etc. And the final goal is to have it all plugged into systems like Google Knowledge Graph, to increase accessibility of information.

[akuckartz]

I am interested in collaborating a bit in this effort.

[myroslav]

@akuckartz we have JSON Schemas. For instance see standard/schema/release-schema.json. Some of the objects already exist at schema.org, i.e. we'd have to reuse them. Is that possible to add extra properties to existing schema.org objects, or I'd have to generate descendant object and add the property there?

[timgdavies]

This is a really interesting idea - and would be really happy to support this.

What would it take to get an activity around this started?

[myroslav]

Regarding my question about adding properties to core schema.org objects.

I'd seen already extra properties that auto extension adds to Vehicle. See "Available properties in extensions" section and accelerationTime property as an example.

[myroslav]

Additionally see following issues regarding process of development and publishing the auto extension:

• Meta-Issue: Automotive Extension schemaorg/schemaorg#509: Meta-Issue: Automotive Extension
• auto.schema.org review tracking  schemaorg/schemaorg#704: auto.schema.org final review tracking

[AlCollier]

+1

On 11 September 2015 at 08:49, timgdavies notifications@github.com wrote:

This is a really interesting idea - and would be really happy to support
this.

What would it take to get an activity around this started?

—
Reply to this email directly or view it on GitHub
#242 (comment)
.

[timgdavies]

Ok. I had a brief chat with @JeniT to get some insights into this, and the main take-away I had from that is that this could be a good path to go down, but we should:

(a) Think about the proposition for search engines or other consumers of this data, and make sure we have this clear. Which platforms might display contract information, and what is the key information they would want to display?

(b) Think carefully about how to frame this as a complement to, rather than replacement for, publishing comprehensive OCDS;

I suspect taking this issue forward might also link with #40 around JSON-LD support for OCDS, as that will also involve us mapping from OCDS to existing vocabularies.

[elf-pavlik]

👍 http://blog.schema.org/2013/06/schemaorg-and-json-ld.html

many groups working on schema.org extensions also created Community Groups as W3C https://www.w3.org/community/ plus coordinate with http://www.w3.org/wiki/WebSchemas list

[timgdavies]

Has anyone been working on this? Any interest in future work on this?

[jpmckinney]

Closing as no strong or recent interest expressed.