@prefix rdf:	<http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dbpedia:	<http://dbpedia.org/resource/> .
dbpedia:Representational_State_Transfer	rdf:type	<http://dbpedia.org/class/yago/Web2.0Neologisms> .
@prefix owl:	<http://www.w3.org/2002/07/owl#> .
dbpedia:Representational_State_Transfer	owl:sameAs	<http://rdf.freebase.com/ns/guid.9202a8c04000641f80000000003a638c> .
@prefix foaf:	<http://xmlns.com/foaf/0.1/> .
@prefix ns4:	<http://en.wikipedia.org/wiki/> .
dbpedia:Representational_State_Transfer	foaf:page	ns4:Representational_State_Transfer .
@prefix dbpprop:	<http://dbpedia.org/property/> .
dbpedia:Representational_State_Transfer	dbpprop:reference	<http://astoria.mslivelabs.com/> ,
		<http://duncan-cragg.org/blog/post/getting-data-rest-dialogues/> ,
		<http://acet.rdg.ac.uk/projects/tycho/> ,
		<http://nicolas-zozol.developpez.com/tutorial/java/rest-jsp-english/> ,
		<http://www.gtrifonov.com/blog/2009/02/04/Building_JSON,XML_REST_API_using_WCF_services.aspx> ,
		<http://dret.net/netdret/docs/soa-rest-www2009/> .
@prefix ns6:	<http://www.infoq.com/articles/> .
dbpedia:Representational_State_Transfer	dbpprop:reference	ns6:rest-anti-patterns ,
		<http://www.xfront.com/REST-Web-Services.html> ,
		ns6:tilkov-rest-doubts .
@prefix ns7:	<http://sourceforge.net/projects/> .
dbpedia:Representational_State_Transfer	dbpprop:reference	ns7:restcgi ,
		ns6:rest-introduction ,
		ns6:designing-restful-http-apps-roth ,
		<http://shouldersofgiants.co.uk/Blog/post/2008/09/27/Creating-a-RESTful-Web-Service-Using-ASPNet-MVC-Part-1-Introduction.aspx> .
