<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>28073</bug_id>
          
          <creation_ts>2015-02-22 10:28:52 +0000</creation_ts>
          <short_desc>[WebVTT] Rename &quot;line position&quot; to something more appropriate?</short_desc>
          <delta_ts>2017-07-10 23:41:41 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>TextTracks CG</product>
          <component>WebVTT</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>v1 widereview</status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Silvia Pfeiffer">silviapfeiffer1</reporter>
          <assigned_to name="This bug has no owner yet - up for the taking">dave.null</assigned_to>
          <cc>philipj</cc>
    
    <cc>silviapfeiffer1</cc>
    
    <cc>singer</cc>
    
    <cc>tai</cc>
          
          <qa_contact name="Web Media Text Tracks CG">public-texttracks</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>118074</commentid>
    <comment_count>0</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-02-22 10:28:52 +0000</bug_when>
    <thetext>The line position is actually more referring to the concept of a 
cue box than to the concept of a line. The first sentence states &quot;The 
line position defines the position of the cue box.&quot;. It would be could 
to have a term that describe this &quot;feature&quot; as an property of the cue 
box instead of lines. As the syntax maybe hard to change it could help 
if a synonymous word could be found.

As per feedback by Andreas Tai:
http://lists.w3.org/Archives/Public/public-texttracks/2015Feb/0005.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118075</commentid>
    <comment_count>1</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-02-22 10:29:54 +0000</bug_when>
    <thetext>Maybe &quot;cue position&quot;?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118076</commentid>
    <comment_count>2</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-02-22 10:30:34 +0000</bug_when>
    <thetext>Futher feedback by Andreas:
Furthermore a relationship to text 
position could be used in addition. While text position &quot;defines the 
positioning of the cue box in the direction defined by the writing 
direction&quot;, the line positon defines the position of the cue box 
orthogonal to the direction defined by the writing direction (?).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118199</commentid>
    <comment_count>3</comment_count>
    <who name="Philip Jägenstedt">philipj</who>
    <bug_when>2015-02-27 11:14:55 +0000</bug_when>
    <thetext>The names on VTTCue seem pretty sensible to me: line and position.

We could possibly call the concepts simply &quot;A line&quot; and &quot;A position&quot; too, but would that be any clearer? I guess &quot;A line position&quot; is a bit less wrong when it comes to percentage line positions.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118427</commentid>
    <comment_count>4</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-03-08 08:46:57 +0000</bug_when>
    <thetext>x and y dimensions don&apos;t work either because line and position depend on the writing direction.

We could start using &quot;offset&quot;.


How about improving the definition of &quot;text position&quot; and &quot;line position&quot;:

The text position defines the offset of the cue box in the direction defined by the writing direction.

&quot;position alignment&quot; then defines what that offset is anchored at wrt the cue box: start, middle or end of cue box in direction defined by the writing direction.

The line position defines the offset of the cue box orthogonal to the direction defined by the writing direction.

