Skip to content

Latest commit

 

History

History
94 lines (48 loc) · 2.21 KB

uris-with-issues.md

File metadata and controls

94 lines (48 loc) · 2.21 KB

Suggestion: give users the possibility to see the raw payload returned by the server (in case of error but also in normal cases). Could add "Right-click and select "View Page Source" for RDF document as returned by the server".

from https://elias.kaerle.com/annotating-a-hotel-offering-rooms-with-the-new-schema-org-version-3-1/

but https://search.google.com/structured-data/testing-tool shows the JSON-LD?

With activated plugin leads to problems (see above)

Same as above. Suggestion: detect XHR requests and do not modify resulting documents (probably used in background tasks and never displayed).

Needs HTML-escape of literals

URIs with &

Probably also needs HTML-escape of & in URIs

Does not parse...

works, but not http://www.w3.org/ns/sosa/Observation.

does not render Turtle, server provides file as "text/xml".

Maybe have a button to send a "shame-ping" to a list of incorrectly served RDF files?

But rapper parses the document fine?

But rapper parses the document fine?

But rapper parses the document fine?

But rapper parses the document fine?

But rapper parses the document fine?

Some prefixes are not correctly recorded, e.g., @prefix comment: rdfs:comment .

Times out?

Invalid URI?

Creates a blank node NaN?

Redirects to a HTML page?

Redirects to a HTML page?

Invalid URI?

Invalid URI?

Is a website...