-
Notifications
You must be signed in to change notification settings - Fork 321
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
Use @id instead of custom ID properties #1
Comments
trieloff
pushed a commit
that referenced
this issue
Jan 5, 2018
#Issue 44: dc:format is missing a type declaration
saurabhere
pushed a commit
to saurabhere/xdm
that referenced
this issue
Mar 29, 2018
salilkanetkar
pushed a commit
to salilkanetkar/xdm
that referenced
this issue
Apr 27, 2018
Change capping-constraint schema
kstreeter
pushed a commit
that referenced
this issue
Jun 29, 2018
Merge dmitry-shkolnik/offer-management
fmeschbe
pushed a commit
that referenced
this issue
Jul 14, 2018
fmeschbe
pushed a commit
that referenced
this issue
Jul 14, 2018
kstreeter
pushed a commit
that referenced
this issue
Mar 28, 2019
reverse merge from master branch of xdm
DennisKehrig
pushed a commit
to DennisKehrig/xdm
that referenced
this issue
Sep 26, 2019
Merge from origin/master
ghost
mentioned this issue
Feb 18, 2023
mjasrotia
pushed a commit
that referenced
this issue
Nov 21, 2023
anandphatak
pushed a commit
that referenced
this issue
Mar 21, 2024
…ney (#1) * Added segment ID * Update journeyOrchestrationServiceEventsDispatcher.example.1.json * Update journeyOrchestrationServiceEventsDispatcher.schema.md * Update journeyOrchestrationServiceEventsDispatcher.schema.json * Update journeyOrchestrationServiceEventsDispatcher.schema.md * Update journeyOrchestrationServiceEventsDispatcher.schema.json * Update journeyOrchestrationServiceEventsDispatcher.schema.json
anandphatak
pushed a commit
that referenced
this issue
Dec 2, 2024
feat: algolia profile/event field groups
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we rely on JSON-LD semantics more heavily (see also #43), I thought it made sense to follow JSON-LD conventions when it comes to IDs and:
@id
property to identify the current object,instead ofin addition to*_id
properties that differ from schema to schemaThis pull request applies this convention to the
asset
schema category.The text was updated successfully, but these errors were encountered: