I was looking in https://developers.coinbase.com/api/v2#introduction to see if there is any Swagger file for Coinbase API but did not find anything.
I found an unofficial one:
https://github.com/CoinFabrik/coinbase-api-swagger
I've no idea how accurate and/or up-to-date it is.
Related
I am currently in the process of choosing a technology/format to expose my API. It seems there are lots of discussion on this topic, but could not find the one for future use. I am planning to use Hydra:
http://www.markus-lanthaler.com/hydra
as it seems to be fully restfull (hypermedia api) but it seems it is not accepted yet (neither HAL is).
when I go to : http://www.markus-lanthaler.com/hydra/api-demo/vocab, I get a json that seems to be what swagger returns.
my questions:
- is Hydra Documentation meant to be sthg like swagger
- could find any tool for it like swagger has.
- I would prefer using Hydra as it seems it has more description on operations... by using json-ld, but it does not seem to be as supported as Hal or swagger is.
-does anyone have experience with hydra
Great that you consider using Hydra. You are right, we do not have extensive tooling yet but that's just a matter of time. In fact, I'm already working on a documentation generator. If you have further questions regarding Hydra, please don't hesitate to post to our mailing list. There are a lot of people on that list that will be happy to help.
I'm looking for an efficient way to generate API documentation in a readable format, from the generated files from Cloud Endpoint (Java). The generated files are either:
- my_api.api
- my_api*.discovery
Something that looks like this:
- https://github.com/kevinrenskers/raml2html#example-output
Swagger, API blueprint and RAML are all nice options, but don't seem adapt well to endpoint generated API descriptor files.
What methods are you using?
Unfortunately we (Apiary) do not actually offer any code generation tool at the moment for API Blueprint.
If you are looking for a way how to generate a description of your API from the code then API Blueprint isn't probably the best choice as we believe it should represent the contract between everybody involved in the API design lifecycle. This is also the reason why we have built the testing tool – Dredd – https://github.com/apiaryio/dredd
With Dredd you can test your API implementation is matching to your blueprint. It wouldn't make much sense if the blueprint would be generated from the implementation.
Hope it clarifies.
Firstly, I'd like to know how to find this out for myself next time. If not, then can somebody tell me?
The reason I want to know is because I want to use the #JsonIdentityInfo annotation on my Cloud Endpoints entities to deal with recursive serialization, but it doesn't compile. I guess this would mean it's some Jackson version less than 2.0.
You should not use repackaged libs - they are for internal GAE use only. They are not part of official API and can change at any time.
Include your own Jackson jar in your project.
Like Peter says, include your own Jackson jar. Make your code use this Jackson library. GAE will use their repackaged JSON parser or whatever they change it to (even not necessarily Jackson). That is of no concern to your project. GAE has no reason to look for Jackson annotations on your Entity classes - only your source code should tell only your Jackson jar to do that.
I'm trying to understand how to use Json-RPC calls in Google Go that would be used in a Google App Engine app. So far I understand that I somehow should call rpc.Client.Dial, but I don't understand what the "network" and "address" parameters should be. Can anyone provide a sample, working code that demonstrates how to use Json-RPC in Go?
I have already written an answer to your question on the go-nuts group, but for completeness, here it is:
Go's jsonrpc package isn't compatible with GAE yet.
Reference: https://groups.google.com/d/msg/google-appengine-go/uQ0cv0m9j0E/H3VCrFgEWvcJ
It's probably a good idea to read the full thread there, since it describes the limitations on GAE nicely and links to a patched library with lots of workarounds... The issue is already known, but has not been solved yet.
I'm really interested in being able to annotate my data. I am not really sure where to start, so I thought of using Apache Uima with Solr. I'm not sure if I'm no the right path, yet. Anyhow, I'm looking for some good documentation on this component called Solr-Uima
http://code.google.com/p/solr-uima/
Thanks,
J
I have no idea what UIMA is, but when I can't find any docs I read the tests. If the tests are not enough I read the code itself. (sorry if this is a generic answer, but this code doesn't seem to be too difficult to follow, so I really think it's a viable option).
The former project on Google Code has been contributed to Lucene / Solr codebase.
There is a wiki page, but needs to be updated.