-
Notifications
You must be signed in to change notification settings - Fork 14
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
Schema.org OpenAPI Catalog #6
Comments
Will need to fit within requirement of being a "175 and 350-hour projects". |
Hello @jansche , I hope this message finds you well. I was wondering if you could clarify the qualification task that needs to be completed for this, as described in the CONTRIBUTOR_GUIDANCE, should i make a repo and try to make open api definitions for some schema.ord objects? and there seems to be a typo here , in remaining issues its mentioned as 18/18+ mentors and here 16 Thank you for your time and assistance. |
Hey Myself Manish. I am currently a Postman Student Leader and a junior developer pursuing my bachelor's in Computer Science and Engineering. As a developer, I am interested in this project because it can save a lot of time and effort when starting new APIs. By having an open catalog of OpenAPI definitions for each of the Schema.org objects, we can have a robust set of starting templates for designing new APIs, and ensure that they are developed using common standards and are interoperable. As a mentee, I would appreciate clear instructions and regular feedback from my mentors. I would also appreciate their availability for questions and support as I work on the project. As I work on this project, I plan to familiarize myself with the OpenAPI specification and Schema.org objects, and keep up-to-date with changes in these areas. I may also explore code used to generate OpenAPI definitions and see if there are ways to optimize it. Along with my studies As a developer, I like to keep myself organized using project management software. I also use version control systems, such as Git, to keep track of changes and collaborate effectively with my team members. I prefer to use collaborative platforms, such as Slack or Microsoft Teams, for communication and sharing resources. |
Hi, |
Hey! |
Hi @money8203 @Pavan-Nambi @yashm277 thank you for your interest in this project. We have now created a repository here: https://github.com/postman-open-technologies/schema-org-openapi-catalog Please look at the issues labelled "Good first issue" and consider taking on one or more of them as your qualifying task. You can comment on the issue with your findings and approaches, as well as asking questions. I look forward to your applications! |
Hello Guys!! |
@Himanshu-Dedha thanks! Link made absolute now. |
Hey folks, the Postman OSPO is live for a Google Summer of Code Q&A session. #gsoc |
Hey @MikeRalphson can I propose the proposal for combining the #6 and #8 project and working together ? Or do I need to submit individual proposal for each of them!! |
Hi @money8203 you can submit a proposal for the combined projects, but to maximise your chance of being selected, please complete a full section of your proposal for each project, so we could break it up if we need to. Thank you. |
Sure, thanks for the feedback! |
Hello there! While researching the Open API specification, I was immediately drawn to its potential to make API development more accessible and efficient. Contributing to this project would enable me to make a meaningful impact by simplifying the process for developers to start on any new API and save their valuable time. @MikeRalphson, I started analyzing the good first issues and will submit the proposal for the same soon. Thanks :) |
Hi @MikeRalphson, is there any other good first issue present to work or should I work on the ones which you have previously mentioned?
|
These are the only qualifying tasks. |
Okay, got it. I will also add my inputs there. |
Hi @MikeRalphson / @saialekhya-001 / @sourabhbagrecha, I want to understand a few things here:
|
"do we need to define OpenAPIs for the schema.org types itself?" Yes, this is the project goal. |
Alright! but I am reading this documentation which says this:
Reference: https://oai.github.io/Documentation/introduction.html |
@MikeRalphson, I dug dip and understood that though the schema.org types are not APIs we can still write the OpenAPI definitions to describe the structure of data that we want to exchange using those types. This can also help if one wants to create an API that uses Schema.org types to represent data. |
Closed as completed as part of 2023 edition. |
Summary: Create an open catalog of OpenAPI definitions for each of the Schema.org Types. Providing a robust set of starting OpenAPI templates for teaching or developing new APIs using a design-first approach. Helping save developers work when it comes to starting new APIs, but also help ensure APIs are developed using common standards and are as interoperable as possible.
Skills: Familiarity with the OpenAPI specification, and Schema.org Types.
Expected Outcomes: A public repository of up-to-date OpenAPI 3.1 definitions and validated JSON Schema instances for each of the Schema.org Types. You must share your code used to generate the output definitions, allowing them to be updated as schema.org Types evolve.
Mentors: @MikeRalphson + 1-2 additional mentors to be named.
Project Repo: https://github.com/postman-open-technologies/schema-org-openapi-catalog
Size of Project: 175h or 350h
Rating: Medium skills level
The text was updated successfully, but these errors were encountered: