a 'mooh' point

clearly an IBM drone

Hyprocrisy 101

Software politics: Hypocracy 101

Course Title: Hypocrisy 101
Major: Software politics
Points earned: 10 ECTS
Prerequisites: none
Attending professor: Mr. Rob Weir, IBM

Course abstract:

When participating in the ever evolving landscape of software politics you need to master a variety of tools essential to ensure your success and accomplish your goals. This course will give you the ability to master any discussion involving software politics and to blow your opponents off the field

Course contents:

Deny, deny, deny: 5 lessons

Introduction: You will have to be able to deny anything at any place without flinching. Even if your opponent has fact-based arguments, simply dismiss these as either

  1. wrong
  2. from questionable resources
  3. or based on faulty assumptions

Remember, you choose what you want to comment on and you choose which arguments to take. 

You’re fucked either way: 4 lessons

Introduction: Never say anything wrong but also never say anything correct. If you are challenged on something you said, simply take any valid and solid resource and pick something out of context. If you are challenged on this, do one more iteration. Most documents can be interpreted either way, and only your imagination limits you in what you can do. 

Talk is silver but silence is gold: 6 lessons

Introduction: This is tricky to apply in a real-world, offline, discussion – but when applied to an asynchronous discussion on a blog, it works wonders. Whenever you feel challenged or cornered up in a discussion, simply leave for at few days. This will effectively dampen down the discussion and cool everything off. Then come back after a few days and pick up another, more easy, discussion as if nothing happened. If someone complains about you leaving the discussion – simply argue that you have a day-job to do to support wife and kids and bloggin’ is your secondary activity.'

Beat around the bush: 8 lessons

Introduction: Aside from not being concrete on anything, you will have to be able to master appearing to answer a question - when you are really not. A real-world example of a perfect example of this is from the blog of Brian Jones.

Brian Jones said:

You know what Rob, how about if you just take the questions and responses and post them on your own site? You are a member of the US national body and you have access to all of the materials. If it's no big deal, then post them for everyone.

Where to the attending Professor, Rob Weir, replyed:

I wouldn't want to give the Ecma password out, because the Ecma server is already slow as it is, and I wouldn't want to put more load on it.  Best to keep that for NB-access only.

Notice how this should be mastered? It appears that the question is answered ... when really, it's not.

 

With regards to which books and resources will be used throughout the course, feel free to contact the attending professor, preferably on his blog at http://www.robweir.com/blog/ .

Smile!

Yderligere svar fra ECMA

Svarene på de 750 unikke kommentarer fra de nationale råd er nu begyndt at komme i en lind strøm fra ECMA. Seneste udmelding fra ECMA er, at antallet af behandlede kommentarer nu er på 51% og tilgængelige fra det ISO/IEC-kontrollerede website. På seneste udmelding fra ECMA er tillige listet en del af de forslag, som de har valgt at følge. Det er en interessant liste, specielt da de faktisk var valgt at lave nogle ændringer, som jeg i hvert fald ikke havde regnet med de ville ændre. Listen er jo på deres website, men er tilføjet dette indlæg også:

  • Anvendelse af ISO-datoer
    Dette er faktisk én af de ting, som jeg er græsk/katolsk overfor, men det ser ud til, at man nu tillader persistering af datoer i regneark som både ISO-datoer og tal. Dermed gøres det på samme måde som i ODF, hvor man også har valget imellem tal eller datoer (hvilket i øvrigt har gået langt over hovedet på de fleste)
  • Internationalisering af ugedage
    Ét kritikpunkt af OOXML har været funktionen WEEKDAY() i regneark, der ikke tillader angivelse af en uge, der starter på andet end enten søndag eller mandag. Nu bliver det muligt at angive dagen, som ugen starter på
  • Sprog-angivelser
    Dette er så vidt jeg kan huske "ST_Lang-problematikken", hvor angivelse af datoer skulle gøre på to forskellige måder i stedet for at anvende en givet standard. Super!, at de nu bliver fixet
  • Side-kanter
    Angivelse af grafik til side-kanter var tidligere en lukket liste, dvs ikke ret fleksibelt. Nu bliver listen åben. Det er en god idé, da kontrol over dokumentets visuelle layout dermed gives tilbage til brugeren ... og ikke er forbeholdt formatet selv.
  • Formel-grammatik
    OOXML anvendte sin egen måde at beskrive formler, og ikke alene var det ikke en standardiseret måde at gøre det på, den var også mangelfuld. Nu ændres det til at anvende en såkaldt "udvidet BNF-notation". Den tekniske reference for dette er "ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF."

Jeg deltog i ECMA-mødet 7. december 2007 og ISO/IEC-plenary 8. december 2007 i Kyoto som repræsentant for Danmark og jeg og de andre repræsentanter for forskellige råd var bla. en del af diskussionerne i ECMA af flere af punkterne herover. Det var rart at høre og få vished for, at de rent faktisk bekymrede sig for vores holdninger til deres rettelser og de spurgte flere gange konkret, om vores respektive holdninger til den ene eller den anden løsning. Det var tydeligt for mig, hvor vigtig godkendelsen af DIS29500 er, og formatet ikke var helligt i dets nuværende form, men at der var en accept af formatet ville blive ændret som et resultat af processen.

Skulle du være interesseret i at se mine egne, personlige, rejseoplevelser, så kig forbi www.ringtilcamilla.dk Smile