//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4153 //
== Context ==
//Segments need to have stable, hash-based IDs that are robust to article update//
== Narrative ==
As a developer, I can calculate the segment ID based on the article title, segment content and adjacent segments.
== //Acceptance Criteria// ==
<i>Segments in different block structure, but with the same content and adjacent segments, have the same ID.</i>
<i>A document explains and justifies our segment ID choices</i>
== //Deliverables// ==
* //Enter link to actually done tangible deliverable(s)//
== //Open tasks// ==
{{
table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' < 'Done' ORDER BY 'Task Status', Owner, Name
}}
== //Completed tasks// ==
{{
table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Actual effort(hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' = 'Done' ORDER BY 'Task Status', Owner, Name
}}
== ==