-
Notifications
You must be signed in to change notification settings - Fork 132
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
Intent naming conventions #681
Labels
Context Data & Intents
Contexts & Intents Discussion Group
enhancement
New feature or request
intents
Milestone
Comments
kriswest
added
intents
Context Data & Intents
Contexts & Intents Discussion Group
labels
Apr 28, 2022
24 tasks
My two cents:
|
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Context Data & Intents
Contexts & Intents Discussion Group
enhancement
New feature or request
intents
Enhancement Request
Provide guidance on the naming of intents.
View____
andStart____
are the existing conventionsSubmitted on behalf of Riko Esteen (@rikoe )
Use Case:
As the FDC3 standard matures, more use cases will evolve in turn identifying new intents that need to be created. This issue has been raised to provide guidance on the naming of those intents.
New proposed conventions:
Create
/Update
/CreateOrUpdate
for e.g. orders, RFQsDelete
Get
(for two-way intents)Share
The text was updated successfully, but these errors were encountered: