Dan Brickley

Schema.org moving from HTTP Content Negotiation to JSON-LD 1.1 "Link:" header for context file

9

This happened faster than planned due to a DOS attack this week, details in https://github.com/schemaorg/schemaorg/issues/2578#issuecomment-632227864 Schema.org no longer publishes a JSON-LD context file using HTTP content negotiation. Our homepage URL...

Consider a mechanism for including content from surrounding document

2

_This is a "what do you think about this" enquiry rather than a fully polished proposal._ At Google we have come to recommend JSON-LD within HTML, for structured data (schema.org...

LICENSE file?

1

This is neat! It would be great if you added a license file that encourages opensource collaboration on this stuff - apache2 etc

[HTML] Add Schema.org and other inline rdf support

12

A great many pages contain RDF data via Schema.org (in microdata, json-ld, rdfa). There are also other vocabularies which uses those syntaxes. Does SPARQL Anything represent that data naturally, or...

Current demo validates differently between shex and shacl (e.g. schema.org Event and Recipe samples)

3

Relaying [from Aaron](https://twitter.com/aaranged): > I pasted the first [http://schema.org/Event](https://t.co/zny2hY4iH4) example into the tool and it passed as error free with ShEx validation, but generated 4 errors with SHACL... (I have...

Stretch goal: Consider supporting Dublin Core CSV format

2

I believe there is code out there to auto-generate SHACL, and maybe ShEx too. * https://www.dublincore.org/resources/glossary/shape_expression/ * https://github.com/dcmi/dctap/blob/main/examples/CourseSchemaOrgAP/courseSchemaOrgAP.csv * https://dctap-python.readthedocs.io/en/latest/ /cc @tombaker

Validator demo site (and API) should expose version numbers for the frontend, supported schema versions/dates/release, and shex + shacl inputs

2

These should also be html visible somewhere, but for now it would be good to know how to go to https://google.github.io/schemarama/demo/ or whatever, and pop up browser devtools and quickly...

Figure out best pattern for linking from bits of ShEx (smaller than shapes) to documentation URLs

1

For a concrete example, consider https://github.com/google/schemarama/blob/main/demo/validation/shex/specific/ServiceB/Dataset.shex which was in fact based on Google's [rules](https://developers.google.com/search/docs/advanced/structured-data/dataset) for describing datasets to Google Dataset Search. This all got anonymized for the opensource launch here...

Figure out a pattern for cutting down noisy validation errors

3

I forget the terminology, but the AND/NOT/OR complexity here serves to suppress errors that are downstream of some more fundamental error. @ericprud et al have plans for doing this within...