https://schema.org/docs/schema_org_rdfa.html 404s

[mr-c]

No description provided.

[RichardWallis]

This is a consequence of some recent internal reengineering.
Did you follow a link to this file - if so can you tell where from.
Or have you previously used it - if so what is your use case.
~Richard

[mr-c]

Hello @RichardWallis

That URL (or the http version of it) was part of the recommended manner of using schema.org annotations in Common Workflow Languages files: https://github.com/search?l=Common+Workflow+Language&q=schema_org_rdfa.html&type=Code (1,454 results)

Now we recommend https://schema.org/version/latest/schema.rdf

FYI https://schema.org/version/8.0/ and similar (as linked to from https://schema.org/docs/releases.html ) also 404 now

[RichardWallis]

Thanks for the input @mr-c

I would recommend https://schema.org/version/latest/all-layers.rdf as it contains definitions for all schema.org terms, not just those in the core vocabulary.

I have raised an issue (#2594) for the 404 from https://schema.org/version/8.0/ , currently https://schema.org/version/8.0 works OK.

[stain]

The top of release documents like https://schema.org/version/8.0 also links to "Alternative formats: rdfa" like http://schema.org/docs/schema_org_rdfa.html so I expect loads of these links to that URL around the world, best to make it work again :)

[mr-c]

Thank you @RichardWallis , can you make the advice about which RDF file to link to explicit at https://schema.org/docs/developers.html ?

[mr-c]

For parsing speed, I think we will continue to recommend https://schema.org/version/latest/schema.rdf as the default ; users are welcome to use the expanded all-layers.rdf if needed

[stain]

Perhaps add links to the programmatically readable JSON-LD @context to https://schema.org/docs/developers.html now that the promoted @context: http://schema.org/ no longer points to the JSON-LD context. (see #2578)

[safo-bart]

Hi guys, I am maintaining one drupal page and it is using easyrdf PHP library. Now, some parts of the page are not working because removed subpage from schema.org. I think it influences more libraries :) Can you please return back subpage /docs/schema_org_rdfa.html ? thank you :)

Doctrine\Common\Proxy\Exception\InvalidArgumentException: Invalid uri + EasyRdf_Http_Exception: HTTP request for https://schema.org/docs/schema_org_rdfa.html failed: Not Found

[stain]

http://schema.org/docs/schema_org_rdfa.html also referenced from https://schema.org/version/7.04/ and many other places, so I think it needs to be reinstated.

https://schema.org/docs/datamodel.html lists that URL as "canonical machine representation of schema.org"

[danbri]

the page at the other end of the URL encoded the canonical ground truth of schema.org in triples; I don't think we committed to the URL or the file format in perpetuity. But it would be good to redirect the URL somewhere or put up a page explaining the situation...

[stain]

Perhaps redirect it to the last known RDFa version which can have a HTML banner on it. I don't suggest moving back to editing RDFa as the Turtle is so much easier!

[danbri]

@stain it looks like the links in the datestamped releases should be pointing to schema.rdfa in the same directory, and not to the non-datestamped URL under discussion here. For example, https://schema.org/version/7.04/schema.rdfa /cc @RichardWallis

[RichardWallis]

@danbri
We have a few options here:

1. Do nothing and accept this as a, now, historical anomaly.
2. Go through all the old releases and manually correct the link to be version specific.
3. As @stain suggests, redirect to the last known version, with added explanatory html banner added.
4. As schema.rdfa is no longer (post V8.0) shipped; put a holding document in its place describing how to find the historical versions and how to obtain other data dumps (eg. schema.ttl, all-layers.ttl) as a replacement.

(my preference is for option 4.)

[danbri]

Yes, (4.) makes sense. We should guide people away from the RDFa. It is almost always not what people need.

It would be good to make sure the Github release tags are all in place too, so we can link to them (or even use Github Releases machinery) from docs/releases.html

[RichardWallis]

@danbri
OK I'll create a PR to do 4.
On the releases stuff I'll do a bit of digging that will hopefully lead to another PR.

[RichardWallis]

Fixed by issue #2656

[lutsik]

Sorry for a potentially inappropriate place to ask this, but can it be that https://schema.org/version/latest/schema.rdf is again broken? CWL workflows using it seem to have lots of problems.

[RichardWallis]

Hi Pavlo, The *schema.rdf* file you reference has not been part of the Schema.org release since the version 9.0 <https://schema.org/docs/releases.html#v9.0> release in July 2020, when the rationalisation of dump files <https://schema.org/docs/releases.html#v9.0> took place. ~Richard.

…

On Thu, 18 Mar 2021 at 09:08, Pavlo Lutsik ***@***.***> wrote: Sorry for a potentially inappropriate place to ask this, but can it be that https://schema.org/version/latest/schema.rdf is again broken? CWL workflows using it seem to have lots of problems. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2593 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADFS2TQC7NBCVUBIV2QPNBDTEG7HVANCNFSM4NQP56ZQ> .