-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
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
Emerging best practice is to use id/type aliases for @id/@type #88
Comments
And schema.org issue: schemaorg/schemaorg#854 |
And more, already accepted: hbz/lobid-organisations#51 |
👍 |
Just to clarify --- I felt I could reasonably add this into schema.org's context file implementation, in the spirit of https://en.wikipedia.org/wiki/Robustness_principle .... for people working with generic context-file JSON-LD tooling. However this is not the same as getting commitment from e.g. google/yahoo/microsoft/yandex that they'll accept this syntax variation, that is a longer conversation to have. I think it makes sense though. I'll continue investigating, and perhaps we'll see a stronger endorsement of this syntax style from the schema.org project. |
Would happily work to get this into the Activity Streams 2.0 |
👍 |
@jasnell 👍 happy to help make that happen. |
Also, this is "closed" via #89 & #90 -- list conversation not withstanding. We can reopen (imo) if/when there are reasons to revisit. Hope that's copacetic @azaroth42 😸 |
For reference, the AS document with the mapping (and maintaining @context):
Thanks to @jasnell :) |
From @msporny: Emerging best practice is to use id and type, not @id and @type. There has been agreement from schema.org (@danbri), and Social Web (@tantek)
This issue is to revert to the previous state where we did this.
The text was updated successfully, but these errors were encountered: