{"id":632,"date":"2026-09-18T18:30:00","date_gmt":"2026-09-18T09:30:00","guid":{"rendered":"https:\/\/www.dtc.teu.ac.jp\/?p=632"},"modified":"2026-09-18T18:30:00","modified_gmt":"2026-09-18T09:30:00","slug":"cc5-tokkio-avatar","status":"publish","type":"post","link":"https:\/\/www.dtc.teu.ac.jp\/ja\/cc5-tokkio-avatar\/","title":{"rendered":"Character Creator 5\u3068Unreal Engine\u3067NVIDIA Tokkio\u7528\u30ab\u30b9\u30bf\u30e0\u30a2\u30d0\u30bf\u30fc\u3092\u4f5c\u6210\u3059\u308b"},"content":{"rendered":"\n

A conversational avatar starts with a reliable character asset, not with a running service. Before connecting speech and facial animation, we need a complete character, correctly reconstructed materials, and facial morph targets that the renderer can actually drive. [1]<\/a> [2]<\/a><\/p>\n\n\n\n

This first article explains how to prepare a Character Creator 5 (CC5) avatar for an Unreal Engine-based NVIDIA Tokkio workflow. We cover character preparation, FBX export, Reallusion Auto Setup import, and asset-level validation. The endpoint is a saved Unreal avatar and a documented handoff. A separate article by another contributor will cover ACE runtime integration, Tokkio configuration, packaging, deployment, and live-stream testing.<\/p>\n\n\n\n

\n
\n Article Scope & Pipeline Boundary<\/span>\n <\/div>\n

\n Scope of this guide:<\/strong> Character Creator 5 (CC5) avatar preparation, clean FBX\/JSON export, Reallusion Auto Setup 2.02 import into Unreal Engine 5.5.4, and asset-level 52-morph target validation.\n <\/p>\n

\n Downstream note:<\/em> Tokkio ACE microservices, live audio streaming, and C++ runtime renderer implementation are covered in a dedicated follow-up article.\n <\/p>\n<\/div>\n\n\n\n

\n
\n Contents & Pipeline Stages<\/span>\n Technical Guide<\/span>\n <\/div>\n
\n
\n

1.<\/strong> Define the deliverable before starting<\/a><\/p>\n

2.<\/strong> Agree on a compatible toolchain<\/a><\/p>\n

3.<\/strong> Prepare the complete character in CC5<\/a><\/p>\n

4.<\/strong> Export a complete FBX bundle<\/a><\/p>\n

5.<\/strong> Prepare Unreal and Reallusion Auto Setup<\/a><\/p>\n

6.<\/strong> Import character with materials & morphs<\/a><\/p>\n <\/div>\n

\n

7.<\/strong> Validate facial-animation contract<\/a><\/p>\n

8.<\/strong> Review saved avatar in Unreal<\/a><\/p>\n

9.<\/strong> Common problems & where to fix them<\/a><\/p>\n

10.<\/strong> Hand off reproducible avatar package<\/a><\/p>\n

Where the next article begins<\/a><\/p>\n

References & Documentation<\/a><\/p>\n <\/div>\n <\/div>\n<\/div>\n\n\n\n

\"NVIDIA
The custom character avatar running in the live NVIDIA Tokkio streaming interface.<\/figcaption><\/figure>\n\n\n\n

1. Define the deliverable before starting<\/h2>\n\n\n\n

The preparation pipeline follows strict checkpoints from asset creation to runtime handover. Each transition must be verified independently:<\/p>\n\n\n\n

A good-looking character in CC5 does not prove that its exported textures resolve, and a clean Unreal viewport does not prove that facial animation targets were correctly imported.<\/p><\/p>\n\n\n\n

For this article, \u201cready for integration\u201d means that the complete character has been exported, imported, saved, reopened, and checked for the facial targets expected by the downstream mapping. It does not mean that Tokkio has been deployed or that speech-driven animation has been verified.<\/p>\n\n\n\n

2. Agree on a compatible toolchain<\/h2>\n\n\n\n

In this implementation workflow, we use Unreal Engine 5.5.4<\/strong> as the baseline, aligned with an ACE package specifically targeting Unreal Engine 5.5. This is a version-specific baseline, not a recommendation to combine any current CC5, Unreal, and ACE releases. Confirm the engine version with the integration owner before creating production assets.<\/p>\n\n\n\n

For avatar authoring, prepare CC5, an Unreal Engine installation agreed with the integration owner, and an engine-compatible Reallusion Auto Setup package. Inspect plugin descriptors and the documentation bundled with the installed release rather than relying on a ZIP filename. Do not mix plugin binaries built for different Unreal minor versions. [2]<\/a> [6]<\/a><\/p>\n\n\n\n

Record the exact CC5 version, Unreal version, Auto Setup version, export directory, Unreal project path, skeletal mesh asset path, and the intended facial profile. For example, Reallusion Auto Setup 2.02 was verified in this pipeline; check your exact installed plugin version for compatibility. ACE renderer plugins and the build\/deployment toolchain belong to the next stage, but their compatibility constraints should be agreed now to avoid re-importing into another engine version later.<\/p>\n\n\n\n

<\/p>\n\n\n\n

3. Prepare the complete character in CC5<\/h2>\n\n\n\n

Finalize the character\u2019s appearance before export, then check the component tree. Exporting only the base body can produce an apparently successful import while leaving important renderable parts behind. Confirm that the character includes its mesh and skeleton, clothing and required materials, eyes, teeth, tongue, tear ducts, and eyelashes. Review these parts together in the neutral pose.<\/p>\n\n\n\n

The facial profile is especially important. Use an Extended \/ ARKit-compatible facial profile<\/strong> with expressions available. In Character Creator, navigate to the Modify<\/strong> panel > Motion<\/strong> > Facial Profile Editor<\/strong> to verify that the Expression node explicitly reads “CC4 Extended”<\/strong>. Do not select a facial profile of None<\/strong> or standard profiles that omit ARKit-level micro-expressions. A character can render perfectly while lacking the shape changes needed for speech, blinking, or subtle emotive expressions. [3]<\/a><\/p>\n\n\n\n

\"Reallusion
Reallusion facial-profile UI. Confirm an Extended \/ ARKit-compatible profile in your installed CC5 version. Source: Reallusion documentation<\/a>. [3]<\/a><\/figcaption><\/figure>\n\n\n\n

Keep the original topology for this reference workflow unless you have a separately validated reason to change it. Topology or facial-profile changes should trigger another morph-coverage check. Also decide whether the export contains the current pose or whether body animation will be delivered separately; do not leave that decision implicit. [4]<\/a><\/p>\n\n\n\n

4. Export a complete FBX bundle<\/h2>\n\n\n\n

In CC5, open File \u2192 Export \u2192 FBX \u2192 Clothed Character<\/strong> and select the Unreal Engine<\/strong> preset\u2014specifically setting the target tool preset to Unreal (UE5 Skeleton)<\/strong>. Ensure the base reference pose is set to A-Pose<\/strong> (or the matching bind pose for the UE5 mannequin). Include the complete character, enable the required facial morphs, and export both textures and the Reallusion JSON sidecar. Keep Embed Textures<\/strong> disabled and verify that Export JSON for Auto Material Setup<\/strong> is enabled in the advanced settings. Leave InstaLOD \/ Remesher<\/strong> disabled; altering mesh topology at export time can disrupt morph vertex IDs and cause facial targets to deform incorrectly or fail during import. [4]<\/a> [5]<\/a><\/p>\n\n\n\n

\"Character
Reallusion FBX export UI. Choose the Unreal Engine target and export the complete character; option labels vary by version. Source: Reallusion documentation<\/a>. [4]<\/a><\/figcaption><\/figure>\n\n\n\n

The JSON sidecar is part of the asset, not optional housekeeping. Reallusion Auto Setup uses the accompanying metadata to reconstruct the intended material setup. Keep it next to the matching FBX, and preserve the relative texture paths generated during export. [4]<\/a> [5]<\/a><\/p>\n\n\n\n

\"Export
Reallusion JSON export reference. Keep the generated JSON beside the matching FBX for Auto Setup. Source: Reallusion documentation<\/a>. [5]<\/a><\/figcaption><\/figure>\n\n\n\n
\n
\n Export Bundle Structure<\/span>\n Directory Layout<\/span>\n <\/div>\n 
AvatarExport\/\n\u251c\u2500\u2500 CharacterName.fbx         # Mesh, skeleton, and embedded morph targets\n\u251c\u2500\u2500 CharacterName.json        # Reallusion Auto Setup material metadata\n\u251c\u2500\u2500 CharacterName.fbm\/        # Base color (diffuse) and normal maps\n\u2514\u2500\u2500 textures\/                 # Metallic, roughness, opacity, and AO maps<\/code><\/pre>\n<\/div>\n\n\n\n
This layout reflects Reallusion\u2019s standard external export structure. When Embed Textures<\/em> is disabled, Character Creator automatically splits textures between two locations: the CharacterName.fbm\/<\/code> folder holds base color (diffuse) and normal maps, while the companion textures\/<\/code> folder holds roughness, metallic, opacity, and ambient occlusion maps. The JSON sidecar maps all these relative paths for Unreal. The essential checks are that the FBX is non-empty, the JSON has the matching basename and parses successfully, and every texture referenced by the JSON exists at the resolved path. Keep both the .fbm<\/code> and textures\/<\/code> directories beside the FBX and JSON during transfer. [5]<\/a><\/p>\n\n\n\n
Keep a small export record containing file paths, byte sizes, timestamps, and the results of the checks above. Fix missing files or broken references in the export bundle before importing. Copying only the FBX to another machine is not a complete handoff.<\/p>\n\n\n\n
5. Prepare Unreal and Reallusion Auto Setup<\/h2>\n\n\n\n
Create or select the project using the agreed Unreal version. The complete reference implementation uses a C++ project for its later project-owned runtime actor. Asset preparation does not require implementing that actor in this article, but working in the intended project avoids unnecessary migration. Agree on a stable content location and skeletal mesh asset name with the integration owner.<\/p>\n\n\n\n
Install Reallusion Auto Setup following the guide bundled with that exact package. Preserve its Content<\/code> subtree and RLPlugin<\/code> directory structure; do not flatten or rename vendor folders. The reference project includes Plugins\/RLPlugin\/RLPlugin.uplugin<\/code>, together with Content\/CC_Shaders\/<\/code> and Content\/SSSProfile\/<\/code>. Treat these as reference paths and follow the installed package\u2019s instructions if its layout differs. [6]<\/a><\/p>\n\n\n\n
Enable the plugin and confirm that the editor starts without relevant plugin-load or compatibility errors. A plugin appearing in a folder is not enough: Unreal must load the correct build before you rely on its import behavior.<\/p>\n\n\n\n
\"Unreal
Reallusion plugin-panel reference in Unreal Engine. Use the package compatible with your installed Unreal Engine version. Source: Reallusion documentation<\/a>. [7]<\/a><\/figcaption><\/figure>\n\n\n\n
6. Import the character with its materials and morphs<\/h2>\n\n\n\n
Use the Reallusion Auto Setup import workflow with the exported FBX and matching JSON beside it. The companion JSON is discovered alongside the FBX. Keep Auto Setup enabled and choose the appropriate character and shader options for the installed release. The guide\u2019s reference UI uses HQ Shader. Avoid treating a plain FBX-only import as equivalent to the metadata-driven workflow. [7]<\/a><\/p>\n\n\n\n
\"Auto
Reallusion Auto Setup import dialog, with Auto Setup enabled and HQ Shader selected. Source: Reallusion documentation<\/a>. [7]<\/a><\/figcaption><\/figure>\n\n\n\n
Control Rig is not required for the facial-asset preparation described here. Leave it disabled unless the project also needs that body-authoring workflow. When Unreal\u2019s FBX import options appear, confirm the skeletal mesh and mesh-import settings, choose the appropriate skeleton context, and explicitly enable Import Morph Targets<\/strong> before selecting Import All<\/strong>. [7]<\/a> [8]<\/a><\/p>\n\n\n\n
\"Unreal
Unreal FBX import options. Enable Import Morph Targets before selecting Import All. Source: Reallusion documentation<\/a>. [7]<\/a><\/figcaption><\/figure>\n\n\n\n
Wait for asset processing and shader compilation to finish before judging materials. Then inspect the skeletal mesh, skeleton, physics asset, materials and material instances, textures, subsurface-scattering profiles, and any facial\/profile assets produced by the installed Auto Setup version. Save all imported packages. [7]<\/a><\/p>\n\n\n\n
\"Unreal
Unreal Content Browser displaying imported character asset families. Save all packages after import. Source: Reallusion documentation<\/a>. [7]<\/a><\/figcaption><\/figure>\n\n\n\n
Reopen the skeletal mesh and inspect its morph-target list. A populated list is a useful first check, but a large total count is not proof of compatibility. For instance, our tested character rig generated 249 morphs; other characters may have a different total count. What matters is whether the specific targets required by the integration are present.<\/p>\n\n\n\n
\"Unreal
Unreal skeletal mesh preview with facial morph targets. Verify that required facial targets are present and functional. Source: Reallusion documentation<\/a>. [7]<\/a><\/figcaption><\/figure>\n\n\n\n
7. Validate the facial-animation contract<\/h2>\n\n\n\n
Although runtime code is outside this article, the asset must satisfy the downstream facial mapping. In our direct-morph mapping pipeline, 52 ACE facial inputs map to 54 CC5 target writes<\/strong>: 50 inputs map to one target each, while two inputs (inner brow raise and cheek puff) drive bilateral left\/right pairs.<\/p>\n\n\n\n
Two different integration approaches:<\/strong> NVIDIA\u2019s public Unreal Renderer 0.1 guide describes a 52-frame ARKit animation, a Pose Asset, and an Animation Blueprint. Our pipeline uses project-owned C++ code that applies CC5 morph targets directly each frame. The 52-input \/ 54-write table below reflects this direct-morph mapping. Agree on the intended approach with the integration owner before preparing additional animation assets. Runtime implementation remains outside this article. [2]<\/a><\/p>\n\n\n\n
\n  \n    \n      \n        \n      \n        \n        \n        \n        \n        \n        \n        \n        
ACE Input & Index<\/th>\n        Required CC5 Target(s)<\/th>\n        Mapping Type<\/th>\n      <\/tr>\n    <\/thead>\n    
EyeBlinkLeft<\/code> \/ 0<\/td>\n        Eye_Blink_L<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n      
EyeBlinkRight<\/code> \/ 7<\/td>\n        Eye_Blink_R<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n      
JawOpen<\/code> \/ 17<\/td>\n        Jaw_Open<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n      
MouthSmileLeft<\/code> \/ 23<\/td>\n        Mouth_Smile_L<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n      
MouthSmileRight<\/code> \/ 24<\/td>\n        Mouth_Smile_R<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n      
BrowInnerUp<\/code> \/ 43<\/td>\n        Brow_Raise_Inner_L<\/code> + Brow_Raise_Inner_R<\/code><\/td>\n        Bilateral pair (1-to-2)<\/td>\n      <\/tr>\n      
CheekPuff<\/code> \/ 46<\/td>\n        Cheek_Puff_L<\/code> + Cheek_Puff_R<\/code><\/td>\n        Bilateral pair (1-to-2)<\/td>\n      <\/tr>\n      
TongueOut<\/code> \/ 51<\/td>\n        Tongue_Out<\/code><\/td>\n        1-to-1 direct<\/td>\n      <\/tr>\n    <\/tbody>\n  <\/table>\n<\/div>\n\n\n\n
The table is a review sample, not the complete mapping. Validate every entry in the complete 52-input mapping against the imported mesh. Preserve the documented spelling, capitalization, and input ordering in the handoff. In particular, eye look-in and look-out are relative to each eye: the reference maps EyeLookInLeft<\/code> to Eye_L_Look_R<\/code>, and EyeLookInRight<\/code> to Eye_R_Look_L<\/code>. Do not \u201ccorrect\u201d these names based on screen direction.<\/p>\n\n\n\n
For an asset-level visual check, double-click the imported Skeletal Mesh in Unreal Engine to open the Persona mesh editor, and locate the Morph Target Previewer<\/strong> tab (accessible via Window \u2192 Morph Target Previewer<\/strong> if hidden). Drag the weight sliders from 0.0<\/code> to 1.0<\/code> for representative morphs: left and right blinks, jaw opening, smiles, the inner-brow pair, cheek puff, and tongue movement. Confirm that the geometry deforms cleanly, the correct anatomical side responds without inversion, and the teeth, tongue, and tear ducts remain visually intact. Reset all sliders back to 0.0<\/code> to restore a neutral resting face before saving. This manual preview is a deformation check, not evidence of a working ACE or Tokkio stream. [8]<\/a><\/p>\n\n\n\n
Produce a target-by-target coverage report for the complete reference mapping, with no missing required targets. If a target is absent, first recheck the CC5 facial profile, expression export, and Unreal\u2019s Import Morph Targets setting. Do not silently rename or skip targets to make a report pass.<\/p>\n\n\n\n
8. Review the saved avatar, not just the import dialog<\/h2>\n\n\n\n
Inspect the neutral character in Unreal under useful lighting and a front-facing view. Check skin, eyes, eyelashes, clothing, and hair where present, and look for missing textures or unintended material assignments. Save the project assets and reopen them to confirm that the imported state persists. Keep a screenshot of the actual imported character and record its asset path.<\/p>\n\n\n\n
Distinguish errors that affect this character from unrelated project warnings. A missing texture referenced by a CC5 material or a missing required morph is blocking. A warning about an unused sample asset may be unrelated, but it should be classified rather than ignored indiscriminately.<\/p>\n\n\n\n
9. Common problems and where to fix them<\/h2>\n\n\n\n
\n  \n    \n      \n        \n      \n        \n        \n        \n        \n        \n        
Symptom<\/th>\n        Check and Repair Procedure<\/th>\n      <\/tr>\n    <\/thead>\n    
Export appears empty or 0 bytes<\/td>\n        Check export folder file sizes and inspect any sibling .fbm<\/code> directory. Re-export if the primary FBX or required material definitions are absent.<\/td>\n      <\/tr>\n      
Textures are missing after transfer<\/td>\n        Restore both the matching JSON and companion texture folder structure (CharacterName.fbm\/<\/code> + textures\/<\/code>). Verify all referenced paths resolve.<\/td>\n      <\/tr>\n      
Materials do not match intended setup<\/td>\n        Confirm compatible Auto Setup installation in Unreal Engine, ensure RLPlugin<\/code> is loaded, and use the JSON-assisted import dialog rather than a raw FBX import.<\/td>\n      <\/tr>\n      
Character renders but facial targets missing<\/td>\n        Recheck the CC5 CC4 Extended<\/strong> profile, verify facial-morph export was selected, and confirm Import Morph Targets<\/strong> is enabled in Unreal import options.<\/td>\n      <\/tr>\n      
Many morphs exist but coverage fails<\/td>\n        Compare actual morph target names in Persona against the complete 52-input mapping specification. Total count alone is not a valid pass criterion.<\/td>\n      <\/tr>\n      
Expressions affect the wrong side<\/td>\n        Review left\/right anatomical naming and eye-relative look directions (e.g. EyeLookInLeft<\/code> maps to Eye_L_Look_R<\/code>). Preview affected targets individually.<\/td>\n      <\/tr>\n    <\/tbody>\n  <\/table>\n<\/div>\n\n\n\n
10. Hand off a reproducible avatar package<\/h2>\n\n\n\n
Deliver the complete FBX\/JSON\/texture bundle together with the saved Unreal project assets and their dependencies. Include a short manifest of tool versions, plugin compatibility, facial profile, export settings, import settings, skeletal mesh path, and the full morph-coverage results. Add a neutral Unreal screenshot and list any remaining limitations explicitly.<\/p>\n\n\n\n
<\/p>\n\n\n\n
\n  
Upcoming in Part 2<\/div>\n  
Where the next article begins<\/div>\n  
\n    At this stage, we have defined and validated the avatar asset ready for consumption by downstream systems. The companion article will take this saved Unreal asset and implement the full runtime integration:\n  <\/p>\n  
\n    
• Connecting to NVIDIA ACE runtime services<\/div>\n    
• Custom C++ renderer actor implementation<\/div>\n    
• Direct 52-target morph application loop<\/div>\n    
• Camera microservice & Tokkio WebRTC streaming<\/div>\n  <\/div>\n<\/div>\n\n\n\n\n
\n  
\n    References & Official Documentation<\/span>\n    Accessed Sept 2026<\/span>\n  <\/div>\n  
\n    
\n      [1] NVIDIA.<\/span>\n      Tokkio 5.0: Customization Options →<\/a>\n      
Overview of digital human and avatar scene customization workflows in NVIDIA Tokkio.<\/div>\n    <\/div>\n    
\n      [2] NVIDIA.<\/span>\n      Unreal Renderer Microservice: Custom Avatar Workflow →<\/a>\n      
Specifications for driving 3D humanoid avatars based on 52 ARKit facial blendshapes in Unreal Engine.<\/div>\n    <\/div>\n    
\n      [3] Reallusion.<\/span>\n      Character Creator 5 Online Manual: Verifying Current Facial Profile →<\/a>\n      
Details on CC4 Standard, Extended, and HD facial profiles.<\/div>\n    <\/div>\n    
\n      [4] Reallusion.<\/span>\n      Character Creator 5 Online Manual: Exporting FBX →<\/a>\n      
Export commands, Unreal tool presets, mesh\/motion settings, and texture export configurations.<\/div>\n    <\/div>\n    
\n      [5] Reallusion.<\/span>\n      Auto Setup Online Manual: Exporting Characters for Unreal Engine →<\/a>\n      
Guidelines for external textures, disabling embedded textures, and generating the Auto Setup companion JSON file.<\/div>\n    <\/div>\n    
\n      [6] Reallusion.<\/span>\n      Character Creator & iClone Auto Setup for Unreal Engine Installation Guide →<\/a>\n      
Instructions for copying Content and Plugins directories into Unreal Engine projects.<\/div>\n    <\/div>\n    
\n      [7] Reallusion.<\/span>\n      Character Creator 5 Online Manual: Exporting Characters to Unreal Engine →<\/a>\n      
Auto Setup workflow in Unreal Engine, HQ Shader options, and inspecting imported assets.<\/div>\n    <\/div>\n    
\n      [8] Epic Games.<\/span>\n      Unreal Engine Documentation: FBX Morph Target Pipeline →<\/a>\n      
Technical overview of importing and previewing morph targets for Skeletal Meshes.<\/div>\n    <\/div>\n  <\/div>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"
A conversational avatar starts with a reliable character asset, not with a running service. Before connecting speech and facial animation, we need a complete character, correctly reconstructed materials, and facial morph targets that the renderer can actually drive. [1] [2] This first article explains how to prepare a Character Creator 5 (CC5) avatar for an Unreal Engine-based NVIDIA Tokkio workflow. We cover character preparation, FBX export, Reallusion Auto Setup import, and asset-level validation. The endpoint is a saved Unreal avatar and a documented handoff. A separate article by another contributor will cover ACE runtime integration, Tokkio configuration, packaging, deployment, and live-stream testing. Article Scope & Pipeline Boundary Scope of this … <\/p>\n
\u7d9a\u304d\u3092\u8aad\u3080 “Creating a Custom Avatar for NVIDIA Tokkio with Character Creator 5 and Unreal Engine”<\/span><\/a><\/p>\n","protected":false},"author":4,"featured_media":670,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-632","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tech-blog"],"_links":{"self":[{"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/posts\/632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/comments?post=632"}],"version-history":[{"count":17,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/posts\/632\/revisions"}],"predecessor-version":[{"id":689,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/posts\/632\/revisions\/689"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/media\/670"}],"wp:attachment":[{"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/media?parent=632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/categories?post=632"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dtc.teu.ac.jp\/ja\/wp-json\/wp\/v2\/tags?post=632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}