[ibis-editorial] Re: Typ value confusion...

  • From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
  • To: "ibis-editorial@xxxxxxxxxxxxx" <ibis-editorial@xxxxxxxxxxxxx>
  • Date: Sat, 3 Mar 2012 00:37:10 +0000

Bob,

"All cases 4 below are correct for List. "
How could they be?

Arpad
===============================

From: ibis-editorial-bounce@xxxxxxxxxxxxx 
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Friday, March 02, 2012 6:09 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: Typ value confusion...

Michael:

Good questions and many more should follow.

So, I would hold off starting to write explanations until we
have the organization nailed down.  Your general question also
applies to Corner, Range, Increment, Step and maybe something
else.  There are different rules and limits for Default values for each
case as to what a member of the class may mean and the limits.

All cases 4 below are correct for List.  For List repeats are required,
so a new "unlisted value" (Default E) would be flagged as an error.

Bob

From: 
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
 On Behalf Of Muranyi, Arpad
Sent: Friday, March 02, 2012 4:01 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] Re: Typ value confusion...

We can discuss that in the next editorial meeting.

Thanks,

Arpad
====================================================

From: 
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
 On Behalf Of Mirmak, Michael
Sent: Friday, March 02, 2012 5:48 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] Re: Typ value confusion...

Arpad,

Thanks.  If this is the consensus answer, we'll need to add some explanatory 
text plus edit out the <typ value> mention in the List syntax definition.  The 
new text would state exactly what you did: if Default is not present for a 
List, the first item in the list is assumed the Default value.


-          MM

From: 
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
 On Behalf Of Muranyi, Arpad
Sent: Friday, March 02, 2012 3:45 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] Re: Typ value confusion...

Mike,

The list is just a list of A, B, C, D, where "A" is the first
item in the list.

If Default is not defined, the first item will be used from the
list.  I don't know why the name "typ" was given to this first
item, but that is just a bad naming convention (probably coming
from the Range, or Increment types).

Does this answer your question?

Thanks,

Arpad
================================================================

From: 
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
 On Behalf Of Mirmak, Michael
Sent: Friday, March 02, 2012 5:37 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] Typ value confusion...

(this may require cross-posting to ibis-macro)

In reviewing Section 10A in the draft 5.1 document, I have a question about the 
"typ value" of a Model Specific parameter: for List, etc., must one list a 
*duplicate* value for the typ value?  In other words, are repeats required?

This should not be affected by the presence of "Default" (though "Default" 
makes it confusing).

Here's an example in four variations.  Which is correct?  My own vote is for 
(1) and (4) being correct.  However, we only say that the Default value has to 
be a member of the list, *not* that the typ value has to be a member of the 
list!  ("Also, if Default is specified, <value> must be a member of the set of 
allowed values of the parameter. If Default is not specified, the default value 
of the parameters will be the <typ> value.")

1)

    (Informative_String (Usage In)(List B A B C D)(Type String)(Default B)
      (Description "This is an example with a repeated item, because the first 
in the list should be the Typ Value"))

2)

    (Informative_String (Usage In)(List A B C D)(Type String)(Default B)
      (Description "This is an example without a repeated item, because the 
first in the list shouldn't have to be the Typ Value, as I have a Default 
declared; but I risk declaring a typ that isn't actually in my list, if the typ 
is A and the list consists only of B, C and D"))

3)

    (Informative_String (Usage In)(List A B C D)(Type String)
      (Description "This is an example without a repeated item, and without a 
Default, I risk declaring a typ that isn't actually in my list, if the typ is A 
and the list consists only of B, C and D"))

4)

    (Informative_String (Usage In)(List B A B C D)(Type String)
      (Description "This is an example with a repeated item, and without a 
Default; this technically matches the spirit and letter of the 5.1 law"))


-          MM

Other related posts: