Skip to content

Create SPECIAL_INTEREST_GROUPS #2661

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

Closed
wants to merge 1 commit into from
Closed

Create SPECIAL_INTEREST_GROUPS #2661

wants to merge 1 commit into from

Conversation

ncaidin
Copy link
Contributor

@ncaidin ncaidin commented Jul 29, 2021

OpenAPI Initiative Special Interest Groups (aka SIGs)

To join go to https://join.slack.com/t/open-api/signup and create your account. If this does not work for any reason, please email operations@openapis.org for help, and specify which SIGs you would like to join or monitor.

Travel SIG

Discussion: Slack - #sig-travel
Purpose:

The Travel SIG will compile and present a collective representation of the API behaviors required by the travel industry documented in the form of use cases and workflows. This effort will include working with various established travel standards and trade association bodies using the Open Travel Alliance as a coordination point. Open Travel will moderate the various needs of sectors such as (but not limited to) air, hotel, car, cruise, rail, tours, distribution channels, etc. with a focus on enabling interoperability across the sectors. The standards bodies and trade associations will lead on what functionality is needed by their members. The Travel SIG will work with other OAI SIGs on how best to support the documented use cases and workflows. The intent here is to avoid duplication of SIG efforts and have the Travel SIG focus on what is needed and work with other SIGs on how to meet that need.

@MikeRalphson
Copy link
Member

@ncaidin to fit in with the rest of the markdown files in the repo (and to enable rich text previews etc) this file should have a .md extension. Is that easy for you to change? Alternatively (though it is not as neat), we could merge this and rename.

@ncaidin
Copy link
Contributor Author

ncaidin commented Aug 20, 2021

Makes sense that is should be an md file. I see a way to edit the text in the PR but not the file name. Another way would be for me to create a new PR with the right name and delete this PR.

@swaldron58
Copy link

Draft blog post for #sig-travel which also explains the role.
Travel Bliss From API Chaos.docx

@ncaidin ncaidin closed this Aug 27, 2021
@ncaidin
Copy link
Contributor Author

ncaidin commented Aug 27, 2021

Created a new PR - #2686
Made sure to include ".md" as part of the file name. Could not figure out how to easily change the filename in Github.

@ncaidin
Copy link
Contributor Author

ncaidin commented Oct 25, 2021

@3laoy26 , I'm not a git/github expert, but I thought I did do this on #2686 ?

If I did something wrong, maybe someone can help me to correct because I've already tried twice and apparently failed.

Copy link

@tg-bot-ap tg-bot-ap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gh pr checkout 2661

@handrews handrews deleted the ncaidin-patch-3 branch April 18, 2024 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants