Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

API Property Types #44

Open
kinlane opened this Issue Jun 30, 2014 · 4 comments

Comments

Projects
None yet
2 participants
Contributor

kinlane commented Jun 30, 2014

Here are my suggestions for next round of API property types:

GettingStarted
FrequentlyAskedQuestions
Signup
BestPractices
ServiceAccord
Documentation
Explorer
ErrorCodes
AuthenticationOverview
AuthenticationTester
CodeLibraries
ApplicationGallery
SoftwareDevelopmentKits
StackExchange
Calendar
OfficeHours
Blog
BlogRSS
LinkedIn
Twitter
Github
Facebook
GooglePlus
Roadmap
ChangeLog
RateLimits
Affiliate
Advertising
CaseStudies
WhitePapers
HowToGuides
Webinars
Ideas
Labs
Opportunities
Branding
PrivacyPolicy
ServiceLevelAgreement
DataLicense
CodeLicense
DeprecationPolicy
Widgets
Buttons
Badges

Contributor

kinlane commented Jul 9, 2014

These are priorities I feel:

GettingStarted
Signup
Documentation
ErrorCodes
AuthenticationOverview
AuthenticationTester
CodeLibraries
ApplicationGallery
SoftwareDevelopmentKits
Blog
BlogRSS
LinkedIn
Twitter
Github
Facebook
GooglePlus
RateLimits
ServiceLevelAgreement
DataLicense
CodeLicense

Contributor

kinlane commented Jul 16, 2014

To accepted by next version:

currently have:

Swagger
RAML
Blueprint
WADL
WSDL
TermsOfService
InterfaceLicense
StatusPage
Pricing
Forums
AlertsTwitterHandle

add next round:

GettingStarted
Signup
Documentation
ErrorCodes
AuthenticationOverview
AuthenticationTester
CodeLibraries
ApplicationGallery
SoftwareDevelopmentKits
Blog
BlogRSS
LinkedIn
Twitter
Github
Facebook
GooglePlus
RateLimits
ServiceLevelAgreement
DataLicense
CodeLicense
APICommonsManifest

Contributor

kinlane commented Sep 29, 2014

Adam Avilla adam@avil.la via googlegroups.com - Sep 24

We are looking to incorporate this for an internal API search engine (company specific APIs) and have identified some fields that we would like to store. I would like to hear your suggested data models for them or if I can contribute to specifying them.

Need:

  • URI Port
  • Source code link
  • Code version
  • Last time deployed
  • Software dependencies
  • Ticket tracking URL

Mostly all of these would be optional. Let me know if there are more questions or if I can be more specific.

Thanks Kin.

@kinlane kinlane added the question label Feb 9, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment