000			03554nam a22003975i 4500
999			_c387112 _d387112
001			387112
003			ES-MaUEC
005			20230225111643.0
006			a||||fo|||| 00| 0
007			cr nn 008mamaa
008			230225s2013 sz | s |||| 0|eng d
020			_a9783031794445
024	7		_a10.1007/978-3-031-79444-5 _2doi
040			_aES-MaUEC _bspa _cES-MaUEC _dES-MaUEC
050		4	_aTK5105.88815 _b2013 EB
100	1		_aSwartz, Aaron, _eautor _4aut _4http://id.loc.gov/vocabulary/relators/aut _9687105 _d1986-2013
245	1	0	_aAaron Swartz's The Programmable Web : _bAn Unfinished Work _cby Aaron Swartz
250			_a1st edition 2013
264		1	_aCham _bSpringer International Publishing _c2013
300			_a1 recurso en línea (IV, 64 páginas)
336			_atexto _btxt _2rdacontent
337			_aelectrónico _bc _2rdamedia
338			_arecurso electrónico _bcr _2rdacarrier
347			_aarchivo de texto _bPDF
490	0		_aSynthesis Lectures on Data Semantics and Knowledge _x2691-2031
505	0		_aIntroduction: A Programmable Web -- Building for Users: Designing URLs -- Building for Search Engines: Following REST -- Building for Choice: Allowing Import and Export -- Building a Platform: Providing APIs -- Building a Database: Queries and Dumps -- Building for Freedom: Open Data, Open Source -- Conclusion: A Semantic Web?.
520			_aThis short work is the first draft of a book manuscript by Aaron Swartz written for the series "Synthesis Lectures on the Semantic Web" at the invitation of its editor, James Hendler. Unfortunately, the book wasn't completed before Aaron's death in January 2013. As a tribute, the editor and publisher are publishing the work digitally without cost. From the author's introduction: " . . . we will begin by trying to understand the architecture of the Web -- what it got right and, occasionally, what it got wrong, but most importantly why it is the way it is. We will learn how it allows both users and search engines to co-exist peacefully while supporting everything from photo-sharing to financial transactions. We will continue by considering what it means to build a program on top of the Web -- how to write software that both fairly serves its immediate users as well as the developers who want to build on top of it. Too often, an API is bolted on top of an existing application, as an afterthought or a completely separate piece. But, as we'll see, when a web application is designed properly, APIs naturally grow out of it and require little effort to maintain. Then we'll look into what it means for your application to be not just another tool for people and software to use, but part of the ecology -- a section of the programmable web. This means exposing your data to be queried and copied and integrated, even without explicit permission, into the larger software ecosystem, while protecting users' freedom. Finally, we'll close with a discussion of that much-maligned phrase, 'the Semantic Web,' and try to understand what it would really mean.".
988			_aSynthesis Collection of Technology_2013
650		7	_2embne _9163805 _aWeb semántica
776	0	8	_iPrinted edition: _z9783031794438
776	0	8	_iPrinted edition: _z9783031794452
856	4	0	_uhttps://go.openathens.net/redirector/universidadeuropea.es?url=https://doi.org/10.1007/978-3-031-79444-5 _zAcceso a este recurso digital (usuarios Universidad Europea de Madrid)
942			_2lcc _cLE
998			_b02/2023 _dz _eIG _zSI