0

3rd party tables

This is a great idea. I've had a go and created a definition for a small section of the Twitter API - http://hapdaniel.pwp.blueyonder.co.uk/pdan...yql/twitter.xml
I've also seen that there is the start of a general repository for table definitions - http://github.com/spullara/yql-tables/tree/master
But now I have some questions (in no particular order):
1. How do I add my definition to the github repository?
2. How could my definition be improved? For instance, my definition is specific to the Atom output for Twitter. Could this be broadened to RSS, XML and JSON output, and if so how?
3. How do I know if somebody else is already working on a definition?
4. What sort of naming convention should be used for the repository?
5. Is my definition good enough to be added to the repository?

I'm not necessarily expecting answers to these questions, but I do think that there are issues that need to be considered at some stage.

by
2 Replies
  • QUOTE (hapdaniel @ Feb 6 2009, 12:40 PM) <{POST_SNAPBACK}>
    This is a great idea. I've had a go and created a definition for a small section of the Twitter API - http://hapdaniel.pwp.blueyonder.co.uk/pdan...yql/twitter.xml
    I've also seen that there is the start of a general repository for table definitions - http://github.com/spullara/yql-tables/tree/master
    But now I have some questions (in no particular order):
    1. How do I add my definition to the github repository?
    2. How could my definition be improved? For instance, my definition is specific to the Atom output for Twitter. Could this be broadened to RSS, XML and JSON output, and if so how?
    3. How do I know if somebody else is already working on a definition?
    4. What sort of naming convention should be used for the repository?
    5. Is my definition good enough to be added to the repository?

    I'm not necessarily expecting answers to these questions, but I do think that there are issues that need to be considered at some stage.


    1. Send me a message on Github and I will add you.
    2. There is no reason to go after the other types if the data is all the same. We support XML and JSON as output types.
    3. Get yours into Github when you start and collaborate.
    4. I like service.apicategory.apiname -- I would probably name yours twitter.user.timeline
    5. Looks like a good start!

    Sam
    0
  • Wow awesome job! You did that really fast.
    0

Recent Posts

in YQL