@prefix rdfs:	<http://www.w3.org/2000/01/rdf-schema#> .
dbpedia:Representational_State_Transfer	rdfs:label	"Representational State Transfer"@de ,
		"REST"@zh ,
		"Representational State Transfer"@sv ,
		"REST"@ja ,
		"Representational State Transfer"@fr ,
		"Representational State Transfer"@es ,
		"REST"@pt ,
		"REST"@ca ,
		"Representational State Transfer"@en ,
		"Representational State Transfer"@it ,
		"REST"@pl ,
		"REST"@ru ;
	dbpprop:abstract	"Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term Representational State Transfer (REST) was introduced and defined in 2000 by the doctoral dissertation of Roy Fielding, one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification versions 1.0 and 1.1. Conforming to the REST constraints is often referred to as being \u2018RESTful\u2019."@en ,
		"REST (\u0441\u043E\u043A\u0440. \u0430\u043D\u0433\u043B. Representational State Transfer, \u00AB\u043F\u0435\u0440\u0435\u0434\u0430\u0447\u0430 \u0441\u043E\u0441\u0442\u043E\u044F\u043D\u0438\u044F \u043F\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043B\u0435\u043D\u0438\u044F\u00BB) \u2014 \u043F\u043E\u0434\u0445\u043E\u0434 \u043A \u0430\u0440\u0445\u0438\u0442\u0435\u043A\u0442\u0443\u0440\u0435 \u0441\u0435\u0442\u0435\u0432\u044B\u0445 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u043E\u0432, \u043E\u0431\u0435\u0441\u043F\u0435\u0447\u0438\u0432\u0430\u044E\u0449\u0438\u0445 \u0434\u043E\u0441\u0442\u0443\u043F \u043A \u0438\u043D\u0444\u043E\u0440\u043C\u0430\u0446\u0438\u043E\u043D\u043D\u044B\u043C \u0440\u0435\u0441\u0443\u0440\u0441\u0430\u043C. \u0411\u044B\u043B \u043E\u043F\u0438\u0441\u0430\u043D \u0438 \u043F\u043E\u043F\u0443\u043B\u044F\u0440\u0438\u0437\u043E\u0432\u0430\u043D \u0432 2000 \u0433\u043E\u0434\u0443 \u0420\u043E\u0439\u0435\u043C \u0424\u0438\u043B\u0434\u0438\u043D\u0433\u043E\u043C (Roy Fielding), \u043E\u0434\u043D\u0438\u043C \u0438\u0437 \u0441\u043E\u0437\u0434\u0430\u0442\u0435\u043B\u0435\u0439 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u0430 HTTP. \u0421\u0430\u043C\u043E\u0439 \u0438\u0437\u0432\u0435\u0441\u0442\u043D\u043E\u0439 \u0441\u0438\u0441\u0442\u0435\u043C\u043E\u0439, \u043F\u043E\u0441\u0442\u0440\u043E\u0435\u043D\u043D\u043E\u0439 \u0432 \u0437\u043D\u0430\u0447\u0438\u0442\u0435\u043B\u044C\u043D\u043E\u0439 \u0441\u0442\u0435\u043F\u0435\u043D\u0438 \u043F\u043E \u0430\u0440\u0445\u0438\u0442\u0435\u043A\u0442\u0443\u0440\u0435 REST, \u044F\u0432\u043B\u044F\u0435\u0442\u0441\u044F \u0441\u043E\u0432\u0440\u0435\u043C\u0435\u043D\u043D\u0430\u044F \u0412\u0441\u0435\u043C\u0438\u0440\u043D\u0430\u044F \u043F\u0430\u0443\u0442\u0438\u043D\u0430. \u0421\u043E\u0433\u043B\u0430\u0441\u043D\u043E REST, \u0441\u0435\u0442\u0435\u0432\u043E\u0439 \u0440\u0435\u0441\u0443\u0440\u0441 \u0434\u043E\u043B\u0436\u0435\u043D \u043F\u043E\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044C \u0432\u0441\u0435\u0433\u043E \u0447\u0435\u0442\u044B\u0440\u0435 \u043E\u043F\u0435\u0440\u0430\u0446\u0438\u0438: GET, PUT, POST \u0438 DELETE (\u0441 \u0442\u0435\u043C\u0438 \u0436\u0435 \u0437\u043D\u0430\u0447\u0435\u043D\u0438\u044F\u043C\u0438, \u043A\u0430\u043A \u0432 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u0435 HTTP). \u0414\u0430\u043D\u043D\u044B\u0435 \u0434\u043E\u043B\u0436\u043D\u044B \u043F\u0435\u0440\u0435\u0434\u0430\u0432\u0430\u0442\u044C\u0441\u044F \u0432 \u0432\u0438\u0434\u0435 \u043D\u0435\u0431\u043E\u043B\u044C\u0448\u043E\u0433\u043E \u043A\u043E\u043B\u0438\u0447\u0435\u0441\u0442\u0432\u0430 \u0441\u0442\u0430\u043D\u0434\u0430\u0440\u0442\u043D\u044B\u0445 \u0444\u043E\u0440\u043C\u0430\u0442\u043E\u0432. \u0421\u0435\u0442\u0435\u0432\u043E\u0439 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B (\u043A\u0430\u043A \u0438 HTTP) \u0434\u043E\u043B\u0436\u0435\u043D \u043F\u043E\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044C \u043A\u044D\u0448\u0438\u0440\u043E\u0432\u0430\u043D\u0438\u0435, \u043D\u0435 \u0434\u043E\u043B\u0436\u0435\u043D \u0437\u0430\u0432\u0438\u0441\u0435\u0442\u044C \u043E\u0442 \u0441\u0435\u0442\u0435\u0432\u043E\u0433\u043E \u0441\u043B\u043E\u044F, \u043D\u0435 \u0434\u043E\u043B\u0436\u0435\u043D \u0441\u043E\u0445\u0440\u0430\u043D\u044F\u0442\u044C \u0438\u043D\u0444\u043E\u0440\u043C\u0430\u0446\u0438\u044E \u043E \u0441\u043E\u0441\u0442\u043E\u044F\u043D\u0438\u0438 \u043C\u0435\u0436\u0434\u0443 \u043F\u0430\u0440\u0430\u043C\u0438 \u00AB\u0437\u0430\u043F\u0440\u043E\u0441-\u043E\u0442\u0432\u0435\u0442\u00BB. \u0423\u0442\u0432\u0435\u0440\u0436\u0434\u0430\u0435\u0442\u0441\u044F, \u0447\u0442\u043E \u0442\u0430\u043A\u043E\u0439 \u043F\u043E\u0434\u0445\u043E\u0434 \u043E\u0431\u0435\u0441\u043F\u0435\u0447\u0438\u0432\u0430\u0435\u0442 \u043C\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u0443\u0435\u043C\u043E\u0441\u0442\u044C \u0441\u0438\u0441\u0442\u0435\u043C\u044B \u0438 \u043F\u043E\u0437\u0432\u043E\u043B\u044F\u0435\u0442 \u0435\u0439 \u044D\u0432\u043E\u043B\u044E\u0446\u0438\u043E\u043D\u0438\u0440\u043E\u0432\u0430\u0442\u044C \u0441 \u043D\u043E\u0432\u044B\u043C\u0438 \u0442\u0440\u0435\u0431\u043E\u0432\u0430\u043D\u0438\u044F\u043C\u0438. \u0410\u043D\u0442\u0438\u043F\u043E\u0434\u043E\u043C REST \u044F\u0432\u043B\u044F\u0435\u0442\u0441\u044F \u043F\u043E\u0434\u0445\u043E\u0434, \u043E\u0441\u043D\u043E\u0432\u0430\u043D\u043D\u044B\u0439 \u043D\u0430 \u0432\u044B\u0437\u043E\u0432\u0435 \u0443\u0434\u0430\u043B\u0435\u043D\u043D\u044B\u0445 \u043F\u0440\u043E\u0446\u0435\u0434\u0443\u0440 (Remote Procedure Call \u2014 RPC). \u041F\u043E\u0434\u0445\u043E\u0434 RPC \u043F\u043E\u0437\u0432\u043E\u043B\u044F\u0435\u0442 \u0438\u0441\u043F\u043E\u043B\u044C\u0437\u043E\u0432\u0430\u0442\u044C \u043D\u0435\u0431\u043E\u043B\u044C\u0448\u043E\u0435 \u043A\u043E\u043B\u0438\u0447\u0435\u0441\u0442\u0432\u043E \u0441\u0435\u0442\u0435\u0432\u044B\u0445 \u0440\u0435\u0441\u0443\u0440\u0441\u043E\u0432 \u0441 \u0431\u043E\u043B\u044C\u0448\u0438\u043C \u043A\u043E\u043B\u0438\u0447\u0435\u0441\u0442\u0432\u043E\u043C \u043C\u0435\u0442\u043E\u0434\u043E\u0432 \u0438 \u0441\u043B\u043E\u0436\u043D\u044B\u043C \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u043E\u043C. \u041F\u0440\u0438 \u043F\u043E\u0434\u0445\u043E\u0434\u0435 REST, \u043A\u043E\u043B\u0438\u0447\u0435\u0441\u0442\u0432\u043E \u043C\u0435\u0442\u043E\u0434\u043E\u0432 \u0438 \u0441\u043B\u043E\u0436\u043D\u043E\u0441\u0442\u044C \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u0430 \u0441\u0442\u0440\u043E\u0433\u043E \u043E\u0433\u0440\u0430\u043D\u0438\u0447\u0435\u043D\u044B, \u0438\u0437-\u0437\u0430 \u0447\u0435\u0433\u043E \u043A\u043E\u043B\u0438\u0447\u0435\u0441\u0442\u0432\u043E \u043E\u0442\u0434\u0435\u043B\u044C\u043D\u044B\u0445 \u0440\u0435\u0441\u0443\u0440\u0441\u043E\u0432 \u0434\u043E\u043B\u0436\u043D\u043E \u0431\u044B\u0442\u044C \u0431\u043E\u043B\u044C\u0448\u0438\u043C."@ru ,
		"REST (Representational State Transfer) \u00E9s una arquitectura de programari pensada per sistemes distribu\u00EFts basats en hypermedia, com ara la web. Aquest terme va ser introdu\u00EFt l'any 2000 en una tesi doctoral sobre arquitectures de programari de xarxes. Aquesta tesi va ser escrita per Roy Thomas Fielding i dirigida per Richard N. Taylor. Roy va ser un dels principals autors de les especificacions del protocol HTTP i explica en la seva tesi com es pot aprofitar aquest protocol per tal de desenvolupar aplicacions distribu\u00EFdes. Tot i que en un principi REST es referia tan sols a un conjunt de principis d'arquitectura de xarxa i la definici\u00F3 i adre\u00E7ament dels recursos, actualment aquest concepte s'utilitza per referir-se a una interf\u00EDcie web que utilitza XML i HTTP sense cap conjunt de cap\u00E7aleres com podria ser en el cas de SOAP i XML-RPC. Segons la tesi de Roy es poden dissenyar interf\u00EDcies XML+HTTP seguint la filosofia de RPC sense utilitzar la complexitat del protocol SOAP."@ca ,
		"Representational State Transfer(REST) \u306F\u3001\u30A6\u30A7\u30D6\u306E\u3088\u3046\u306A\u5206\u6563\u30CF\u30A4\u30D1\u30FC\u30E1\u30C7\u30A3\u30A2\u30B7\u30B9\u30C6\u30E0\u306E\u305F\u3081\u306E\u30BD\u30D5\u30C8\u30A6\u30A7\u30A2\u30A2\u30FC\u30AD\u30C6\u30AF\u30C1\u30E3\u306E\u30B9\u30BF\u30A4\u30EB\u306E\u3072\u3068\u3064\u3067\u3042\u308B\u3002\u3053\u306E\u8A9E\u306F2000\u5E74\u306B\u3001HTTP\u30D7\u30ED\u30C8\u30B3\u30EB\u898F\u683C\u306E\u4E3B\u8981\u8457\u8005\u306E\u4E00\u4EBA\u3067\u3042\u308BRoy Fielding\u304C\u3001\u30A6\u30A7\u30D6\u306B\u3064\u3044\u3066\u66F8\u3044\u305F\u535A\u58EB\u8AD6\u6587\u3067\u521D\u3081\u3066\u73FE\u308C\u3001\u30CD\u30C3\u30C8\u30EF\u30FC\u30AD\u30F3\u30B0\u30B3\u30DF\u30E5\u30CB\u30C6\u30A3\u306E\u4E2D\u3067\u3059\u3050\u306B\u5E83\u304F\u4F7F\u308F\u308C\u308B\u3053\u3068\u306B\u306A\u3063\u305F\u3002 REST\u306F\u3001\u521D\u3081\u306F\u30A2\u30FC\u30AD\u30C6\u30AF\u30C1\u30E3\u306E\u539F\u5247\u3068\u5236\u7D04\u306E\u96C6\u307E\u308A(\u5F8C\u8FF0)\u3092\u6307\u3057\u3066\u3044\u305F\u304C\u3001\u6B21\u7B2C\u306B\u3001XML\u3084HTTP\u3092\u4F7F\u3063\u305F\u7C21\u6613\u306A\u30A6\u30A7\u30D6\u30D9\u30FC\u30B9\u306E\u30A4\u30F3\u30BF\u30FC\u30D5\u30A7\u30A4\u30B9\u306E\u3046\u3061\u3001Web\u30B5\u30FC\u30D3\u30B9\u306ESOAP\u30D7\u30ED\u30C8\u30B3\u30EB\u306E\u3088\u3046\u306A MEP\uFF08Message Exchange Pattern; SOAP\u30CE\u30FC\u30C9\u76F8\u4E92\u306E\u30E1\u30C3\u30BB\u30FC\u30B8\u4EA4\u63DB\u306E\u30D1\u30BF\u30FC\u30F3\u3092\u78BA\u7ACB\u3059\u308B\u305F\u3081\u306E\u96DB\u578B\uFF09\u30D9\u30FC\u30B9\u306E\u7279\u5225\u306A\u62BD\u8C61\u5316\u3092\u3057\u306A\u3044\u3082\u306E\u306E\u3053\u3068\u3092\u3001\u5927\u307E\u304B\u306B\u610F\u5473\u3059\u308B\u7528\u8A9E\u3068\u3057\u3066\u4F7F\u308F\u308C\u308B\u3088\u3046\u306B\u306A\u3063\u305F\u3002REST\u306F\u6B21\u306B\u8FF0\u3079\u308B\u3088\u3046\u306B2\u3064\u306E\u3084\u3084\u7570\u306A\u308B\u610F\u5473\u3067\u4F7F\u308F\u308C\u3066\u3044\u308B\u3002 Fielding\u306EREST\u30A2\u30FC\u30AD\u30C6\u30AF\u30C1\u30E3\u30B9\u30BF\u30A4\u30EB\u306E\u539F\u5247\u306B\u5408\u308F\u305B\u305FWeb\u30B5\u30FC\u30D3\u30B9\u30B7\u30B9\u30C6\u30E0\u3002 RPC\u30B9\u30BF\u30A4\u30EB\u306B\u5408\u308F\u305B\u305F\u7C21\u6613\u306A XML+HTTP \u30A4\u30F3\u30BF\u30FC\u30D5\u30A7\u30A4\u30B9\u3092\u63A1\u7528\u3057\u305F\u30B7\u30B9\u30C6\u30E0(SOAP\u306F\u4F7F\u308F\u306A\u3044) \u3002 REST\u306F\u3053\u306E\u3088\u3046\u306B2\u3064\u306E\u3084\u3084\u7570\u306A\u308B\u610F\u5473\u3067\u4F7F\u308F\u308C\u3066\u3044\u308B\u305F\u3081\u3001\u6280\u8853\u7684\u306A\u8B70\u8AD6\u306E\u4E2D\u3067\u6DF7\u4E71\u3092\u5F15\u304D\u8D77\u3053\u3059\u3053\u3068\u304C\u3042\u308B\u3002 \u305F\u3060\u3057\u3001RPC\u306FREST\u306E\u5B9F\u4F8B\u3068\u306F\u3044\u3048\u306A\u3044\u3002 Fielding\u306EREST\u539F\u5247\u306B\u5F93\u3046\u30B7\u30B9\u30C6\u30E0\u306F\u3001\u3057\u3070\u3057\u3070RESTful\u3068\u3044\u308F\u308C\u308B\u3002REST\u3092\u3068\u3066\u3082\u71B1\u5FC3\u306B\u652F\u6301\u3059\u308B\u4EBA\u3005\u306F\u81EA\u3089\u306E\u3053\u3068\u3092RESTafarians\u3068\u547C\u3076\u3002\u3061\u306A\u307F\u306B\u3001\u3053\u306E\u547C\u79F0\u306F\u300C\u30E9\u30B9\u30BF\u30D5\u30A1\u30EA\u30A2\u30F3\u300D(Rastafarians)\u306E\u3082\u3058\u308A\u3067\u3042\u308B\u3002"@ja ,
		"A Transfer\u00EAncia de Estado Representacional (Representational State Transfer) ou somente (REST) \u00E9 uma t\u00E9cnica de engenharia de software para sistemas hiperm\u00EDdia distribu\u00EDdos como a World Wide Web. O termo se originou no ano de 2000, em uma tese de doutorado (PHD) sobre a web escrita por Roy Fielding, um dos principais autores as especifica\u00E7\u00E3o do protocolo HTTP que \u00E9 utilizado por sites da internet. O termo REST se referia, originalmente, a um conjunto de princ\u00EDpios de arquitectura (descritos mais abaixo), na actualidade se usa no sentido mais amplo para descrever qualquer interface web simples que utiliza XML e HTTP, sem as abstra\u00E7\u00F5es adicionais dos protocolos baseados em padr\u00F5es de trocas de mensagem como o protocolo de servi\u00E7os web SOAP. \u00C9 poss\u00EDvel desenhar sistemas de servi\u00E7os web de acordo com o estilo arquitetural REST descrito por Fielding, e tamb\u00E9m \u00E9 poss\u00EDvel desenhar interfaces XMLHTTP de acordo com o estilo de RPC mas sem utilizar SOAP. Estes usos diferentes do termo REST causam certa confus\u00E3o em discuss\u00F5es t\u00E9cnicas, onde RPC n\u00E3o \u00E9 um exemplo de REST. Os sistemas que seguem os princ\u00EDpios REST s\u00E3o freq\u00FCentemente chamados de RESTful; os defensores mais ferrenhos do REST s\u00E3o chamados pelos mesmos de RESTafarianos."@pt ,
		"Representational State Transfer \u2013 wzorzec architektury oprogramowania opieraj\u0105cy si\u0119 na bezstanowej wymianie informacji w \u015Brodowisku rozproszonym. Jako no\u015Bnik informacji wykorzystuje m. in. formaty XML i JSON. W przeciwie\u0144stwie do architektur opartych na us\u0142ugach (SOA), w REST g\u0142\u00F3wn\u0105 jednostk\u0105 informacji jest zas\u00F3b, do kt\u00F3rego dost\u0119p uzyskuje si\u0119 poprzez wykorzystanie r\u00F3\u017Cnych czasownik\u00F3w \u2013 typ\u00F3w wywo\u0142a\u0144 protoko\u0142u HTTP. Zaproponowany przez Roya T. Fieldinga w publikacji Principled Design of the Modern Web Architecture, zosta\u0142 spopularyzowany przez framework aplikacji internetowych Ruby on Rails."@pl ,
		"Representational state transfer (REST) \u00E8 un tipo di architettura software per i sistemi di ipertesto distribuiti come il World Wide Web. Il termine \"representational state transfer\" e \"REST\" furono introdotti nel 2000 nella tesi di dottorato di Roy Fielding, uno dei principali autori delle specifiche dell' Hypertext Transfer Protocol, termine ampiamente usato nella comunit\u00E0 di internet. REST si riferisce ad un insieme di principi di architetture di rete, i quali delineano come le risorse sono definite e indirizzate. Il termine \u00E8 spesso usato nel senso di descrivere ogni semplice interfaccia che trasmette dati su HTTP senza un livello opzionale come SOAP o la gestione della sessione tramite i cookies. Questi due concetti possono andare in conflitto cosi come in sovrapposizione. \u00C8 possibile progettare ogni sistema software complesso in accordo con l'architettura REST di Fielding senza usare HTTP e senza interagire con il World Wide Web. \u00C8 anche possibile progettare una semplice interfaccia XML+HTTP che non sia conforme ai principi REST, e invece segua un modello di Remote Procedure Call. La differenza tra l'uso del termine \"REST\" quindi causa qualche confusione nei dibattiti. I sistemi che seguono i principi REST sono spesso definiti \"RESTful\"."@it ,
		"\u8868\u8C61\u5316\u72B6\u6001\u8F6C\u53D8\uFF08\u82F1\u6587\uFF1ARepresentational State Transfer\uFF0C\u7B80\u79F0REST\uFF09\u662FRoy Fielding\u535A\u58EB\u57282000\u5E74\u4ED6\u7684\u535A\u58EB\u8BBA\u6587\u4E2D\u63D0\u51FA\u6765\u7684\u4E00\u79CD\u8F6F\u4EF6\u67B6\u6784\u98CE\u683C\u3002 \u76EE\u524D\u5728\u4E09\u79CD\u4E3B\u6D41\u7684Web\u670D\u52A1\u5B9E\u73B0\u65B9\u6848\u4E2D\uFF0C\u56E0\u4E3AREST\u6A21\u5F0F\u7684Web\u670D\u52A1\u4E0E\u590D\u6742\u7684SOAP\u548CXML-RPC\u5BF9\u6BD4\u6765\u8BB2\u660E\u663E\u7684\u66F4\u52A0\u7B80\u6D01\uFF0C\u8D8A\u6765\u8D8A\u591A\u7684web\u670D\u52A1\u5F00\u59CB\u91C7\u7528REST\u98CE\u683C\u8BBE\u8BA1\u548C\u5B9E\u73B0\u3002\u4F8B\u5982\uFF0CAmazon. com\u63D0\u4F9B\u63A5\u8FD1REST\u98CE\u683C\u7684Web\u670D\u52A1\u8FDB\u884C\u56FE\u4E66\u67E5\u627E\uFF1B\u96C5\u864E\u63D0\u4F9B\u7684Web\u670D\u52A1\u4E5F\u662FREST\u98CE\u683C\u7684\u3002"@zh ,
		"Der Begriff Representational State Transfer bzw. das Akronym REST bezeichnen einen Softwarearchitekturstil f\u00FCr verteilte Hypermedia-Informationssysteme wie das World Wide Web. W\u00E4hrend dessen Architektur durch den URI-Standard und HTTP beschrieben werden kann, legt der REST-Architekturstil nahe, jede Ressource mit einer eigenen URI anzusprechen. REST stammt aus der Dissertation von Roy Fielding aus dem Jahre 2000, in welcher der Erfolg des World Wide Webs auf bestimmte Eigenschaften der verwendeten Mechanismen und Protokolle (z. B. HTTP) zur\u00FCckgef\u00FChrt wird. Fielding war zuvor auch an der Spezifikation des Hypertext-Transfer-Protokolls (HTTP) beteiligt gewesen. Der Begriff wird auch im weiteren Sinne verwendet, um grunds\u00E4tzlich einfache Schnittstellen zu kennzeichnen, die Daten via HTTP \u00FCbertragen, ohne etwa eine zus\u00E4tzliche Transportschicht wie SOAP oder Session-Verwaltung via Cookies einzusetzen. REST gilt in seiner Konsequenz als eine wichtige Richtlinie f\u00FCr die Nutzung von Web-Standards, in Abgrenzung zu vielen historisch gewachsenen Verfahren. Daraus folgt teils eine R\u00FCckbesinnung auf grundlegende Web-Technologien, die Implementierungen verteilter webbasierter Systeme vereinfachen soll."@de ,
		"La Transferencia de Estado Representacional (Representational State Transfer) o REST es una t\u00E9cnica de arquitectura software para sistemas hipermedia distribuidos como la World Wide Web. El t\u00E9rmino se origin\u00F3 en el a\u00F1o 2000, en una tesis doctoral sobre la web escrita por Roy Fielding, uno de los principales autores de la especificaci\u00F3n del protocolo HTTP y ha pasado a ser ampliamente utilizado por la comunidad de desarrollo. Si bien el t\u00E9rmino REST se refer\u00EDa originalmente a un conjunto de principios de arquitectura \u2014descritos m\u00E1s abajo\u2014, en la actualidad se usa en el sentido m\u00E1s amplio para describir cualquier interfaz web simple que utiliza XML y HTTP, sin las abstracciones adicionales de los protocolos basados en patrones de intercambio de mensajes como el protocolo de servicios web SOAP. Es posible dise\u00F1ar sistemas de servicios web de acuerdo con el estilo arquitectural REST de Fielding y tambi\u00E9n es posible dise\u00F1ar interfaces XMLHTTP de acuerdo con el estilo de llamada a procedimiento remoto pero sin usar SOAP. Estos dos usos diferentes del t\u00E9rmino REST causan cierta confusi\u00F3n en las discusiones t\u00E9cnicas, aunque RPC no es un ejemplo de REST. Los sistemas que siguen los principios REST se llaman con frecuencia RESTful; los defensores m\u00E1s ac\u00E9rrimos de REST se llaman a s\u00ED mismos RESTafaris. REST afirma que la web ha disfrutado de escalabilidad como resultado de una serie de dise\u00F1os fundamentales clave: Un protocolo cliente/servidor sin estado: cada mensaje HTTP contiene toda la informaci\u00F3n necesaria para comprender la petici\u00F3n. Como resultado, ni el cliente ni el servidor necesitan recordar ning\u00FAn estado de las comunicaciones entre mensajes. Sin embargo, en la pr\u00E1ctica, muchas aplicaciones basadas en HTTP utilizan cookies y otros mecanismos para mantener el estado de la sesi\u00F3n (algunas de estas pr\u00E1cticas, como la reescritura de URLs, no son permitidas por REST) Un conjunto de operaciones bien definidas que se aplican a todos los recursos de informaci\u00F3n: HTTP en s\u00ED define un conjunto peque\u00F1o de operaciones, las m\u00E1s importantes son POST, GET, PUT y DELETE. Con frecuencia estas operaciones se equiparan a las operaciones CRUD que se requieren para la persistencia de datos, aunque POST no encaja exactamente en este esquema. Una sintaxis universal para identificar los recursos. En un sistema REST, cada recurso es direccionable \u00FAnicamente a trav\u00E9s de su URI El uso de hipermedios, tanto para la informaci\u00F3n de la aplicaci\u00F3n como para las transiciones de estado de la aplicaci\u00F3n: la representaci\u00F3n de este estado en un sistema REST son t\u00EDpicamente HTML o XML. Como resultado de esto, es posible navegar de un recurso REST a muchos otros, simplemente siguiendo enlaces sin requerir el uso de registros u otra infraestructura adicional."@es ,
		"Varje resurs \u00E4r unikt adresserbar enligt en gemensam standard. Alla resurser har ett gemensamt gr\u00E4nssnitt f\u00F6r att \u00F6verf\u00F6ra kommandon mellan klient och server. Detta best\u00E5r av: Grundl\u00E4ggande kommandon f\u00F6r att interagera med objekt baserade p\u00E5 de verb som \u00E4r angivna i HTTP-standarden: POST, GET, PUT och DELETE. En upps\u00E4ttning inneh\u00E5llstyper baserade p\u00E5 mime types. Varje resurs kan erh\u00E5llas i ett av flera representationsformat. Till skillnad fr\u00E5n tj\u00E4nster implementerade p\u00E5 WS-stacken exponeras data ist\u00E4llet f\u00F6r metoder."@sv ,
		"REST (Representational State Transfer) est une mani\u00E8re de construire une application pour les syst\u00E8mes distribu\u00E9s comme le World Wide Web. Le terme a \u00E9t\u00E9 invent\u00E9 par Roy Fielding en 2000. REST n'est pas un protocole ou un format, c'est un style d'architecture, c'est le style architectural original du Web, b\u00E2ti sur quelques principes simples : l'URI est important : conna\u00EEtre l'URI doit suffire pour acc\u00E9der \u00E0 la ressource; HTTP fournit toutes les op\u00E9rations n\u00E9cessaires (GET, POST, PUT et DELETE, essentiellement); chaque op\u00E9ration est auto-suffisante : il n'y a pas d'\u00E9tat; utilisation des standards hypermedia : HTML ou XML qui permettent de faire des liens vers d'autres ressources et d'assurer ainsi la navigation dans l'application REST."@fr ;
	rdfs:comment	"A Transfer\u00EAncia de Estado Representacional (Representational State Transfer) ou somente (REST) \u00E9 uma t\u00E9cnica de engenharia de software para sistemas hiperm\u00EDdia distribu\u00EDdos como a World Wide Web. O termo se originou no ano de 2000, em uma tese de doutorado (PHD) sobre a web escrita por Roy Fielding, um dos principais autores as especifica\u00E7\u00E3o do protocolo HTTP que \u00E9 utilizado por sites da internet."@pt ,
		"Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term Representational State Transfer (REST) was introduced and defined in 2000 by the doctoral dissertation of Roy Fielding, one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification versions 1.0 and 1.1. Conforming to the REST constraints is often referred to as being \u2018RESTful\u2019."@en ,
		"La Transferencia de Estado Representacional (Representational State Transfer) o REST es una t\u00E9cnica de arquitectura software para sistemas hipermedia distribuidos como la World Wide Web. El t\u00E9rmino se origin\u00F3 en el a\u00F1o 2000, en una tesis doctoral sobre la web escrita por Roy Fielding, uno de los principales autores de la especificaci\u00F3n del protocolo HTTP y ha pasado a ser ampliamente utilizado por la comunidad de desarrollo."@es ,
		"\u8868\u8C61\u5316\u72B6\u6001\u8F6C\u53D8\uFF08\u82F1\u6587\uFF1ARepresentational State Transfer\uFF0C\u7B80\u79F0REST\uFF09\u662FRoy Fielding\u535A\u58EB\u57282000\u5E74\u4ED6\u7684\u535A\u58EB\u8BBA\u6587\u4E2D\u63D0\u51FA\u6765\u7684\u4E00\u79CD\u8F6F\u4EF6\u67B6\u6784\u98CE\u683C\u3002 \u76EE\u524D\u5728\u4E09\u79CD\u4E3B\u6D41\u7684Web\u670D\u52A1\u5B9E\u73B0\u65B9\u6848\u4E2D\uFF0C\u56E0\u4E3AREST\u6A21\u5F0F\u7684Web\u670D\u52A1\u4E0E\u590D\u6742\u7684SOAP\u548CXML-RPC\u5BF9\u6BD4\u6765\u8BB2\u660E\u663E\u7684\u66F4\u52A0\u7B80\u6D01\uFF0C\u8D8A\u6765\u8D8A\u591A\u7684web\u670D\u52A1\u5F00\u59CB\u91C7\u7528REST\u98CE\u683C\u8BBE\u8BA1\u548C\u5B9E\u73B0\u3002\u4F8B\u5982\uFF0CAmazon. com\u63D0\u4F9B\u63A5\u8FD1REST\u98CE\u683C\u7684Web\u670D\u52A1\u8FDB\u884C\u56FE\u4E66\u67E5\u627E\uFF1B\u96C5\u864E\u63D0\u4F9B\u7684Web\u670D\u52A1\u4E5F\u662FREST\u98CE\u683C\u7684\u3002"@zh ,
		"Der Begriff Representational State Transfer bzw. das Akronym REST bezeichnen einen Softwarearchitekturstil f\u00FCr verteilte Hypermedia-Informationssysteme wie das World Wide Web. W\u00E4hrend dessen Architektur durch den URI-Standard und HTTP beschrieben werden kann, legt der REST-Architekturstil nahe, jede Ressource mit einer eigenen URI anzusprechen."@de ,
		"Representational State Transfer \u2013 wzorzec architektury oprogramowania opieraj\u0105cy si\u0119 na bezstanowej wymianie informacji w \u015Brodowisku rozproszonym. Jako no\u015Bnik informacji wykorzystuje m. in. formaty XML i JSON. W przeciwie\u0144stwie do architektur opartych na us\u0142ugach (SOA), w REST g\u0142\u00F3wn\u0105 jednostk\u0105 informacji jest zas\u00F3b, do kt\u00F3rego dost\u0119p uzyskuje si\u0119 poprzez wykorzystanie r\u00F3\u017Cnych czasownik\u00F3w \u2013 typ\u00F3w wywo\u0142a\u0144 protoko\u0142u HTTP. Zaproponowany przez Roya T."@pl ,
		"REST (Representational State Transfer) \u00E9s una arquitectura de programari pensada per sistemes distribu\u00EFts basats en hypermedia, com ara la web. Aquest terme va ser introdu\u00EFt l'any 2000 en una tesi doctoral sobre arquitectures de programari de xarxes. Aquesta tesi va ser escrita per Roy Thomas Fielding i dirigida per Richard N. Taylor."@ca ,
		"REST (Representational State Transfer) est une mani\u00E8re de construire une application pour les syst\u00E8mes distribu\u00E9s comme le World Wide Web. Le terme a \u00E9t\u00E9 invent\u00E9 par Roy Fielding en 2000."@fr ,
		"Representational state transfer (REST) \u00E8 un tipo di architettura software per i sistemi di ipertesto distribuiti come il World Wide Web. Il termine \"representational state transfer\" e \"REST\" furono introdotti nel 2000 nella tesi di dottorato di Roy Fielding, uno dei principali autori delle specifiche dell' Hypertext Transfer Protocol, termine ampiamente usato nella comunit\u00E0 di internet."@it ,
		"Varje resurs \u00E4r unikt adresserbar enligt en gemensam standard. Alla resurser har ett gemensamt gr\u00E4nssnitt f\u00F6r att \u00F6verf\u00F6ra kommandon mellan klient och server. Detta best\u00E5r av: Grundl\u00E4ggande kommandon f\u00F6r att interagera med objekt baserade p\u00E5 de verb som \u00E4r angivna i HTTP-standarden: POST, GET, PUT och DELETE. En upps\u00E4ttning inneh\u00E5llstyper baserade p\u00E5 mime types. Varje resurs kan erh\u00E5llas i ett av flera representationsformat."@sv ,
		"REST (\u0441\u043E\u043A\u0440. \u0430\u043D\u0433\u043B. Representational State Transfer, \u00AB\u043F\u0435\u0440\u0435\u0434\u0430\u0447\u0430 \u0441\u043E\u0441\u0442\u043E\u044F\u043D\u0438\u044F \u043F\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043B\u0435\u043D\u0438\u044F\u00BB) \u2014 \u043F\u043E\u0434\u0445\u043E\u0434 \u043A \u0430\u0440\u0445\u0438\u0442\u0435\u043A\u0442\u0443\u0440\u0435 \u0441\u0435\u0442\u0435\u0432\u044B\u0445 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u043E\u0432, \u043E\u0431\u0435\u0441\u043F\u0435\u0447\u0438\u0432\u0430\u044E\u0449\u0438\u0445 \u0434\u043E\u0441\u0442\u0443\u043F \u043A \u0438\u043D\u0444\u043E\u0440\u043C\u0430\u0446\u0438\u043E\u043D\u043D\u044B\u043C \u0440\u0435\u0441\u0443\u0440\u0441\u0430\u043C. \u0411\u044B\u043B \u043E\u043F\u0438\u0441\u0430\u043D \u0438 \u043F\u043E\u043F\u0443\u043B\u044F\u0440\u0438\u0437\u043E\u0432\u0430\u043D \u0432 2000 \u0433\u043E\u0434\u0443 \u0420\u043E\u0439\u0435\u043C \u0424\u0438\u043B\u0434\u0438\u043D\u0433\u043E\u043C (Roy Fielding), \u043E\u0434\u043D\u0438\u043C \u0438\u0437 \u0441\u043E\u0437\u0434\u0430\u0442\u0435\u043B\u0435\u0439 \u043F\u0440\u043E\u0442\u043E\u043A\u043E\u043B\u0430 HTTP."@ru ,
		""@ja .
