Title: Re: [backstage] Web2.0 - tennets, rules, development philosophy...I'd love you to give us some feedback
Kim,
I was sitting in a meeting at Microsoft a few months ago when someone from Redmond used the BBCs site to explain RSS to a bunch of other Microsoft people that page
Title: Re: [backstage] Web2.0 - tennets, rules, development philosophy...I'd love you to give us some feedback
Hi all,
This is my first post to the list but I have enjoyed this thread so wanted to contribute. Im an ASP.NET developer and Im heavily involved with the Microsoft Development
On Mon, 17 Jul 2006, Matthew Somerville wrote:
[...] Amazon launched their web services in
2002, and I remember mash-ups being created back then - e.g. Amazon Light.
I was mashing up Gopher interfaces mining into our text based BLS
OPAC at the University back in 92/93. Is that too old skool?
Daniel Morris wrote:
Firstly, the list seems fairly comprehensive and easy to read.
Secondly, apologies if there are obvious answers to this email, i'm new...
How come REST API gets mentioned, but ajax doesn't?
I know ajax is an overused buzzword at the moment, but it is
unavoidably
At 09:10 +0100 17/7/06, Daniel Morris wrote:
Hi,
Client Side
Technologies used appropriately
e.g.. Flash elements on pages, not flash pages
Flash content should be sub-addressable?
Also, tables for tabular data.
I'll try and come up with more suggestions later :-)
-dan
AJAX for
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luke Dicken
Sent: 17 July 2006 10:57
To: backstage@lists.bbc.co.uk
Subject: Re: [backstage] Web2.0 - tennets, rules, development
philosophy... I'd love you to give us some feedback
AJAX is a language/technology not an API - HTML doesn't get
Phil Whelan wrote:
Web 2.0 for me is the movement of the web from something you read to
something you participate in, and the new web-communities helping to
build sites with which they have an interest. This is enabled by new
technologies such as blogs, readers leaving comments, voting,
Listening to a podcast last week, Gillmor Daily, here the argument being advanced was that web 2.0 was a fairly misleading term and one to avoid. It was argued that the real change occured around 2001 with XML and more recently RSS.
The community argument doesn't ring true for me, though I wish it
Kim Plowright wrote:
I'd be really interested to hear what everyone here thinks. Am I missing things?
It reads like a very good list, certainly... of what I'd expect *any*
website to do! :-) Perhaps it's just me and the whole Web2.0 blah, but
certainly anything in the Code section (apart
Kim
Lots of good stuff in there.
On 14 Jul 2006, at 17:08, Kim Plowright wrote:
Common Engines
APIs
* REST for Quick, light and elegant
1 SOAP for the heavy corporate lifting
Maybe I'm reading more into this than you meant to imply but I think
it's a mistake to assume that REST can't
Matthew Somerville wrote:
new technologies? Blogs (including online diaries) that you can
leave comments on have been around since 1998; RSS 1999. Wikipedia
launched in 2001. XMLHTTP was invented by Microsoft for Outlook Web
Access 2000. eBay launched its API in November 2000, Amazon launched
At 11:49 +0100 17/7/06, Richard Hyett wrote:
Listening to a podcast last week, Gillmor Daily, here the argument
being advanced was that web 2.0 was a fairly misleading term and one
to avoid. It was argued that the real change occured around 2001
with XML and more recently RSS.
The community
2006 10:57
To: backstage@lists.bbc.co.uk
Subject: Re: [backstage] Web2.0 - tennets, rules, development
philosophy... I'd love you to give us some feedback
Daniel Morris wrote:
Firstly, the list seems fairly comprehensive and easy to read.
Secondly, apologies if there are obvious answers
Maybe I'm reading more into this than you meant to imply but
I think it's a mistake to assume that REST can't scale and
that SOAP is required for 'serious' work. Arguably REST
scales _better_ than SOAP.
Apparently; querying Amazon using REST is 6 times faster than with
SOAP [1]
There
On 17 Jul 2006, at 14:40, Kim Plowright wrote:
- AJAX is more than just a scripting language; it too can be the
'appropriate technology' for an API
Umm, to a techie that's a bit confused:
* Ajax isn't a scripting language, Javascript is (the 'j' in Ajax).
* An 'Ajax' API doesn't really make
Way back in the mists of the late 20th century I attended a meeting with
someone from Factual and Learning about the Digital Curriculum - at a time
when it was still a thought. We suggested that it would be really useful if
teachers could take the content that the BBC produced and re-arrange it
to
To: backstage@lists.bbc.co.uk
Subject: RE: [backstage] Web2.0 - tennets, rules, development
philosophy... I'd love you to give us some feedback
Way back in the mists of the late 20th century I attended a meeting with
someone from Factual and Learning about the Digital Curriculum - at a
time when
Hi Kim,
I have read all the replies, and I must say, as an outsider to the BBC and the
Web2 concept... that the technical jargon in the list is overwhelming and
therefore confusing to me. I respect the fact that my point of view is
therefore pretty unenlightening, but it would seem that the
HTML
- At the root of everything, standards compliant, with presentation
separate from content.
HTML? You mean I to switch back from XHTML? Since when?!??!
:-)
Gordo
--
Think Feynman/
http://pobox.com/~gordo/
[EMAIL PROTECTED]///
-
Sent via the backstage.bbc.co.uk discussion
Quoting Kim Plowright [EMAIL PROTECTED]:
AJAX
- Is currently the best way to build responsive, in-browser application
like experiences for performing actions on data*
- AJAX is more than just a scripting language; it too can be the
'appropriate technology' for an API
Hmn. AJAX is a good
Richard Lockwood wrote:
I think you've hit the nail on the head Kim. Web 2.0 is buzzwords,
buzzwords, and more buzzwords, but ultimately, means nothing.
Services, not packaged software, with cost-effective scalability
Control over unique, hard-to-recreate data sources that get richer
as
21 matches
Mail list logo
