[Developers] Metaweb Perl module

[Shawn Simister]

Hi Kirsten,

I agree that a common base would be a good idea even if it just starts 
off as a very small set of features.
So far, in developing a Ruby module for Metaweb, I have been building on 
the following core concepts:

ReadService.read(queries)
WriteService.authenticate(host, user, password)
WriteService.write(queries)

As each layer of abstraction is added, the API becomes more language 
specific so at some point there will be certain features that Ruby can 
do but more rigid languages like Java couldn't. Still, I think there is 
enough overlap to warrant a common knowledge base of source code and 
best practices for API developers. Each API would be allowed to grow 
organically while maintain compatibility with Metaweb Core 1.0 (for 
example).

Can anyone from Metaweb comment on if Metaweb would want to get involved 
in a standard like this?

Shawn Simister

Kirsten Jones wrote:
> All,
>
> I'm just about ready to start working with Hayden's perl module, and  
> had some thoughts I wanted to bounce off of the rest of you.
>
> On the more general topic of modules, I'd really love for the  
> developer community to come up with a set of guidelines for client  
> libraries for Metaweb.  Each language's library might well have  
> additional functionality, but I'd love to define what the 'base  
> functionality' for each library should be.  Doing this will make it  
> easier for people to move among the various dynamic languages and  
> leverage off of other people's work in different languages to seed  
> their own applications.  It seems like it would also make it easier  
> to create the client libraries if some essential set of behaviors is  
> already specified.
>
> Metaweb is so flexible that I'm afraid if we *don't* come up with  
> something like this, the modeling in each language may end up being  
> radically different.
>
> Since I currently work at a wiki company, I was thinking of creating  
> a workspace for people who are interested in collaborating on what  
> these guidelines might be.  But I thought I'd start here and see what  
> people think - good, bad, indifferent?  There are certainly arguments  
> to be made for allowing these things to grow organically.
>
> Thanks,
> Kirsten
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers
>
>