UK Meetup April 2011

One of several microformats events.

details

When: 2011-04-12 from 19:30 to 23:00
Where: Greene Room,; The Cricketers Pub, Black Lion Street, Brighton, BN1 1ND, UK
What: The meetup is going part social and part workshop to brainstorm the input micorformat ideas. It’s open to everyone who's interested in microformats and semantic mark-up. If you are just want to join us for the social element that's cool the current plan is keep the brainstorming and discussion part to about an hour at the beginning of the evening.

As most people who said they who attended came from the Brighton area, we have organised the event in Brighton, but it would be really nice to see as many people as possible. Brighton is only 50 mins from London by train and 4 leave Brighton every hour until 23:37.

Web: http://lanyrd.com/2011/ufukmeet-april11/; http://plancast.com/p/4ttt; https://www.facebook.com/event.php?eid=100332266721736; http://maps.google.co.uk/maps?q=Black+Lion+Street,+Brighton+BN1+1ND&z=16; http://www.goldenliongroup.co.uk/bars-and-pubs/greene-room

Add this event to your diary or calendar program

attendees

Add yourself alphabetically sorted by family name if you plan on attending or attended.

regrets:

Nicholas Tollervey (can't make it all the way to Brighton... I'm north of London) :-(
...

photographs

...

notes

Please forgive that fact that I have not noted everyone’s name who took part. The main people contributing were; Aral Balkan, Glenn Jones, Jeremy Keith, Josh Emerson and Tantek Çelik. The session was broken down into 7 small discussions of specific problem areas. I have summarised below.

Using the class attribute and hierarchies

There was full agreement for the use of the className attribute instead of the form field name attribute. The name attribute can only take a single value and does not give enough flexibility to the author of a form as the name maybe dictated by the server side code.

For the current version of microformats, the use of hierarchical structures was agreed upon. The structures will be flattened in version 2 of microformats. In principle, form mark-up should follow the hierarchical structure of the microformat.

Examples used for the discussion:

<fieldset class="adr">
<input class="locality" name="city" type="text" />
<input class="country-name" name="country" type="text" />
</fieldset>

<div class="tel">
<input class="value" name="telephone-number" type="text" />
<select class="type" name="telephone-type" multiple="multiple">
<option value="none">Select phone type</option>
<option value="home">Home</option>
<option value="work">Work</option>
<option value="pref">Pref</option>
<option value="fax">Fax</option>
<option value="cell">Mobile</option>
<option value="cell">Pager</option>
</select>
</div>

Defining types in the className attribute

There is a problem adding ‘type’ information i.e. home, work and pref to inputs that take telephone numbers or email addresses. There are many use cases where the author wants to define a specific ‘type’ of a property, such as a mobile telephone number, to a single input. To accommodate this we somehow have to add the ‘type’ metadata as well as the property name.

In the current version of microformats, most people at the meeting were happy with the type information being added into the className attribute. For version2 of microformts, Tantek suggested adding a prefix of ‘l’ standing for label.

There was some discussion of using the HTML label element to define the microformat property. But it was dropped as we could not think of an authoring use case and it would add complexity.

Tanteks microformats v2 idea:

<input class="p-tel l-cell" name="mobile-number" type="text" />
<input class="p-tel l-fax" name="fax-number" type="text" />