the semantic analizer will get angry, because ELL0 is not on the lexicon table, he don't understand ELL0 and can't add it to the lexicon table because to do so, must be on the left part of a LET sentence. Poor dumb semantic analizer don't know ELL0 was the user tryiing to write a number, it look to him like a symbol for where search fails.
<start-time>2015-02-26T08:00:00</start-time> <end-time>2015-02-26T09:00:00</end-time></Meeting>
(a) The statement that "the meeting's start time must be before the end time" is a statement about semantics.
Too high level for a poor semantic analizer. Maybe he can detect it and generate a warning.
(b) The statement that "the keywords are case insensitive" is a statement about semantics.
Too low level for a semantic analizer, this is a parser job
(c) The statement that "the meeting's start time must be before the end
time" is a statement about a data relationship (a co-constraint), it has
nothing to do with the semantics of the meeting.
Too high level for a poor semantic analizer. Maybe he can detect it and generate a warning.
(d) The statement that "the keywords are case insensitive" is a
statement about how a lexer should tokenize the DOT language, it has
nothing to do with the semantics of the keywords.
Seems correct to me
(e) We spend too much time worrying about whether something should or shouldn't be labeled "semantics".
The first time I had to work with SOAP I got the impression somebody had quadruple complicators gloves here. I would submit the whole of SOAP to a site like theDailywtf.com and see if they post it.
(f) We should stop using the word "semantics" since nobody can agree to what it is.
No?, almost everybody uses the word "hacker" wrong, I think is not reason enough to continue using it properly. Hollywood be damned.
