Top Judge Apologizes for Judicial Appointment Delay, Promises Official Statement Next Week
Translated from Korean and summarized by DistantNews. Read the original for the full story.
At a glance
- Supreme Court Chief Justice Jo Hee-dae apologized for the public concern caused by the presidential office's rejection of a judicial nominee.
- Jo stated that the Supreme Court is reviewing the situation and will release an official statement next week.
- The presidential office requested a re-nomination, citing procedural issues with the initial nomination of Son Bong-ki.
Supreme Court Chief Justice Jo Hee-dae has apologized to the public for the concern generated by the presidential office's rejection of a nominee for Supreme Court Justice. He promised to issue an official statement on the matter next week.
Speaking to reporters as he left work, Jo indicated that the Supreme Court is currently reviewing the details of the situation. When asked about plans to re-form the nomination committee, he stated that a clearer direction would be provided next week after internal discussions are finalized.
The presidential office had previously announced its decision not to submit the appointment confirmation bill for Son Bong-ki, who was nominated to succeed former Justice Roh Tae-ak. The office cited procedural concerns with the nomination, which was made via written submission, suggesting it did not fully meet the requirements of the Court Organization Act.
Presidential spokesperson Kang Yu-jeong emphasized the importance of respecting the recommendations of the Supreme Court Justice Recommendation Committee. The office urged the Chief Justice to proceed with the re-nomination process swiftly to prevent further delays in filling the vacant Supreme Court seat and to ensure the public's right to trial is not compromised.
Originally published by Dong-A Ilbo in Korean. Translated, summarized, and contextualized automatically by DistantNews, with a note on how the source frames the story. Not individually reviewed before publishing. How this works.