@prefix skos:	<http://www.w3.org/2004/02/skos/core#> .
dbpedia:Representational_State_Transfer	skos:subject	<http://dbpedia.org/resource/Category:Web_2.0_neologisms> .
@prefix ns10:	<http://dbpedia.org/resource/Category:> .
dbpedia:Representational_State_Transfer	skos:subject	ns10:Software_architecture ,
		ns10:Cloud_standards .
@prefix ns11:	<http://www4.wiwiss.fu-berlin.de/flickrwrappr/photos/> .
dbpedia:Representational_State_Transfer	dbpprop:hasPhotoCollection	ns11:Representational_State_Transfer .
@prefix dbpedia-owl:	<http://dbpedia.org/ontology/> .
dbpedia:Apache_Wink	dbpedia-owl:genre	dbpedia:Representational_State_Transfer .
@prefix ns13:	<http://dbpedia.org/ontology/Work/> .
dbpedia:Apache_Wink	ns13:genre	dbpedia:Representational_State_Transfer ;
	dbpprop:genre	dbpedia:Representational_State_Transfer .
dbpedia:RESTfully	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:Restful_web_service	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:REST	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:RESTful	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:Rest_interface	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:Restful	dbpprop:redirect	dbpedia:Representational_State_Transfer .
dbpedia:RESTafarian	dbpprop:redirect	dbpedia:Representational_State_Transfer .
@prefix yago:	<http://mpii.de/yago/resource/> .
yago:Representational_State_Transfer	owl:sameAs	dbpedia:Representational_State_Transfer .