{"id":494,"date":"2026-10-28T01:40:06","date_gmt":"2026-10-28T01:40:06","guid":{"rendered":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/"},"modified":"2026-10-28T01:40:09","modified_gmt":"2026-10-28T01:40:09","slug":"master-use-case-modeling-visual-paradigm-vp-opendocs-integration","status":"publish","type":"gallery","link":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/","title":{"rendered":"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs"},"content":{"rendered":"<div class=\"vpg-article-wrapper\" style=\"max-width: 100% !important; width: 100% !important; box-sizing: border-box !important; overflow-wrap: break-word !important; word-break: break-word !important; min-width: 0 !important;\">\n<p style=\"max-width: 100% !important; box-sizing: border-box !important; text-align: center !important; margin: 1.5rem 0 !important;\"><img alt=\"Diagram use case sistem pemesanan kamar hotel yang menampilkan aktor Pelanggan dan Staf Hotel.\" data-fifu-alt=\"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.\" decoding=\"async\" fifu-alt=\"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.\" src=\"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png\" style=\"max-width: 100% !important; height: auto !important; display: block !important; margin: 0 auto !important; box-sizing: border-box !important; border-radius: 6px !important;\" title=\"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.\"\/><\/p>\n<p>Dalam rekayasa perangkat lunak modern, kesenjangan antara desain dan dokumentasi sering kali dipenuhi dengan hambatan. Tim memodelkan sistem mereka dalam alat desktop yang kuat seperti Visual Paradigm, hanya untuk menemukan bahwa dokumentasi yang dihasilkan bersifat statis, usang, atau sulit diakses oleh para pemangku kepentingan. Tutorial ini menjembatani kesenjangan tersebut, menjelaskan cara memanfaatkan<strong>Pipa Visual Paradigm<\/strong>untuk mengintegrasikan<strong>Diagram Kasus Penggunaan<\/strong>langsung ke dalam<strong>OpenDocs<\/strong>.<\/p>\n<p>Kami akan menelusuri arsitektur Sistem Pemesanan Kamar Hotel, mendemonstrasikan cara mendefinisikan aktor, memetakan persyaratan fungsional, dan memanfaatkan hubungan lanjutan seperti<code>&lt;&lt;include&gt;&gt;<\/code>untuk menciptakan alur kerja dokumentasi yang hidup dan tersinkronisasi.<\/p>\n<h2>1. Memahami Arsitektur Model Kasus Penggunaan<\/h2>\n<p>Diagram Kasus Penggunaan bukan sekadar gambar; ini adalah cetak biru struktural fungsionalitas sistem dari perspektif pengguna. Diagram ini mengidentifikasi<strong>aktor<\/strong>(pengguna atau sistem eksternal) dan<strong>kasus penggunaan<\/strong>(tindakan yang dilakukan sistem).<\/p>\n<h3>Sistem Pemesanan Kamar Hotel<\/h3>\n<p>Mari kita analisis entitas inti yang terlibat dalam sistem contoh kami:<\/p>\n<ul>\n<li><strong>Pelanggan:<\/strong>Pengguna utama yang memulai proses pemesanan.<\/li>\n<li><strong>Staf Hotel:<\/strong>Sebuah aktor administratif yang mampu mengelola reservasi dan modifikasi.<\/li>\n<li><strong>Sistem Pemesanan Kamar Hotel:<\/strong>Batas yang mencakup semua proses internal.<\/li>\n<\/ul>\n<p>Dengan mendefinisikan batas-batas ini dengan jelas, kami memastikan bahwa dokumentasi selanjutnya yang dihasilkan di OpenDocs tetap akurat sesuai dengan ruang lingkup sistem.<\/p>\n<h2>2. Memetakan Persyaratan Fungsional dan Hubungan<\/h2>\n<p>Setelah aktor didefinisikan, kami memetakan fungsi-fungsi spesifik. Dalam arsitektur yang disediakan, kami mengamati tiga interaksi berbeda untuk Pelanggan dan satu untuk Staf.<\/p>\n<ol>\n<li><strong>Modifikasi Pemesanan:<\/strong>Sebuah tindakan yang memungkinkan perubahan pada reservasi yang sudah ada.<\/li>\n<li><strong>Cari Kamar Tersedia:<\/strong> Fungsi kueri untuk memeriksa stok.<\/li>\n<li><strong>Pesan Kamar:<\/strong> Kasus penggunaan transaksional utama.<\/li>\n<li><strong>Batalkan Reservasi:<\/strong> Tindakan pembatalan yang dikelola oleh staf.<\/li>\n<\/ol>\n<h3>Pemodelan Lanjutan: Hubungan &lt;&lt;include&gt;&gt;<\/h3>\n<p>Konsep kritis dalam diagram ini adalah <strong>Include<\/strong> (direpresentasikan dengan panah putus-putus dengan stereotipe <code>&lt;&lt;include&gt;&gt;<\/code>). Ini menunjukkan bahwa kasus penggunaan tertentu <em>harus<\/em> terjadi sebagai bagian dari kasus penggunaan lain.<\/p>\n<p>Dalam contoh kami:<\/p>\n<ul>\n<li>Proses <strong>Pesan Kamar<\/strong> tidak berdiri sendiri. Proses ini <em>memuat<\/em> <strong>Periksa Ketersediaan Kamar<\/strong> dan <strong>Bayar Biaya Pemesanan<\/strong>.<\/li>\n<li>Dengan menggunakan <code>&lt;&lt;include&gt;&gt;<\/code>, kami menghindari redundansi. Jika kami perlu mengubah logika untuk &#8220;Bayar Biaya Pemesanan,&#8221; kami akan memperbaruinya di satu tempat, dan perubahan tersebut akan tercermin di setiap skenario yang memuatnya.<\/li>\n<\/ul>\n<h2>3. Alur Kerja &#8220;Konsep ke Dokumen&#8221;<\/h2>\n<p>Kekuatan sejati dari arsitektur ini terletak pada sinkronisasi antara alat pemodelan dan platform dokumentasi. Berikut adalah alur kerja teknis langkah demi langkah:<\/p>\n<h3>Langkah 1: Pemodelan di Desktop<\/h3>\n<p>Mulailah dengan membuat diagram di Visual Paradigm Desktop. Pastikan diagram tersebut bersih, menggunakan notasi UML standar, dan memberi label dengan jelas pada <code>&lt;&lt;include&gt;&gt;<\/code> hubungan. Ini berfungsi sebagai &#8220;Sumber Kebenaran Tunggal.&#8221;<\/p>\n<h3>Langkah 2: Sinkronisasi Pipa<\/h3>\n<p>Saat siap untuk mendokumentasikan, fitur &#8220;Pipeline&#8221; berfungsi sebagai mekanisme transportasi. Fitur ini menangkap artefak diagram dan mendorongnya ke repositori OpenDocs. Ini bukan ekspor gambar statis (seperti JPG); ini adalah transfer artefak terstruktur.<\/p>\n<h3>Langkah 3: Integrasi di OpenDocs<\/h3>\n<p>Setelah tiba di OpenDocs, diagram disematkan langsung ke halaman dokumentasi. Seperti yang ditunjukkan pada antarmuka, diagram tetap dapat diedit. Hal ini memungkinkan penulis teknis atau pemangku kepentingan untuk memberi anotasi pada diagram tanpa meninggalkan konteks dokumentasi. Sistem secara otomatis menangani kontrol versi, memastikan bahwa jika diagram diperbarui di Desktop, versi OpenDocs dapat diperbarui untuk mencerminkan keadaan terbaru.<\/p>\n<aside class=\"vpg-callout-box vpg-did-you-know\">\n<h4>\ud83d\udca1 Tips Pro: Mengelola Include vs. Extend<\/h4>\n<p>Sementara <code>&lt;&lt;include&gt;&gt;<\/code> bersifat wajib (misalnya, Anda tidak dapat memesan kamar tanpa membayar), <code>&lt;&lt;extend&gt;&gt;<\/code> bersifat opsional. Saat memodelkan sistem Pemesanan Hotel, gunakan <code>&lt;&lt;extend&gt;&gt;<\/code> untuk skenario seperti &#8220;Terapkan Kode Diskon,&#8221; yang hanya terjadi jika pengguna memilih untuk memasukkan kode, sehingga menjaga alur utama Anda tetap bersih.<\/p>\n<\/aside>\n<h2>4. Manfaat Arsitektur Terintegrasi<\/h2>\n<p>Mengadopsi alur kerja ini mengubah cara tim menangani utang teknis. Dengan menghubungkan lingkungan pemodelan secara langsung ke platform dokumentasi, Anda mencapai hal-hal berikut:<\/p>\n<ul>\n<li><strong>Akurasi Real-time:<\/strong> Pemangku kepentingan selalu melihat versi terkini dari logika sistem.<\/li>\n<li><strong>Beban Berkurang:<\/strong> Tidak diperlukan tangkapan layar manual atau salin-tempel.<\/li>\n<li><strong>Ulasan Kolaboratif:<\/strong> Panel &#8220;Artefak yang Digunakan&#8221; di OpenDocs memungkinkan tim untuk meninjau riwayat revisi diagram langsung di dalam antarmuka dokumentasi.<\/li>\n<\/ul>\n<p>Dengan memahami elemen struktural diagram Use Case dan memanfaatkan integrasi pipa, tim dapat memastikan bahwa dokumentasi mereka berkembang seiring dengan sistem mereka, mempertahankan standar tinggi komunikasi teknis.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Bridge the gap between Visual Paradigm and OpenDocs by learning to integrate UML Use Case Diagrams into a synchronized documentation workflow for hotel booking systems.<\/p>\n","protected":false},"author":1,"featured_media":495,"template":"","meta":{"inline_featured_image":false,"_eb_attr":"","source_url":"https:\/\/www.ez-knowledge.com\/mastering-the-visual-paradigm-desktop-to-opendocs-pipeline\/","source_h1_title":"","fifu_image_url":"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png","fifu_image_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","_fifu_image_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","fifu_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","_fifu_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","fifu_image_title":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","_fifu_image_title":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","fifu_input_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","vp_image_hash":"8d9d521932165e83e765b9065b4ac3fbef44357df0d89f062b58ccffba5c54b7"},"asset-category":[30,26],"class_list":["post-494","gallery","type-gallery","status-publish","has-post-thumbnail","hentry","asset-category-visual-paradigm","asset-category-vp-opendocs"],"source_url":"https:\/\/www.ez-knowledge.com\/mastering-the-visual-paradigm-desktop-to-opendocs-pipeline\/","source_h1_title":"","fifu_image_url":"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png","fifu_image_alt":"Hotel room booking system use case diagram showing Customer and Hotel Staff actors.","vp_image_hash":"8d9d521932165e83e765b9065b4ac3fbef44357df0d89f062b58ccffba5c54b7","yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia\" \/>\n<meta property=\"og:description\" content=\"Bridge the gap between Visual Paradigm and OpenDocs by learning to integrate UML Use Case Diagrams into a synchronized documentation workflow for hotel booking systems.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/\" \/>\n<meta property=\"og:site_name\" content=\"Go PDF Kit Indonesia\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-28T01:40:09+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png\" \/><meta property=\"og:image\" content=\"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1192\" \/>\n\t<meta property=\"og:image:height\" content=\"724\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"3 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/\",\"url\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/\",\"name\":\"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia\",\"isPartOf\":{\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png\",\"datePublished\":\"2026-10-28T01:40:06+00:00\",\"dateModified\":\"2026-10-28T01:40:09+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage\",\"url\":\"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png\",\"contentUrl\":\"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png\",\"width\":1192,\"height\":724},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.go-pdfkit.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.go-pdfkit.com\/id\/#website\",\"url\":\"https:\/\/www.go-pdfkit.com\/id\/\",\"name\":\"Go PDF Kit Indonesia\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.go-pdfkit.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/","og_locale":"id_ID","og_type":"article","og_title":"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia","og_description":"Bridge the gap between Visual Paradigm and OpenDocs by learning to integrate UML Use Case Diagrams into a synchronized documentation workflow for hotel booking systems.","og_url":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/","og_site_name":"Go PDF Kit Indonesia","article_modified_time":"2026-10-28T01:40:09+00:00","og_image":[{"url":"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png","type":"","width":"","height":""},{"width":1192,"height":724,"url":"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_image":"https:\/\/www.visual-paradigm.com\/servlet\/editor-content\/guide\/visual-paradigms-pipeline-hands-on-review-of-visual-paradigms-desktop-to-opendocs-integration\/sites\/7\/2026\/05\/img_69c35791cace1.png","twitter_misc":{"Estimasi waktu membaca":"3 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/","url":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/","name":"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs - Go PDF Kit Indonesia","isPartOf":{"@id":"https:\/\/www.go-pdfkit.com\/id\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage"},"image":{"@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage"},"thumbnailUrl":"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png","datePublished":"2026-10-28T01:40:06+00:00","dateModified":"2026-10-28T01:40:09+00:00","breadcrumb":{"@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/"]}]},{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#primaryimage","url":"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png","contentUrl":"https:\/\/www.go-pdfkit.com\/id\/wp-content\/uploads\/sites\/8\/2026\/10\/img_69c35791cace1.png","width":1192,"height":724},{"@type":"BreadcrumbList","@id":"https:\/\/www.go-pdfkit.com\/id\/gallery\/master-use-case-modeling-visual-paradigm-vp-opendocs-integration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.go-pdfkit.com\/id\/"},{"@type":"ListItem","position":2,"name":"Pemodelan Kasus Penggunaan Utama: Integrasi Visual Paradigm ke VP OpenDocs"}]},{"@type":"WebSite","@id":"https:\/\/www.go-pdfkit.com\/id\/#website","url":"https:\/\/www.go-pdfkit.com\/id\/","name":"Go PDF Kit Indonesia","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.go-pdfkit.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"}]}},"_links":{"self":[{"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/gallery\/494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/gallery"}],"about":[{"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/types\/gallery"}],"author":[{"embeddable":true,"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/users\/1"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/media\/495"}],"wp:attachment":[{"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/media?parent=494"}],"wp:term":[{"taxonomy":"asset-category","embeddable":true,"href":"https:\/\/www.go-pdfkit.com\/id\/wp-json\/wp\/v2\/asset-category?post=494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}