&quot;line alignment&quot; then defines what that offset is anchored at wrt the cue box: start, middle or end of cue box in direction orthogonal to the direction defined by the writing direction.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118787</commentid>
    <comment_count>5</comment_count>
    <who name="Andreas Tai">tai</who>
    <bug_when>2015-03-22 15:50:44 +0000</bug_when>
    <thetext>Makes sense to me.(In reply to Silvia Pfeiffer from comment #4)
&gt; x and y dimensions don&apos;t work either because line and position depend on the
&gt; writing direction.
&gt; 
&gt; We could start using &quot;offset&quot;.
&gt; 
&gt; 
&gt; How about improving the definition of &quot;text position&quot; and &quot;line position&quot;:
&gt; 
&gt; The text position defines the offset of the cue box in the direction defined
&gt; by the writing direction.
&gt; 
&gt; &quot;position alignment&quot; then defines what that offset is anchored at wrt the
&gt; cue box: start, middle or end of cue box in direction defined by the writing
&gt; direction.
&gt; 
&gt; The line position defines the offset of the cue box orthogonal to the
&gt; direction defined by the writing direction.
&gt; 
&gt; &quot;line alignment&quot; then defines what that offset is anchored at wrt the cue
&gt; box: start, middle or end of cue box in direction orthogonal to the
&gt; direction defined by the writing direction.

Makes sense to me.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118862</commentid>
    <comment_count>6</comment_count>
    <who name="Philip Jägenstedt">philipj</who>
    <bug_when>2015-03-23 09:55:47 +0000</bug_when>
    <thetext>In my own reading of the spec, the definitions (which could be improved) aren&apos;t the biggest source of confusion. Rather it&apos;s that the labels &quot;line position&quot; and &quot;text position&quot; are easy enough to confuse, in particular I often have to check if &quot;line position&quot; corresponds to VTTCue.line or VTTCue.position.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120780</commentid>
    <comment_count>7</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-06-07 08:40:59 +0000</bug_when>
    <thetext>(In reply to Philip Jägenstedt from comment #6)
&gt; In my own reading of the spec, the definitions (which could be improved)
&gt; aren&apos;t the biggest source of confusion. Rather it&apos;s that the labels &quot;line
&gt; position&quot; and &quot;text position&quot; are easy enough to confuse, in particular I
&gt; often have to check if &quot;line position&quot; corresponds to VTTCue.line or
&gt; VTTCue.position.

How about &quot;line offset&quot; and &quot;text offset&quot; then? That clarifies &quot;line position&quot;...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120781</commentid>
    <comment_count>8</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-06-07 08:58:17 +0000</bug_when>
    <thetext>(In reply to Silvia Pfeiffer from comment #7)
&gt; (In reply to Philip Jägenstedt from comment #6)
&gt; &gt; In my own reading of the spec, the definitions (which could be improved)
&gt; &gt; aren&apos;t the biggest source of confusion. Rather it&apos;s that the labels &quot;line
&gt; &gt; position&quot; and &quot;text position&quot; are easy enough to confuse, in particular I
&gt; &gt; often have to check if &quot;line position&quot; corresponds to VTTCue.line or
&gt; &gt; VTTCue.position.
&gt; 
&gt; How about &quot;line offset&quot; and &quot;text offset&quot; then? That clarifies &quot;line
&gt; position&quot;...

Actually, &quot;text position&quot; remains, of course. But &quot;line offset&quot; could work.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120783</commentid>
    <comment_count>9</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-06-07 09:26:54 +0000</bug_when>
    <thetext>I&apos;ve given it a go at https://github.com/w3c/webvtt/pull/194 . See what you think.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120820</commentid>
    <comment_count>10</comment_count>
    <who name="Philip Jägenstedt">philipj</who>
    <bug_when>2015-06-08 12:50:42 +0000</bug_when>
    <thetext>Merged.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120835</commentid>
    <comment_count>11</comment_count>
    <who name="Philip Jägenstedt">philipj</who>
    <bug_when>2015-06-09 10:05:20 +0000</bug_when>
    <thetext>Reopened due to https://github.com/w3c/webvtt/pull/194#issuecomment-110051562</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120955</commentid>
    <comment_count>12</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-06-12 21:57:24 +0000</bug_when>
    <thetext>Further improvements in https://github.com/w3c/webvtt/pull/197 .

IMO that change has made things much clearer. The word offset works really well because it explains clearly what the lines are offset from, i.e. which side of the video viewport.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>122520</commentid>
    <comment_count>13</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2015-08-09 06:29:03 +0000</bug_when>
    <thetext>Fix landed. Please open new bugs if you want to further tweak the language.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>127734</commentid>
    <comment_count>14</comment_count>
    <who name="David Singer">singer</who>
    <bug_when>2016-10-11 18:25:04 +0000</bug_when>
    <thetext>wording improved (line offset, etc.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>128682</commentid>
    <comment_count>15</comment_count>
    <who name="Andreas Tai">tai</who>
    <bug_when>2017-07-10 06:16:33 +0000</bug_when>
    <thetext>There has been a long discussion about this issue and the current status in the draft seems to reflect what can be achieved. Therefore, I accept that only part of the original proposal can be addressed. From my view the original PR (https://github.com/w3c/webvtt/pull/197) was a good pragmatic way to solve the problem. By disconnecting the terminology from the &quot;cue&quot; concept in PR 211 (https://github.com/w3c/webvtt/pull/211) the solution was reverted and the situation has not really improved. But because it seems not possible to come to another agreement, the dependencies between the different parts make terminology changes very difficult and also because this has been in the draft now for 2 years, it seems best to not start the discussion again.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>128686</commentid>
    <comment_count>16</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2017-07-10 07:10:55 +0000</bug_when>
    <thetext>Hi Andreas,
Thanks for going through all your bugs and accepting the decisions!

On this bug FYI: in the end we renamed &quot;line position&quot; to &quot;line offset&quot;, so we actually did accept the change.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>128698</commentid>
    <comment_count>17</comment_count>
    <who name="Andreas Tai">tai</who>
    <bug_when>2017-07-10 19:30:13 +0000</bug_when>
    <thetext>Hi Silvia,

The full comment in my email was as follows:

&quot; The line position is actually more referring to the concept of a
cue box than to the concept of a line. The first sentence states &quot;The
line position defines the position of the cue box.&quot;. It would be could
to have a term that describe this &quot;feature&quot; as an property of the cue
box instead of lines. As the syntax maybe hard to change it could help
if a synonymous word could be found. Furthermore a relationship to text
position could be used in addition. While text position &quot;defines the
positioning of the cue box in the direction defined by the writing
direction&quot;, the line positon defines the position of the cue box
orthogonal to the direction defined by the writing direction (?).&quot;


In the version I reviewed Feb 2015 the terms have been:

&quot;line position&quot; and &quot;text position&quot;

Now the terms are:

&quot;line&quot; and &quot;position&quot;


If you read just the first sentences of each concept it seems a bit circular:

line: The line defines positioning of the cue box.

position: The position defines the indent of the cue box in the direction defined by the writing direction.


&quot;line offset&quot; is used in the description once (&quot;The line offsets the cue box from the top...&quot;) but not as the name of the concept.

So overall, I am not sure if it is now better then before. 

(I use as reference the latest editor draft from 25th of June 2017)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>128705</commentid>
    <comment_count>18</comment_count>
    <who name="Silvia Pfeiffer">silviapfeiffer1</who>
    <bug_when>2017-07-10 23:41:41 +0000</bug_when>
    <thetext>A cue box is position by counting lines from the top and a percentage indent from the left. That&apos;s why they use of the word &quot;line&quot; makes sense - and the wording &quot;line offset&quot; has been used to describe it.

You seem to have more of a problem with the word &quot;position&quot; though - it would probably have been better to use &quot;indent&quot; for it, but that&apos;s likely a bit too late.

May it would be best to add a drawing that explains the concepts. The words we choose are always going to be ambiguous to some people.

Also, we could make just a simple change from:
&quot;line: The line defines positioning of the cue box.&quot;
to
&quot;line: The line defines the offset of the cue box.&quot;</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>