000 03983nam a22005535i 4500
001 978-3-031-79444-5
003 DE-He213
005 20240730163600.0
007 cr nn 008mamaa
008 221102s2013 sz | s |||| 0|eng d
020 _a9783031794445
_9978-3-031-79444-5
024 7 _a10.1007/978-3-031-79444-5
_2doi
050 4 _aQA1-939
072 7 _aPB
_2bicssc
072 7 _aMAT000000
_2bisacsh
072 7 _aPB
_2thema
082 0 4 _a510
_223
100 1 _aSwartz, Aaron.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_979341
245 1 0 _aAaron Swartz's The Programmable Web
_h[electronic resource] :
_bAn Unfinished Work /
_cby Aaron Swartz.
250 _a1st ed. 2013.
264 1 _aCham :
_bSpringer International Publishing :
_bImprint: Springer,
_c2013.
300 _aIV, 64 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
490 1 _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.".
650 0 _aMathematics.
_911584
650 0 _aInternet programming.
_935503
650 0 _aApplication software.
_979342
650 0 _aComputer networks .
_931572
650 0 _aOntology.
_95277
650 1 4 _aMathematics.
_911584
650 2 4 _aWeb Development.
_935505
650 2 4 _aComputer and Information Systems Applications.
_979343
650 2 4 _aComputer Communication Networks.
_979344
650 2 4 _aOntology.
_95277
710 2 _aSpringerLink (Online service)
_979345
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783031794438
776 0 8 _iPrinted edition:
_z9783031794452
830 0 _aSynthesis Lectures on Data, Semantics, and Knowledge,
_x2691-2031
_979346
856 4 0 _uhttps://doi.org/10.1007/978-3-031-79444-5
912 _aZDB-2-SXSC
942 _cEBK
999 _c84764
_d84764