REST, hypermedia, and the semantic gap: why "RMM-level3 REST" is not enough
"Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusabilit...
Gespeichert in:
| Weitere beteiligte Personen: | |
|---|---|
| Format: | Elektronisch Video |
| Sprache: | Englisch |
| Veröffentlicht: |
[Place of publication not identified]
O'Reilly Media
2015
|
| Schlagwörter: | |
| Links: | https://learning.oreilly.com/library/view/-/9781491936511/?ar |
| Zusammenfassung: | "Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusability of APIs. But what are Hypermedia APIs? What do they look like? And why are they "better" than the common CRUD APIs we all use today? This webcast illustrates the differences between CRUD and Hypermedia APIs and how you can design & implement clients and services that can take advantages of APIs based on hypermedia, not just resources and a tiny handful of verbs. Along the way, we'll look at working versions of both styles and get a chance to see why adding more hypermedia in service responses can result in more functionality on the client while reducing the amount of API-specific code on the client."--Resource description page. |
| Beschreibung: | Title from title screen (Safari, viewed August 25, 2015). - Date of publication taken from resource description page |
| Umfang: | 1 Online-Ressource (1 streaming video file (51 min., 2 sec.)) digital, sound, color. |
Internformat
MARC
| LEADER | 00000cgm a22000002 4500 | ||
|---|---|---|---|
| 001 | ZDB-30-ORH-047615052 | ||
| 003 | DE-627-1 | ||
| 005 | 20240228115929.0 | ||
| 006 | m o | | | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 191023s2015 xx ||| |o o ||eng c | ||
| 035 | |a (DE-627-1)047615052 | ||
| 035 | |a (DE-599)KEP047615052 | ||
| 035 | |a (ORHE)9781491936511 | ||
| 035 | |a (DE-627-1)047615052 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rda | ||
| 041 | |a eng | ||
| 100 | 1 | |a Amundsen, Michael |e RednerIn |4 spk | |
| 245 | 1 | 0 | |a REST, hypermedia, and the semantic gap |b why "RMM-level3 REST" is not enough |c with Mike Amundsen |
| 264 | 1 | |a [Place of publication not identified] |b O'Reilly Media |c 2015 | |
| 300 | |a 1 Online-Ressource (1 streaming video file (51 min., 2 sec.)) |b digital, sound, color. | ||
| 336 | |a zweidimensionales bewegtes Bild |b tdi |2 rdacontent | ||
| 337 | |a Computermedien |b c |2 rdamedia | ||
| 338 | |a Online-Ressource |b cr |2 rdacarrier | ||
| 500 | |a Title from title screen (Safari, viewed August 25, 2015). - Date of publication taken from resource description page | ||
| 520 | |a "Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusability of APIs. But what are Hypermedia APIs? What do they look like? And why are they "better" than the common CRUD APIs we all use today? This webcast illustrates the differences between CRUD and Hypermedia APIs and how you can design & implement clients and services that can take advantages of APIs based on hypermedia, not just resources and a tiny handful of verbs. Along the way, we'll look at working versions of both styles and get a chance to see why adding more hypermedia in service responses can result in more functionality on the client while reducing the amount of API-specific code on the client."--Resource description page. | ||
| 650 | 0 | |a Software architecture | |
| 650 | 0 | |a Representational State Transfer (Software architecture) | |
| 650 | 0 | |a Hypertext systems | |
| 650 | 0 | |a Application program interfaces (Computer software) | |
| 650 | 4 | |a Architecture logicielle | |
| 650 | 4 | |a REST (Architecture logicielle) | |
| 650 | 4 | |a Hypertexte | |
| 650 | 4 | |a Interfaces de programmation d'applications | |
| 650 | 4 | |a APIs (interfaces) | |
| 650 | 4 | |a Application program interfaces (Computer software) |0 (OCoLC)fst00811704 | |
| 650 | 4 | |a Hypertext systems |0 (OCoLC)fst00965876 | |
| 650 | 4 | |a Representational State Transfer (Software architecture) |0 (OCoLC)fst01747417 | |
| 650 | 4 | |a Software architecture |0 (OCoLC)fst01200416 | |
| 966 | 4 | 0 | |l DE-91 |p ZDB-30-ORH |q TUM_PDA_ORH |u https://learning.oreilly.com/library/view/-/9781491936511/?ar |m X:ORHE |x Aggregator |z lizenzpflichtig |3 Volltext |
| 912 | |a ZDB-30-ORH | ||
| 935 | |c vide | ||
| 951 | |a BO | ||
| 912 | |a ZDB-30-ORH | ||
| 049 | |a DE-91 | ||
Datensatz im Suchindex
| DE-BY-TUM_katkey | ZDB-30-ORH-047615052 |
|---|---|
| _version_ | 1821494951423246336 |
| adam_text | |
| any_adam_object | |
| author2 | Amundsen, Michael |
| author2_role | spk |
| author2_variant | m a ma |
| author_facet | Amundsen, Michael |
| building | Verbundindex |
| bvnumber | localTUM |
| collection | ZDB-30-ORH |
| ctrlnum | (DE-627-1)047615052 (DE-599)KEP047615052 (ORHE)9781491936511 |
| format | Electronic Video |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02846cgm a22004812 4500</leader><controlfield tag="001">ZDB-30-ORH-047615052</controlfield><controlfield tag="003">DE-627-1</controlfield><controlfield tag="005">20240228115929.0</controlfield><controlfield tag="006">m o | | </controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">191023s2015 xx ||| |o o ||eng c</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)047615052</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)KEP047615052</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ORHE)9781491936511</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)047615052</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Amundsen, Michael</subfield><subfield code="e">RednerIn</subfield><subfield code="4">spk</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">REST, hypermedia, and the semantic gap</subfield><subfield code="b">why "RMM-level3 REST" is not enough</subfield><subfield code="c">with Mike Amundsen</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">[Place of publication not identified]</subfield><subfield code="b">O'Reilly Media</subfield><subfield code="c">2015</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (1 streaming video file (51 min., 2 sec.))</subfield><subfield code="b">digital, sound, color.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">zweidimensionales bewegtes Bild</subfield><subfield code="b">tdi</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Title from title screen (Safari, viewed August 25, 2015). - Date of publication taken from resource description page</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">"Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusability of APIs. But what are Hypermedia APIs? What do they look like? And why are they "better" than the common CRUD APIs we all use today? This webcast illustrates the differences between CRUD and Hypermedia APIs and how you can design & implement clients and services that can take advantages of APIs based on hypermedia, not just resources and a tiny handful of verbs. Along the way, we'll look at working versions of both styles and get a chance to see why adding more hypermedia in service responses can result in more functionality on the client while reducing the amount of API-specific code on the client."--Resource description page.</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Software architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Representational State Transfer (Software architecture)</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Hypertext systems</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Application program interfaces (Computer software)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Architecture logicielle</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">REST (Architecture logicielle)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Hypertexte</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Interfaces de programmation d'applications</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">APIs (interfaces)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Application program interfaces (Computer software)</subfield><subfield code="0">(OCoLC)fst00811704</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Hypertext systems</subfield><subfield code="0">(OCoLC)fst00965876</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Representational State Transfer (Software architecture)</subfield><subfield code="0">(OCoLC)fst01747417</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software architecture</subfield><subfield code="0">(OCoLC)fst01200416</subfield></datafield><datafield tag="966" ind1="4" ind2="0"><subfield code="l">DE-91</subfield><subfield code="p">ZDB-30-ORH</subfield><subfield code="q">TUM_PDA_ORH</subfield><subfield code="u">https://learning.oreilly.com/library/view/-/9781491936511/?ar</subfield><subfield code="m">X:ORHE</subfield><subfield code="x">Aggregator</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="935" ind1=" " ind2=" "><subfield code="c">vide</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">BO</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield></record></collection> |
| id | ZDB-30-ORH-047615052 |
| illustrated | Not Illustrated |
| indexdate | 2025-01-17T11:22:32Z |
| institution | BVB |
| language | English |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 Online-Ressource (1 streaming video file (51 min., 2 sec.)) digital, sound, color. |
| psigel | ZDB-30-ORH TUM_PDA_ORH ZDB-30-ORH |
| publishDate | 2015 |
| publishDateSearch | 2015 |
| publishDateSort | 2015 |
| publisher | O'Reilly Media |
| record_format | marc |
| spelling | Amundsen, Michael RednerIn spk REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough with Mike Amundsen [Place of publication not identified] O'Reilly Media 2015 1 Online-Ressource (1 streaming video file (51 min., 2 sec.)) digital, sound, color. zweidimensionales bewegtes Bild tdi rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Title from title screen (Safari, viewed August 25, 2015). - Date of publication taken from resource description page "Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusability of APIs. But what are Hypermedia APIs? What do they look like? And why are they "better" than the common CRUD APIs we all use today? This webcast illustrates the differences between CRUD and Hypermedia APIs and how you can design & implement clients and services that can take advantages of APIs based on hypermedia, not just resources and a tiny handful of verbs. Along the way, we'll look at working versions of both styles and get a chance to see why adding more hypermedia in service responses can result in more functionality on the client while reducing the amount of API-specific code on the client."--Resource description page. Software architecture Representational State Transfer (Software architecture) Hypertext systems Application program interfaces (Computer software) Architecture logicielle REST (Architecture logicielle) Hypertexte Interfaces de programmation d'applications APIs (interfaces) Application program interfaces (Computer software) (OCoLC)fst00811704 Hypertext systems (OCoLC)fst00965876 Representational State Transfer (Software architecture) (OCoLC)fst01747417 Software architecture (OCoLC)fst01200416 |
| spellingShingle | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough Software architecture Representational State Transfer (Software architecture) Hypertext systems Application program interfaces (Computer software) Architecture logicielle REST (Architecture logicielle) Hypertexte Interfaces de programmation d'applications APIs (interfaces) Application program interfaces (Computer software) (OCoLC)fst00811704 Hypertext systems (OCoLC)fst00965876 Representational State Transfer (Software architecture) (OCoLC)fst01747417 Software architecture (OCoLC)fst01200416 |
| subject_GND | (OCoLC)fst00811704 (OCoLC)fst00965876 (OCoLC)fst01747417 (OCoLC)fst01200416 |
| title | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough |
| title_auth | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough |
| title_exact_search | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough |
| title_full | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough with Mike Amundsen |
| title_fullStr | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough with Mike Amundsen |
| title_full_unstemmed | REST, hypermedia, and the semantic gap why "RMM-level3 REST" is not enough with Mike Amundsen |
| title_short | REST, hypermedia, and the semantic gap |
| title_sort | rest hypermedia and the semantic gap why rmm level3 rest is not enough |
| title_sub | why "RMM-level3 REST" is not enough |
| topic | Software architecture Representational State Transfer (Software architecture) Hypertext systems Application program interfaces (Computer software) Architecture logicielle REST (Architecture logicielle) Hypertexte Interfaces de programmation d'applications APIs (interfaces) Application program interfaces (Computer software) (OCoLC)fst00811704 Hypertext systems (OCoLC)fst00965876 Representational State Transfer (Software architecture) (OCoLC)fst01747417 Software architecture (OCoLC)fst01200416 |
| topic_facet | Software architecture Representational State Transfer (Software architecture) Hypertext systems Application program interfaces (Computer software) Architecture logicielle REST (Architecture logicielle) Hypertexte Interfaces de programmation d'applications APIs (interfaces) |
| work_keys_str_mv | AT amundsenmichael resthypermediaandthesemanticgapwhyrmmlevel3restisnotenough |