Profile cover photo
Profile photo
Jeni Tennison
1,935 followers
1,935 followers
About
Posts

Post has attachment
Bill recreates The Warlock of Firetop Mountain in Lego Heroica form.
PhotoPhotoPhotoPhotoPhoto
View album

Post has shared content
One of the Task Forces announced here is on data embedded in HTML. If you have an interest in helping users navigate the microdata/RDFa/microformats minefield, please join the mailing list. We'll only be running for 2-3 months.

Post has attachment
+Ian Hickson, could you point me to the use case(s) that led you to introducing itemref in microdata? I've looked through the list of use cases at http://lists.w3.org/Archives/Public/public-html/2009May/0207.html but none of them mention itemref (perhaps it was called something else at that point and I missed it). Many thanks in advance.

Post has attachment
Posted a series of three posts about the mismatches between microdata and RDFa and what might be done to bring them closer together. If you prefer to comment on Google+ then please do so on this post.

Post has attachment
+Philip Jägenstedt Can you take a look at: https://gist.github.com/1150357 ?

I'm using your Live Microdata converter. I was expecting the itemid attribute on the <head> element to be resolved relative to the base URL set by the <base> element, but instead it's using the normal base URL from your converter. Have I misinterpreted the way in which the itemid will be resolved, or is this a bug?

Thanks :)

Post has attachment
+Ian Hickson In microdata, the restrictions on the terms in the itemprop attribute (at http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#names:-the-itemprop-attribute) say that properties on items with types must be defined property names, but don't say anything similar for properties on nested items (that don't themselves have a type). Does that mean that the property names on the nested items shouldn't/mustn't be associated with the type of the outer item or is it OK to do so?


I'm guessing it's OK, as you basically did this in the (now-defunct) microdata-to-RDF mapping. If it is, perhaps properties on items that are nested within a typed item should have the same restriction to be defined property names as those directly on typed items?
An example is in the vCard example at http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#examples-1 where the n and adr items have nested properties that are part of the vCard vocabulary.

Post has attachment
More confirmation that whatever you do, you're going to screw up your kids.

Post has attachment
Blogged an alternative approach for convergence of microdata and RDFa, for discussion. Comment there or here as you prefer.

Post has shared content
Absolutely agree with this. I have people in circles based on what I think their interests are, but it seems ridiculous to restrict visibility based on my assumptions.
G+ circles aren't a substitution for tags/hashtags, because circles are restrictive, while hashtags are descriptive. For example, if I create a Flying circle and post my aviation-related updates only to it, no one else can ready them; if I make the flying posts public, then everyone who has me in a circle will see the posts whether they're interested in aviation or not.

Perhaps G+ could introduce channels as well as circles. Channels describe a theme/topic ("Flying", "Gardening", "Politics", "Knitting"), while circles are for authorization. For example, if I did something stupid and got in trouble with Transport Canada, I might post something about it to my Flying channel (descriptive) but allow only my Family and Friends circles to read it (restrictive).

Post has attachment
+Ian Hickson What's the reason in microdata [1] for the restriction "Specifications that introduce defined property names that are not absolute URLs must ensure all such property names contain no U+002E FULL STOP characters (.), no U+003A COLON characters (:), and no space characters." ?

Space characters is obvious, but why full stops and colons?

Thanks.

[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#names:-the-itemprop-attribute
Wait while more posts are being loaded