W3C home > Mailing lists > Public > www-archive@w3.org > February 2007

[wbs] response to 'Standardizing a Semantic Web API for Javascript'

From: WBS Mailer on behalf of <webmaster@w3.org>
Date: Fri, 16 Feb 2007 01:10:01 +0000
To: www-archive@w3.org
Message-Id: <wbs-7a7a9fda2e400d39876a593f32b7dedc@cgi.w3.org>


The following answers have been successfully submitted to 'Standardizing a
Semantic Web API for Javascript' (the public) for  by .



---------------------------------
Should W3C Do This?
----
Should W3C work toward standardization of a Semantic Web API for
Javascript in browsers?



 * ( ) Yes
 * ( ) No - It's too early (ask again in a year or two)
 * (x) No - Someone should work on this, but not W3C
 * ( ) No - Other Reason (please explain)
 * ( ) Undecided

Rationale: 
The role of the W3C should be on usefully standardizing areas which (a)
already exhibit useful work, (b) would benefit from standardization, and
(c) are amenable to standardization because a fairly uniform set of
requirements can be identified.

I am yet to see any evidence for any of these points.




---------------------------------
Timeline
----
If W3C does this work, what should the timeline be?   There is probably a
natural tradeoff between speed and quality -- a vote for speed is a vote
for accepting a lower-quality first version.


 * ( ) One Year -- get something out fast!

 * (x) Two Years

 * ( ) Three years -- take your time...






---------------------------------
Your Identity
----
If we publish the results of this survey, how should be identify you?   
If you leave this question blank, your answers will be kept anonymous.

If you are using the public version of this form, for which you do not
need to log in, you were asked about your name and employer, above.  That
information will always be kept confidential.   Similarly, if you are
logged in, our system has a record of your name, etc.   That information
will not be used for any results we publish -- instead, we will use the
information you provide below, if any. 

This question is optional.   We may publish any information you provide
here.
Your Name : Richard Newman
Your E-Mail Address : 
Your Website Address: 




---------------------------------
Language Plans
----
In what languages, if any, do you seriously anticipate implementing
Semantic Web software over the next two years?



 * [ ] C
 * [ ] C#
 * [ ] C++
 * [ ] Cobol
 * [ ] Cold Fusion
 * [x] Common Lisp
 * [ ] Haskell
 * [ ] Java
 * [x] Javascript / ECMAScript
 * [ ] .Net/Mono
 * [ ] PHP
 * [ ] Perl
 * [ ] Prolog
 * [ ] Python
 * [ ] Ruby
 * [ ] Scheme
 * [ ] Visual Basic / ASP
 * [ ] XSLT
 * [ ] XQuery
 * [ ] Other (details in Comments)

Comments (or a URI pointing to your comments): 
In my scenario, Javascript is only used as an AJAX glue between
server-side manipulations. No meaningful manipulation of RDF is expected
to be done in the browser. If this invalidates my selection of Javascript,
please disregard that selection.




---------------------------------
Developer Experience - Javascript
----
Please describe your experience and expertise, if any, in developing
software in Javascript

Comments (or a URI pointing to your comments): 
I've developed multiple AJAX and plain Javascript applications, from basic
enhancement of HTML through to dynamic all-Javascript, highly-coupled tree
editors. I have also generated Javascript programmatically.




---------------------------------
Developer Experience - as Semantic Web API user
----
What Semantic Web APIs/Toolkits have you used? 

Some lists of systems are available from Bizer and Westphal,
ESW-Wiki, and
PlanetRDF.  If you refer to systems not listed there, please include a URL
or other explanation.

Comments (or a URI pointing to your comments): 
Wilbur, AllegroGraph, Kowari, Jena, Sesame (including implementing the
HTTP API), cwm, TopBraid Composer, Redland, Protege, probably others at
one time or another.




---------------------------------
Developer Experience - as Semantic Web API developer
----
What Semantic Web APIs/Toolkits have you created or maintained? 

Some lists of systems are available from Bizer and Westphal,
ESW-Wiki, and
PlanetRDF.  If you refer to systems not listed there, please include a URL
or other explanation.

Comments (or a URI pointing to your comments): 
Wilbur (URIQA and SPARQL implementations, miscellaneous additions),
AllegroGraph. I have also written a Cocoa wrapper for Redland for my own
use, and ad hoc Python tools.




---------------------------------
Candidates and Features
----
Would you recommend any particular API/Toolkit as a starting point for
this work?

Do you have any features or design approaches which you would strongly
recommend?

Comments (or a URI pointing to your comments): 
I thought the W3C was "beginning to consider whether to start a Working
Group", not wondering which toolkit to use!

If I were to approach this, my main concern would be to idiomatically
follow Javascript where it joins well to RDF -- objects do not have
strictly defined attributes, as in mainstream OO languages.




---------------------------------
Expected Participation
----
In what way(s) do you expect you would be involved?




 * ( ) I am currently associated with a W3C member, and I expected I would
join the Working Group
 * ( ) I expect to be able to get my organization to join W3C, and then I
will join the Working Group
 * ( ) I hope to find a way to join the Working Group, even though I do
not expect to be sponsored by a W3C member.
 * (x) I do not expect to join, but will follow the work of the Working
Group, reading drafts and offering comments.
 * ( ) I do not expect to participate in this work.

Comments (or a URI pointing to your comments): 




Answers to this questionnaire can be set and changed at
http://www.w3.org/2002/09/wbs/1/semweb-js-api/ until 2007-03-15.

 Regards,

 The Automatic WBS Mailer
Received on Friday, 16 February 2007 01:10:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:02 GMT