- From: Robert Warren <warren@glengarryag.com>
- Date: Mon, 4 Aug 2025 13:41:52 -0400
- To: SDW WG <public-sdw-wg@w3.org>, Grellet Sylvain <S.Grellet@brgm.fr>, Kathi Schleidt <Kathi@DataCove.eu>, Robert Warren <warren@glengarryag.com>, Rob Atkinson <robatkinson101@gmail.com>, Maxime Lefrançois <maxime.lefrancois@emse.fr>, Krzysztof Janowicz <krzysztof.janowicz@univie.ac.at>, Luis de Sousa <luis.moreira.de.sousa@tecnico.ulisboa.pt>, Simon Cox <dr.shorthair@pm.me>, Bert Bos <bert@w3.org>
Following the July 30th meeting, I've received emails that I will politely characterize as "encouraging antagonism". Everyone reading this is a grownup with an expensive education. If you have concerns with someone's behaviour please bring it up with them directly. This axe grinding and gossip over side-channels isn't helping. This is a standards meeting. Not a soap opera or a revolutionary committee. *chill* Last week I asked a question that should had been a Yes or No answer. The discussion that followed mixed fact, opinion, process, what the spec said, says and what it was supposed to say. After 27m of discussion my take away is that not everyone is on the same page. I disagree with Maxime. I also disagree with many other similarly highly qualified people. Many of those also disagree with me too. It's not personal, it's work. My comment about his students was also genuine: the readers of this document are in a similar situation to us: needs are infinite, resources are limited, deadlines abound and spouses demand dinner at a predictable time. But, our readers don't have our depth of background. They want a simple, easy to understand solution that fixes their problem without creating new ones. I'm not being derogatory when I say that these are people who will ask about the "jason LD" format, why string language tags aren't the same everywhere "in the file" and what "non-normative" means. Assuming I'm the dumb kid in the classroom, not quite at the very right of the curve, consider what it means about the rest of the audience. A good plan, poorly communicated, tends to become a bad expensive plan. Professional ethics, if not common sense, dictates that I can't communicate or endorse things that I don't fully understand. The observation collections were a good idea, but OperatingConditionKind appears to over-engineer (maybe?) a non-problem (I think?) with operating conditions: the average sensor has 1 or 2 (fine, or 3) conditions (I know). So what problem are we solving with this? I've put my thoughts in what was a provisional PR. Git is as much a negotiation tool as it is a decision recording tool. I think these are reasonable concerns; I'll look forward to the discussion Wednesday. Please do not send me gripes about each other; Kissinger would say that you only prove that the work doesn't matter and I don't have the time for it. -rhw
Received on Monday, 4 August 2025 17:42:09 UTC