design - What is a "field"? "Field" vs "Field Value" -
There is a field in a passport: First name , and the value in that field is John .
I believe that the relationship is right to describe:
area first name :
- a name (First name).
- is a set of valid values (for example, regex [a-za-z.] {1,30}
- defined by a description (name is the full name of the person
and passport is a set of pairs (field: field value), such as:
- A field in the passport is "first name"
- The field is for the field "first name"
Right The path (perceptual / academic) is to say: "Passport Has the value of 'John' for the 'First Name' field.
In practical terms it means (Pseudo C #):
Structure passport {map < Lt; field, object & gt; fieldValues;} Struct field {string name; string description; bool isvid value (object value);}question: Which means? Any ideas?
It is very subjective and completely sensitive, and a silly Looks like the thing.
True or not, if I am discussing "passport" with colleagues, then I will throw some of them, if I say every time I say "the first name is' John '', and Told me to say "the first name of the passport field is 'John'. You will just come in the form of annoying.
Comments
Post a Comment