We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "id" property is defined in schema.org / JSON-LD as a URI, however the RPDE spec defines "id" as the native system ID.
schema.org uses "identifier" to reference the native system ID.
This has the potential to create confusion when JSON-LD is embedded in RPDE as there are two "id" properties for the same item with different values.
Should the next version of RPDE use "identifier" instead of "id" for consistency?
The text was updated successfully, but these errors were encountered:
Now depends on openactive-archive/opportunity-api#10
Sorry, something went wrong.
No branches or pull requests
The "id" property is defined in schema.org / JSON-LD as a URI, however the RPDE spec defines "id" as the native system ID.
schema.org uses "identifier" to reference the native system ID.
This has the potential to create confusion when JSON-LD is embedded in RPDE as there are two "id" properties for the same item with different values.
Should the next version of RPDE use "identifier" instead of "id" for consistency?
The text was updated successfully, but these errors were encountered: