Re: [Slim] New wording for the use of the asterisk in draft-ietf-slim-negotiating-human-language

[Gunnar Hellström <[e-mail]>]

Den 2017-06-06 kl. 03:00, skrev Randall Gellens:
> At 10:21 PM +0200 6/5/17, Gunnar Hellström wrote:
>
>>  Den 2017-06-04 kl. 23:51, skrev Randall Gellens:
>>>  Hi Gunnar,
>>>
>>>  What I'd suggest is that we include an informational reference to 
>>> the draft, although that requires that at least an initial version 
>>> of the draft be published pretty quickly. So, my suggestion is that 
>>> you publish at least a skeleton draft right away (which you can 
>>> revise and extend quickly), and we add text along the lines of the 
>>> following, perhaps after the second paragraph of Section 5.3:
>>>
>>>     Note that separate work [draft-xxx] proposes to use the asterisk 
>>> (or
>>>     lack thereof) to convey information between endpoints.
>>>
>>>  This alerts implementers to the other draft.
>>  This might be a possible way ahead, if others also think it is 
>> feasible.
>
> Gunnar, please upload at least a skeleton version of the draft right 
> away, and let me know the title.  If you need help with that, I can 
> create one.
>
>>  The wording and placement of the text requires more tuning. E.g. it 
>> should not say "proposes", but rather "specifies".
>
> I was reluctant to say "specifies" until we have a more solid draft 
> (we don't yet have anything). How about if the text says "uses" rather 
> than "proposes to use"?  I think that covers it.
Yes, the drafts for the two functionality extensions are uploaded.

I would think that it would be more logical to insert the note about the 
added meaning of the asterisk in section 5.2, because 5.3 is for the 
current interpretation case only.

I propose a change to this current text in 5.2

------old text----


    In an offer, each value MAY have an asterisk appended as the final
    value.  An asterisk appended to either value in an offer indicates a
    request by the caller to the callee to not fail the call if there is
    no language in common.  See Section 5.3 for more information and
    discussion.

-----new text could be----

    In an offer or answer, each value MAY have an asterisk appended as the final
    token.  An asterisk appended to either value in an offer indicates a
    request by the caller to the callee to not fail the call if there is
    no language in common.  See Section 5.3 for more information and
    discussion.

    Note that separate work [draft-hellstrom-slim-modalitypref] extends the use of the
    asterisk with a media level indication.


---end of change-----------------

  



The other draft, about simultaneous modality may also need to be announced.
I suggest this change:

----old text in 5.2------

  
  BCP 47 describes mechanisms for
    matching language tags.  Note that [RFC5646] Section 4.1 advises to
    "tag content wisely" and not include unnecessary subtags.

  ----new text-----

  
  BCP 47 describes mechanisms for
    matching language tags.  Note that [RFC5646] Section 4.1 advises to
    "tag content wisely" and not include unnecessary subtags.

  
  Note also that separate work in [draft-hellstrom-slim-simultaneous-modality] uses a
  notation with a subtag for extended functionality. It is therefore of importance to
  use the mechanisms from BCP 47 for matching languages correctly.

----end of change-----
  

This all builds on that we can at least get WG draft status soon on the 
new drafts.

Gunnar
>
>

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
[e-mail]
[phone]