Re: Call for Consensus to request transition of DAPT to Candidate Recommendation

   hi,

On 2024/10/21 22:19, Nigel Megitt wrote:
> Hi Atsushi,
> 
> You can query GitHub using something like https://github.com/w3c/dapt/pulls?q=is%3Apr+merged%3A%3E2023-04-25+-label%3Aeditorial+-label%3Aci to get the PRs merged since FPWD that are not marked as editorial or as CI - I just went through them all checking that the labels are correct.

   Ah, yes. I've actually wanted to go through substantive issues/PR list..
Also as I wrote, to create description for HR...

   Several questions on current substantive changes list:
https://www.w3.org/TR/dapt/substantive-changes-summary.txt


1. Write a Privacy and Security section (#166)

   It seems added section is informative. I'm personally fine to be listed
as important changes, but might not be substantive?

2. at-risk issues

   'PR-must-have' at the end of each line might be better removed?
   I believe we will have PRs for changes against referred issues in
at-risk issue, and all merged. But it seems cleaner with listing
actual changes (or its issues), since we have list of at-risk issues
in the spec itself.
# If we just list potential features to be added and aiming to mark
part of these as at-risk, listing in changes seems mis-leading?




   For record, to be used during CRS transition, following substantive
changes are made after horizontal review requests (2023-07-18), but no
new feature is added.
   Most of substantive changes are to refactor defined daptm: objects
and properties for ease of use and extensibility.


* Write a Privacy and Security section (#166)

   Added informative Privacy and Security section. (PR #168)

* Identify the original language on top of the current language #148  (introduce daptm:langSrc) (#148, #173)

   daptm:langSrc was changed from ENUM origina/translated into having original
language code for better and extended handling about status of original or
translated. (PR #179)

* Script Event Description should be an object (#174)

   Script Event Descript was defined as a property of Script Event, this change
turns property into a separate object. (PR 181)

* Remove Character Style (#124, #162)

   Character Style object removed. (PR #185)

* Create inline Registry Tables and Registry Definition (#195)

   Added registry table as inline. (PR #196)

* Discuss extensibility and backwards compatible behavior; add section about mapping TTML to the DAPT data model (#110, #214, #234)

   Clarifies the TTML document type, and provides more clarity about both the TTML
representation and the mapping back from TTML into the DAPT data model.
   Optional #scriptEventMapping feature added.  (PR #216)

* Replace workflowType with represents; support within workflowType for generic script origination (#169, #194)

   daptm:workflowType (ENUM dubbing and audioDescription) was replaced with
daptm:represents which can have items from content-descriptor registry
table.
   Also content-descriptor inline registry table added. (PR #217)

* Add nested div feature and mark as permitted, at risk (#237)

   Added #scriptEventGrouping TT feature as permitted.
   This feature is marked as at-risk (Issue #239).
   (PR #238)

* Required metadata field for earliest SMPTE time code to allow conversion between DAPT and ESEF (#232)

   Added Timecode related metadata. Also refer urn:ebu:tt:metadata namespace. (PR #240)

* Remove Script Event Type, use Represents instead (#227)

   Remove Script Event Type, and make Represents an optional property of Script
Event.
   Merge registry table entries for eventType into <content-descriptor>.
   Add permitted #represents-div feature. (PR #241)

* Defining restrictions per Script Type (#75)

   Added three constraints, Pre-Recording Scripts SHOULD NOT contain Audio objects,
and As-Recorded Scripts SHOULD NOT contain Synthesized Audio objects and SHOULD
contain Audio Recording objects