[reporting] 更新（編集上

Use the more common index.bs naming, which also fixes the spec-prod output file.
w3c/reporting@f2bea95

Update index.src.html
w3c/reporting@ad68ae3

Author: triple-underscore

reporting1-ja.html

@@ -120,7 +120,7 @@
 ●●options
 
 spec_title:Reporting API
-spec_date:2024-08-13
+spec_date:2025-05-15
 trans_update:2025-05-16
 source_checked:201019
 page_state_key:WEBAPPSEC
@@ -129,7 +129,7 @@
 spec_status:ED
 ref_id_prefix:biblio-
 ref_id_lowercase:true
-copyright:2024,permissive
+copyright:2025,permissive
 trans_1st_pub:2016-06-06
 
 
@@ -499,6 +499,10 @@
 
 報告を生成する:#generate-a-report
 報告を生成して~queueする:#generate-and-queue-a-report
+	%文脈:#generate-and-queue-a-report-context
+	%種別:#generate-and-queue-a-report-type
+	%行先:#generate-and-queue-a-report-destination
+	%~data:#generate-and-queue-a-report-data
 
 報告先:#endpoint
 eP.名前:#dom-endpoint-name
@@ -676,12 +680,12 @@
     Anne van Kesteren. ＜DOM Standard＞. Living Standard. URL: https://dom.spec.whatwg.org/
 [FETCH]
     Anne van Kesteren. ＜Fetch Standard＞. Living Standard. URL: https://fetch.spec.whatwg.org/
-[FileAPI]
-    Marijn Kruisselbrink. ＜File API＞. URL: https://w3c.github.io/FileAPI/
 [HTML]
     Anne van Kesteren; et al. ＜HTML Standard＞. Living Standard. URL: https://html.spec.whatwg.org/multipage/
 [INFRA]
     Anne van Kesteren; Domenic Denicola. ＜Infra Standard＞. Living Standard. URL: https://infra.spec.whatwg.org/
+[RDF12-CONCEPTS]
+    Olaf Hartig; et al. ＜RDF 1.2 Concepts and Abstract Syntax＞. URL: https://w3c.github.io/rdf-concepts/spec/
 [RFC3864]
     G. Klyne; M. Nottingham; J. Mogul. ＜Registration Procedures for Message Header Fields＞. September 2004. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc3864
 [RFC5234]
@@ -1734,7 +1738,7 @@ <h4 title="Generate report of type with data">3.4.1. ある種別の報告を %~
 ◎終
 に対し：
 ◎
-When the user agent is to generate and queue a report for a Document or WorkerGlobalScope object (context), given a string (type), another string (destination), and a serializable object (data), it must run the following steps:
+When the user agent is to generate and queue a report for a Document or WorkerGlobalScope object (context), given a string (type), a string (destination), and a serializable object (data), it must run the following steps:
 </p>
 <ol>
 	<li>
@@ -2213,7 +2217,7 @@ <h2 title="Reporting Observers">4. 報告用~観測器</h2>
 </dl>
 
 <p class="note">注記：
-報告用~観測器が関連するのは、
+`報告用~観測器$が関連するのは、
 ~JS~engineを備える~UA用に限られる。
 ◎
 Note: Reporting observers are only relevant for user agents with JavaScript engines.
@@ -2863,9 +2867,7 @@ <h3 title="Generate Test Report">7.1. ~test報告を生成する</h3>
 <ol>
 	<li>
 ~IF［
-%parameters は~JSON
-`Object＠~FILEAPI#blob-url-entry-object$【 `Object^jT ？】
-でない
+%parameters は~JSON `Object^jT でない【！https://w3c.github.io/rdf-concepts/spec/#dfn-object】
 ］
 ⇒
 ~RET `~WebDriver~error$( `無効な引数$i )
@@ -3023,9 +3025,9 @@ <h3 title="Network Leakage">9.1. ~network漏洩e</h3>
 軽減策を考慮する。
 例えば、
 別の~networkへ変更されたときは，報告を落とすこともできるような。
-`w3c/BackgroundSync 課題 #107＠https://github.com/WICG/background-sync/issues/107$
+[`WICG/background-sync 課題 #107＠https://github.com/WICG/background-sync/issues/107$]
 ◎
-Consider mitigations. For example, we could drop reports if we change from one network to another. [Issue #w3c/BackgroundSync#107]
+Consider mitigations. For example, we could drop reports if we change from one network to another. [WICG/background-sync Issue #107]
 </p>
 
 		</section>