{"id":52640,"date":"2019-11-13T00:00:00","date_gmt":"2019-11-12T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu"},"modified":"2020-02-18T14:00:25","modified_gmt":"2020-02-18T11:00:25","slug":"xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu","title":{"rendered":"XML is almost always used improperly","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"XML is almost always used improperly\" src=\"\/wp-content\/uploads\/2019\/11\/8152077415a94ef74806af230ef44bd7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nGjuha XML u shpik n\u00eb vitin 1996. Pothuajse sapo filloi t\u00eb ekzistoj\u00eb, mund\u00ebsit\u00eb e p\u00ebrdorimit t\u00eb tij u kuptuan gabimisht, dhe p\u00ebr ato q\u00ebllime p\u00ebr t\u00eb cilat u p\u00ebrpoq t\u00eb adaptohej, ai nuk ishte zgjedhja m\u00eb e mir\u00eb.<\/p>\n<p>Nuk do t\u00eb ishte ekzagjerim t\u00eb thuash se shumica d\u00ebrrmuese e skemave XML q\u00eb kam par\u00eb, p\u00ebrb\u00ebnin nj\u00eb p\u00ebrdorim t\u00eb paarsyesh\u00ebm ose t\u00eb gabuar t\u00eb XML. P\u00ebr m\u00eb tep\u00ebr, kjo p\u00ebrdorim i XML testamentonte nj\u00eb keqkuptim themelor t\u00eb asaj \u00e7far\u00eb n\u00eb thelb \u00ebsht\u00eb XML.<\/p>\n<p>XML \u00ebsht\u00eb nj\u00eb gjuh\u00eb sh\u00ebnjimi. <b>Kjo nuk \u00ebsht\u00eb nj\u00eb format t\u00eb dh\u00ebnash<\/b>. N\u00eb shumic\u00ebn e skemave XML, kjo ndarje nuk u mor parasysh, duke e ngat\u00ebrruar XML me nj\u00eb format t\u00eb dh\u00ebnash, \u00e7ka n\u00eb fund n\u00ebnkuptonte nj\u00eb gabim n\u00eb zgjedhjen e XML, pasi n\u00eb t\u00eb v\u00ebrtet\u00eb duhej nj\u00eb format t\u00eb dh\u00ebnash.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nN\u00ebse nuk duam t\u00eb hyjm\u00eb n\u00eb detaje, XML i p\u00ebrshtatet m\u00eb s\u00eb miri annotimit t\u00eb blloqeve t\u00eb tekstit me struktur\u00eb dhe metadata. N\u00ebse q\u00ebllimi juaj kryesor nuk \u00ebsht\u00eb t\u00eb punoni me nj\u00eb bllok teksti, zgjedhja e XML-s\u00eb v\u00ebshtir\u00eb se do t\u00eb ishte e arsyeshme.<\/p>\n<p>Nga kjo pik\u00ebpamje, ekziston nj\u00eb m\u00ebnyr\u00eb e thjesht\u00eb p\u00ebr t\u00eb verifikuar se sa mir\u00eb \u00ebsht\u00eb nd\u00ebrtuar nj\u00eb skem\u00eb XML. Merrni p\u00ebr shembull nj\u00eb dokument n\u00eb skem\u00ebn e parashikuar dhe hiqni t\u00eb gjitha etiketat dhe atribute. N\u00ebse n\u00eb at\u00eb q\u00eb ka mbetur nuk ka kuptim (ose n\u00ebse mbetet nj\u00eb varg i zbraz\u00ebt), at\u00ebher\u00eb ose skema juaj \u00ebsht\u00eb nd\u00ebrtuar gabimisht, ose thjesht nuk duhej t\u00eb p\u00ebrdornit XML.<\/p>\n<p>M\u00eb tej do t\u00eb jap disa nga shembujt m\u00eb t\u00eb zakonsh\u00ebm t\u00eb skemave t\u00eb nd\u00ebrtuara gabimisht.<\/p>\n<pre><code class=\"xml\"><\/code><\/pre>\n<p>\nK\u00ebtu shihet nj\u00eb shembull i nj\u00eb p\u00ebrpjekjeje t\u00eb bazuar dhe t\u00eb \u00e7uditshme (edhe pse shum\u00eb t\u00eb zakonshme) p\u00ebr t\u00eb shprehur me gjuh\u00ebn XML nj\u00eb fjalor t\u00eb thjesht\u00eb \"\u00e7el\u00ebs-vler\u00eb\". N\u00ebse hiqen t\u00eb gjitha etiketat dhe atributet, mbetet nj\u00eb varg i zbraz\u00ebt. N\u00eb thelb, ky dokument p\u00ebrfaq\u00ebson, sa absurd t\u00eb ting\u00eblloj\u00eb, nj\u00eb annotim semantik t\u00eb vargut t\u00eb zbraz\u00ebt.<\/p>\n<pre><code class=\"xml\">&lt;root name=\"John\" city=\"London\" \/&gt;<\/code><\/pre>\n<p>\n\u00c7far\u00eb \u00ebsht\u00eb edhe m\u00eb keq, k\u00ebtu nuk kemi vet\u00ebm nj\u00eb annotim semantik t\u00eb nj\u00eb string t\u00eb zbraz\u00ebt si nj\u00eb m\u00ebnyr\u00eb ekstravagante p\u00ebr t\u00eb shprehur rregulloren \u2014 k\u00ebt\u00eb her\u00eb 'rregullorja' \u00ebsht\u00eb koduar direkt si atribute t\u00eb elementit rr\u00ebnj\u00eb. Nga kjo, grupi i caktuar i emrave t\u00eb atributeve n\u00eb element b\u00ebhet i paqart\u00eb dhe dinamik. M\u00eb tej, \u00ebsht\u00eb e qart\u00eb se gjith\u00e7ka q\u00eb autori donte t\u00eb shprehte, ishte nj\u00eb sintaks\u00eb e thjesht\u00eb '\u00e7el\u00ebs-vler\u00eb', por n\u00eb vend t\u00eb k\u00ebsaj ai zgjodhi nj\u00eb vendim krejt\u00ebsisht t\u00eb \u00e7uditsh\u00ebm p\u00ebr t\u00eb aplikuar XML, duke detyruar p\u00ebrdorimin e nj\u00eb elementi t\u00eb zbraz\u00ebt si nj\u00eb prefiks p\u00ebr t\u00eb p\u00ebrdorur sintaks\u00ebn e atributeve. K\u00ebto skema m\u00eb hasen shum\u00eb shpesh.<\/p>\n<pre><code class=\"xml\">John\n  London<\/code><\/pre>\n<p>\nKjo \u00ebsht\u00eb disi m\u00eb mir\u00eb, por tani \u00e7el\u00ebsat p\u00ebr nj\u00eb arsye jan\u00eb metadata, nd\u00ebrsa vlerat jo. Nj\u00eb pik\u00ebpamje shum\u00eb e \u00e7uditshme p\u00ebr rregulloret. N\u00ebse hiqni t\u00eb gjitha etiketat dhe atributet, do t\u00eb humbas\u00eb gjysm\u00ebn e informacionit.<\/p>\n<p>Shprehja e sakt\u00eb e rregullor\u00ebs n\u00eb XML do t\u00eb dukej k\u00ebshtu:<\/p>\n<pre><code class=\"xml\">Name\n    John\n  \n  \n    City\n    London<\/code><\/pre>\n<p>\nPor n\u00ebse njer\u00ebzit pranojn\u00eb nj\u00eb vendim t\u00eb \u00e7uditsh\u00ebm p\u00ebr t\u00eb aplikuar XML si format t\u00eb dh\u00ebnash dhe m\u00eb pas t\u00eb rendisin rregulloren me t\u00eb, ata duhet t\u00eb kuptojn\u00eb se ajo q\u00eb po b\u00ebjn\u00eb \u00ebsht\u00eb e pap\u00ebrshtatshme dhe e pak\u00ebndshme. Shpesh, dizajnuesit zgjedhin gabimisht XML p\u00ebr t\u00eb nd\u00ebrtuar aplikacionet e tyre. Por edhe m\u00eb shpesh, ata p\u00ebrkeq\u00ebsojn\u00eb situat\u00ebn duke aplikuar XML pa kuptim n\u00eb nj\u00ebr\u00ebn nga format e p\u00ebrmendura m\u00eb sip\u00ebr, duke injoruar faktin se XML thjesht nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr k\u00ebt\u00eb.<\/p>\n<p><b>Schemi m\u00eb e keqe XML?<\/b> P\u00ebr m\u00eb tep\u00ebr, \u00e7mimi p\u00ebr <i>schem\u00ebn m\u00eb t\u00eb keqe XML q\u00eb kam par\u00eb ndonj\u00ebher\u00eb,<\/i> e merr formati i skedarit t\u00eb konfigurimit p\u00ebr ndarjen automatike t\u00eb burimeve p\u00ebr telefonat IP t\u00eb telekomunikacionit Polycom. K\u00ebta skedar\u00eb k\u00ebrkojn\u00eb ngarkimin e skedar\u00ebve XML t\u00eb k\u00ebrkesave p\u00ebrmes TFTP, t\u00eb cilat... Pra, ja nj\u00eb fragment nga nj\u00eb skedar i till\u00eb:<\/p>\n<pre><code class=\"xml\">&lt;softkey\n        softkey.feature.directories=\"0\"\n        softkey.feature.buddies=\"0\"\n        softkey.feature.forward=\"0\"\n        softkey.feature.meetnow=\"0\"\n        softkey.feature.redial=\"1\"\n        softkey.feature.search=\"1\"\n\n        softkey.1.enable=\"1\"\n        softkey.1.use.idle=\"1\"\n        softkey.1.label=\"Foo\"\n        softkey.1.insert=\"1\"\n        softkey.1.action=\"...\"\n\n        softkey.2.enable=\"1\"\n        softkey.2.use.idle=\"1\"\n        softkey.2.label=\"Bar\"\n        softkey.2.insert=\"2\"\n        softkey.2.action=\"...\" \/&gt;<\/code><\/pre>\n<p>\nKjo nuk \u00ebsht\u00eb nj\u00eb shaka e d\u00ebshtuar e dikujt. Dhe nuk \u00ebsht\u00eb imagjinata ime:<\/p>\n<ul>\n<li>Elementet p\u00ebrdoren thjesht si prefiks p\u00ebr t\u00eb ngjitur atribute, t\u00eb cilat vet\u00eb kan\u00eb emra hierarkik\u00eb.\n<\/li>\n<li>N\u00ebse duhet t\u00eb bashk\u00ebngjitni vlera p\u00ebr disa instanca t\u00eb regjistrimeve t\u00eb nj\u00eb lloji t\u00eb caktuar, duhet t\u00eb p\u00ebrdorni emrat e atributeve, <i>n\u00eb t\u00eb cilat ka indekse<\/i>.\n<\/li>\n<li>P\u00ebrve\u00e7 k\u00ebsaj, atributet q\u00eb fillojn\u00eb me <code>softkey.<\/code>, duhet t\u00eb vendosen n\u00eb element\u00ebt <code>&lt;softkey\/&gt;<\/code>, atributet q\u00eb fillojn\u00eb me <code>feature.<\/code>, duhet t\u00eb vendosen n\u00eb element\u00ebt <code>&lt;feature\/&gt;<\/code> etj., megjith\u00ebse kjo duket krejt\u00ebsisht e tep\u00ebrt dhe n\u00eb pamje t\u00eb par\u00eb pa kuptim.\n<\/li>\n<li>Dhe, p\u00ebrfundimisht, n\u00ebse shpresonit q\u00eb komponenti i par\u00eb i emrit t\u00eb atributit p\u00ebrfaq\u00ebson gjithmon\u00eb emrin e elementit \u2014 asgj\u00eb e till\u00eb! P\u00ebr shembull, atributet <code>up.<\/code> duhet t\u00eb bashk\u00ebngjiten n\u00eb <code>&lt;userpreferences\/&gt;<\/code>. Renditja e bashk\u00ebngjitjes s\u00eb emrave t\u00eb atributeve n\u00eb element\u00eb \u00ebsht\u00eb arbitrare, madje praktikisht plot\u00ebsisht.\n<\/li>\n<\/ul>\n<p>\n<b>Dokumentet ose t\u00eb dh\u00ebnat.<\/b>Koha pas kohe, ndokush b\u00ebn gj\u00ebra krejt\u00ebsisht t\u00eb \u00e7uditshme, duke u p\u00ebrpjekur t\u00eb krahasoj\u00eb XML dhe JSON, \u2014 dhe duke treguar k\u00ebshtu se nuk kupton asnj\u00ebrin, as tjetrin. XML \u00ebsht\u00eb nj\u00eb gjuh\u00eb markup dokumentesh. Nd\u00ebrsa JSON \u00ebsht\u00eb nj\u00eb format p\u00ebr t\u00eb dh\u00ebna t\u00eb strukturuara, k\u00ebshtu q\u00eb krahasimi i tyre me nj\u00ebri-tjetrin \u00ebsht\u00eb si t\u00eb provosh t\u00eb krahasosh t\u00eb ngrohta me t\u00eb buta.<\/p>\n<p>T\u00eb kuptosh k\u00ebt\u00eb do t\u00eb ndihmoj\u00eb koncepti i ndryshimit midis <i>dokumenteve dhe t\u00eb dh\u00ebnave.<\/i>Si analogji p\u00ebr XML mund t\u00eb marr\u00ebsh nj\u00eb dokument t\u00eb lexuesh\u00ebm nga makina. Edhe pse \u00ebsht\u00eb nd\u00ebrtuar p\u00ebr t'u lexuar nga makina, metaforikisht p\u00ebrfaq\u00ebson dokumentet, dhe nga ky k\u00ebndv\u00ebshtrim \u00ebsht\u00eb praktikisht i krahasuesh\u00ebm me dokumentet PDF, t\u00eb cilat shpesh her\u00eb nuk jan\u00eb lexueshm\u00ebrisht nga makina. <\/p>\n<p>P\u00ebr shembull, n\u00eb XML ka r\u00ebnd\u00ebsi rendi i elementeve. Nd\u00ebrsa n\u00eb JSON rendi i \u00e7iftave \"\u00e7el\u00ebs-vler\u00eb\" brenda objekteve nuk ka kuptim dhe nuk \u00ebsht\u00eb e p\u00ebrcaktuar. N\u00ebse d\u00ebshiron t\u00eb marr\u00ebsh nj\u00eb fjalor t\u00eb pa renditur nga \u00e7iftet \"\u00e7el\u00ebs-vler\u00eb\", rendi real me t\u00eb cilin ndodhen elementet n\u00eb k\u00ebt\u00eb skedar nuk ka r\u00ebnd\u00ebsi. Por mund t\u00eb formosh nga k\u00ebto t\u00eb dh\u00ebna shum\u00eb dokumente t\u00eb ndryshme, <i>dokumentesh,<\/i>p\u00ebr shkak se n\u00eb nj\u00eb dokument ka nj\u00eb renditje t\u00eb caktuar. Metaforikisht, kjo \u00ebsht\u00eb nj\u00eb analogji me nj\u00eb dokument n\u00eb let\u00ebr, megjith\u00ebse nuk ka dimensions fizike, n\u00eb kund\u00ebrshtim me nj\u00eb printim ose skedarin PDF.<\/p>\n<p>N\u00eb shembullin tim t\u00eb paraqitjes s\u00eb duhur t\u00eb fjalorit n\u00eb gjuh\u00ebn XML, tregohet rendi i elementeve n\u00eb fjalor, n\u00eb dallim nga paraqitja n\u00eb gjuh\u00ebn JSON. Nuk mund ta injoroj k\u00ebt\u00eb rend: kjo linearitet \u00ebsht\u00eb fillimisht e natyrshme p\u00ebr modelin e dokumenteve dhe formatin XML. Disa mund t\u00eb vendosin ta injorojn\u00eb k\u00ebt\u00eb rend gjat\u00eb interpretimit t\u00eb k\u00ebtij dokumenti XML, por \u00ebsht\u00eb e paarsyeshme t\u00eb diskutohet p\u00ebr k\u00ebt\u00eb, pasi ky \u00e7\u00ebshtje del jasht\u00eb diskutimit mbi v\u00ebrtet\u00eb formatin. P\u00ebr m\u00eb tep\u00ebr, n\u00ebse e b\u00ebni dokumentin t\u00eb shikuesh\u00ebm n\u00eb shfletues, duke i lidhur atij nj\u00eb tabel\u00eb stilesh, do t\u00eb mund t\u00eb shihni se elementet e fjalorit ndjekin nj\u00eb rend t\u00eb caktuar, dhe as n\u00eb ndonj\u00eb tjet\u00ebr.<\/p>\n<p>Me fjal\u00eb t\u00eb tjera, fjalori (nj\u00eb fragment i t\u00eb dh\u00ebnave t\u00eb strukturuara) mund t\u00eb konvertohet n\u00eb <i>n<\/i> dokumente t\u00eb ndryshme t\u00eb mundshme (n\u00eb formatin XML, PDF, n\u00eb let\u00ebr etj.), ku <i>n<\/i> \u2014 numri i kombinimeve t\u00eb mundshme t\u00eb elementeve n\u00eb fjalor, dhe kjo akoma nuk i kemi marr\u00eb parasysh variablat e tjera t\u00eb mundshme.<\/p>\n<p>Nj\u00ebkoh\u00ebsisht, nga kjo ndjek gjithashtu se n\u00ebse d\u00ebshironi t\u00eb transferoni vet\u00ebm t\u00eb dh\u00ebna, p\u00ebrdorimi i nj\u00eb dokumenti t\u00eb lexuesh\u00ebm nga makina do t\u00eb ishte joefektiv. Ai p\u00ebrdor nj\u00eb model q\u00eb n\u00eb k\u00ebt\u00eb rast \u00ebsht\u00eb i panevojsh\u00ebm, ai do t\u00eb pengonte vet\u00ebm. P\u00ebr m\u00eb tep\u00ebr, p\u00ebr t\u00eb nxjerr\u00eb t\u00eb dh\u00ebnat origjinale, do t\u00eb duhet t\u00eb shkruani nj\u00eb program. \u00cbsht\u00eb v\u00ebshtir\u00eb t\u00eb ket\u00eb kuptim t\u00eb p\u00ebrdorni XML p\u00ebr di\u00e7ka q\u00eb n\u00eb nj\u00eb faz\u00eb t\u00eb caktuar nuk do t\u00eb formohet si nj\u00eb dokument (p.sh., me CSS ose XSLT, ose t\u00eb dyja), pasi kjo \u00ebsht\u00eb arsyeja kryesore (n\u00ebse jo e vetme) p\u00ebr t\u00eb mbajtur modelin e dokumentit.<\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr, pasi n\u00eb XML nuk ka nj\u00eb nocion t\u00eb numrave (ose shprehjeve logjike, ose gjith\u00e7kaje tjet\u00ebr), t\u00eb gjitha numrat e paraqitur n\u00eb k\u00ebt\u00eb format trajtohen vet\u00ebm si tekst t\u00eb shtuar. P\u00ebr t\u00eb nxjerr\u00eb t\u00eb dh\u00ebnat, duhet t\u00eb dihet skema dhe lidhja e saj me t\u00eb dh\u00ebnat p\u00ebrkat\u00ebse q\u00eb shprehen. Gjithashtu, duhet t\u00eb dihet se kur, n\u00eb p\u00ebrputhje me kontekstin, nj\u00eb element i caktuar i tekstit p\u00ebrb\u00ebn nj\u00eb num\u00ebr dhe duhet t\u00eb konvertohet n\u00eb num\u00ebr, etj.<\/p>\n<p>Prarr se, procesi i nxjerrjes s\u00eb t\u00eb dh\u00ebnave nga dokumentet XML nuk \u00ebsht\u00eb shum\u00eb ndryshe nga procesi i njohjes s\u00eb dokumenteve t\u00eb skanuara q\u00eb p\u00ebrmbajn\u00eb, p\u00ebr shembull, tabela q\u00eb formojn\u00eb shum\u00eb faqe t\u00eb dh\u00ebnash numerike. Po, n\u00eb parim \u00ebsht\u00eb e mundur, por nuk \u00ebsht\u00eb rruga m\u00eb e optimizuar, p\u00ebrve\u00e7se n\u00eb raste ekstreme kur nuk ka alternativa t\u00eb tjera. Nj\u00eb zgjidhje e arsyeshme do t\u00eb ishte thjesht t\u00eb gjejm\u00eb nj\u00eb kopje digjitale t\u00eb t\u00eb dh\u00ebnave origjinale, q\u00eb nuk jan\u00eb t\u00eb inkorporuara n\u00eb modelin e dokumentit, n\u00eb t\u00eb cilin t\u00eb dh\u00ebnat jan\u00eb t\u00eb bashkuara me p\u00ebrfaq\u00ebsimin e tyre specifik tekstual.<\/p>\n<p>Prandaj, nuk m\u00eb befason aspak q\u00eb XML \u00ebsht\u00eb popullor n\u00eb biznes. Arsyeja p\u00ebr k\u00ebt\u00eb \u00ebsht\u00eb se formati i dokumenteve (n\u00eb let\u00ebr) \u00ebsht\u00eb i kuptuesh\u00ebm dhe i njohur p\u00ebr biznesin, dhe ata duan t\u00eb vazhdojn\u00eb t\u00eb p\u00ebrdorin nj\u00eb model q\u00eb jan\u00eb m\u00ebsuar. P\u00ebr t\u00eb nj\u00ebjt\u00ebn arsye, n\u00eb biznes shpesh p\u00ebrdoren dokumentet n\u00eb PDF n\u00eb vend t\u00eb formateve m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr p\u00ebrpunim automatike \u2013 sepse ata jan\u00eb akoma t\u00eb lidhur me konceptin e faqeve t\u00eb printuara me nj\u00eb madh\u00ebsi fizike t\u00eb caktuar. Kjo ndodh edhe me dokumentet q\u00eb nuk do t\u00eb printohen ndonj\u00ebher\u00eb (p\u00ebr shembull, nj\u00eb skedar PDF t\u00eb dokumentacionit t\u00eb regjistrit me 8000 faqe). Nga ky k\u00ebndv\u00ebshtrim, p\u00ebrdorimi i XML n\u00eb biznes \u00ebsht\u00eb n\u00eb thelb nj\u00eb manifestim i skevomorfizmit. Nj\u00eb ide metaforike e faqes s\u00eb printuar me nj\u00eb madh\u00ebsi t\u00eb kufizuar \u00ebsht\u00eb e kuptueshme p\u00ebr njer\u00ebzit, dhe ata e kuptojn\u00eb si t\u00eb krijojn\u00eb procese biznesi mbi baz\u00ebn e dokumenteve t\u00eb printuara. N\u00ebse kjo \u00ebsht\u00eb referenca juaj, dokumentet pa nj\u00eb madh\u00ebsi fizike t\u00eb kufizuar, t\u00eb cilat jan\u00eb t\u00eb lexueshme nga makina \u2013 dokumentet XML \u2013 p\u00ebrfaq\u00ebsojn\u00eb nj\u00eb inovacion, duke q\u00ebn\u00eb nj\u00ebkoh\u00ebsisht nj\u00eb ekuivalent t\u00eb njohur dhe t\u00eb rehatsh\u00ebm t\u00eb dokumentit. Kjo nuk ndalon q\u00eb ato t\u00eb mbeten nj\u00eb m\u00ebnyr\u00eb e pav\u00ebrtet\u00eb dhe tep\u00ebr skevomorfike p\u00ebr t\u00eb paraqitur t\u00eb dh\u00ebna.<\/p>\n<p>Sot, skemat e vetme XML q\u00eb un\u00eb v\u00ebrtet mund t'i quaj p\u00ebrdorim t\u00eb sakt\u00eb t\u00eb k\u00ebtij formati jan\u00eb XHTML dhe DocBook.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/mailru\/blog\/475474\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042f\u0437\u044b\u043a XML \u0431\u044b\u043b \u0438\u0437\u043e\u0431\u0440\u0435\u0442\u0435\u043d \u0432 1996 \u0433\u043e\u0434\u0443. \u0415\u0434\u0432\u0430 \u043e\u043d \u0443\u0441\u043f\u0435\u043b \u043f\u043e\u044f\u0432\u0438\u0442\u044c\u0441\u044f, \u043a\u0430\u043a \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0435\u0433\u043e \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0443\u0436\u0435 \u043d\u0430\u0447\u0430\u043b\u0438 \u043f\u043e\u043d\u0438\u043c\u0430\u0442\u044c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e, \u0438 \u0434\u043b\u044f \u0442\u0435\u0445 \u0446\u0435\u043b\u0435\u0439, \u043a \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u0435\u0433\u043e \u043f\u044b\u0442\u0430\u043b\u0438\u0441\u044c \u0430\u0434\u0430\u043f\u0442\u0438\u0440\u043e\u0432\u0430\u0442\u044c, \u043e\u043d \u0431\u044b\u043b \u043d\u0435 \u043b\u0443\u0447\u0448\u0438\u043c \u0432\u044b\u0431\u043e\u0440\u043e\u043c. \u041d\u0435 \u0431\u0443\u0434\u0435\u0442 \u043f\u0440\u0435\u0443\u0432\u0435\u043b\u0438\u0447\u0435\u043d\u0438\u0435\u043c \u0441\u043a\u0430\u0437\u0430\u0442\u044c, \u0447\u0442\u043e \u043f\u043e\u0434\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0435 \u0431\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u0441\u0445\u0435\u043c XML, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043d\u0435 \u0434\u043e\u0432\u043e\u0434\u0438\u043b\u043e\u0441\u044c \u0432\u0438\u0434\u0435\u0442\u044c, \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u043b\u0438 \u0441\u043e\u0431\u043e\u0439 \u043d\u0435\u0446\u0435\u043b\u0435\u0441\u043e\u043e\u0431\u0440\u0430\u0437\u043d\u043e\u0435 \u0438\u043b\u0438 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435 XML. \u0411\u043e\u043b\u0435\u0435 \u0442\u043e\u0433\u043e, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":52641,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-52640","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u042f\u0437\u044b\u043a XML \u0431\u044b\u043b \u0438\u0437\u043e\u0431\u0440\u0435\u0442\u0435\u043d \u0432 1996 \u0433\u043e\u0434\u0443.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47XML \u043f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438 \u0432\u0441\u0435\u0433\u0434\u0430 \u043f\u0440\u0438\u043c\u0435\u043d\u044f\u0435\u0442\u0441\u044f \u043d\u0435 \u043f\u043e \u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u044e | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u042f\u0437\u044b\u043a XML \u0431\u044b\u043b \u0438\u0437\u043e\u0431\u0440\u0435\u0442\u0435\u043d \u0432 1996 \u0433\u043e\u0434\u0443.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-11-12T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:00:25+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47XML p\u00ebrdoret pothuajse gjithmon\u00eb p\u00ebr q\u00ebllime t\u00eb gabuara | ProHoster","description":"Gjuha XML u shpik n\u00eb vitin 1996.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47XML \u043f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438 \u0432\u0441\u0435\u0433\u0434\u0430 \u043f\u0440\u0438\u043c\u0435\u043d\u044f\u0435\u0442\u0441\u044f \u043d\u0435 \u043f\u043e \u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u044e | ProHoster","og:description":"\u042f\u0437\u044b\u043a XML \u0431\u044b\u043b \u0438\u0437\u043e\u0431\u0440\u0435\u0442\u0435\u043d \u0432 1996 \u0433\u043e\u0434\u0443.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/xml-prakticheski-vsegda-primenyaetsya-ne-po-naznacheniyu","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-11-12T21:00:00+00:00","article:modified_time":"2020-02-18T11:00:25+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52640","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 04:19:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:11:32","updated":"2026-01-24 04:19:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/52640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=52640"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/52640\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/52641"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=52640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=52640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=52640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}