On Wed, 13 Feb 2013, Ed Summers wrote:
I am looking for some guidance about the use of multiple itemtypes in
microdata [1], specifically the phrase defined to use the same
vocabulary in:
The item types must all be types defined in applicable specifications
and must all be defined to
On Thu, 08 Dec 2011 22:04:41 +0100, Ian Hickson i...@hixie.ch wrote:
I changed the spec as you suggest.
Thanks!
--
Philip Jägenstedt
Core Developer
Opera Software
On Sat, 9 Jul 2011, Philip Jägenstedt wrote:
On Sat, 09 Jul 2011 01:19:02 +0200, Ian Hickson i...@hixie.ch wrote:
On Sat, 9 Jul 2011, Philip Jägenstedt wrote:
Step 11 is If current has an itemprop attribute specified, add it
to results. but should be If current has one or more
On Thu, 2011-07-07 at 22:33 +, Ian Hickson wrote:
The JSON algorithm now ends the crawl when it hits a loop, and replaces
the offending duplicate item with the string ERROR.
The RDF algorithm preserves the loops, since doing so is possible with
RDF. Turns out the algorithm almost did
On Tue, 12 Jul 2011 09:41:18 +0200, Henri Sivonen hsivo...@iki.fi wrote:
On Thu, 2011-07-07 at 22:33 +, Ian Hickson wrote:
The JSON algorithm now ends the crawl when it hits a loop, and replaces
the offending duplicate item with the string ERROR.
The RDF algorithm preserves the loops,
On Tue, 12 Jul 2011, Henri Sivonen wrote:
On Thu, 2011-07-07 at 22:33 +, Ian Hickson wrote:
The JSON algorithm now ends the crawl when it hits a loop, and
replaces the offending duplicate item with the string ERROR.
The RDF algorithm preserves the loops, since doing so is possible
On Sat, 09 Jul 2011 01:19:02 +0200, Ian Hickson i...@hixie.ch wrote:
On Sat, 9 Jul 2011, Philip Jägenstedt wrote:
Step 11 is If current has an itemprop attribute specified, add it to
results. but should be If current has one or more property names, add
it to results. Property names are
On Fri, 08 Jul 2011 00:33:14 +0200, Ian Hickson i...@hixie.ch wrote:
On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote:
I've been looking into Microdata specification and it struck me, that
crawling algorithm is so complex, when it comes to expressing simple
ideas. I think that foremost the
On Fri, 08 Jul 2011 21:31:49 +0200, Ian Hickson i...@hixie.ch wrote:
On Fri, 8 Jul 2011, Philip Jägenstedt wrote:
On Fri, 08 Jul 2011 00:33:14 +0200, Ian Hickson i...@hixie.ch wrote:
On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote:
I've been looking into Microdata specification and it struck
On Wed, 8 Jun 2011, Tomasz Jamroszczak wrote:
I've been looking into Microdata specification and it struck me, that
crawling algorithm is so complex, when it comes to expressing simple
ideas. I think that foremost the algorithm should be described in the
specification with explanation
Hello,
Reading
http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#microdata
Section '5.2.3 Names: the itemprop attribute' states something
important about Microdata's data model,
Within an item, the properties are unordered with respect to each
other, except for properties
Hi everybody, I originally intended to send this message to the
implementors list but seeing in the archives that there hasn't been
much activity there for the last couple of months, I'm sending this to
the general list. Well, basically I just wanted to announce that I've
just released (
On Mon, 18 Jan 2010 16:24:46 +0100, Jeremy Keith jer...@adactio.com
wrote:
Hixie wrote:
Finally on vCard, the final part of the extraction algorithm goes to
great trouble to guess what is the family name and what is the given
name. This guess will be broken for transliterated east Asian
On Mon, 18 Jan 2010 13:58:16 +0100, Ian Hickson i...@hixie.ch wrote:
I'd like at some point to introduce some sort of semantic textContent
that handles br, pre, bdo, dir=, img alt, del, space-
collapsing, and newline elimination, but there hasn't been much
enthusiasm
around the idea, and
On Mon, 18 Jan 2010, Aryeh Gregor wrote:
On Mon, Jan 18, 2010 at 7:58 AM, Ian Hickson i...@hixie.ch wrote:
I've made it redirect to the spec.
Could you say that the URL *should* provide human-readable information
about the vocabulary? We all know the problems with having
On Thu, 12 Nov 2009, Philip Jägenstedt wrote:
I've been playing with the microdata DOM APIs again, continuing the
JavaScript experimental implementation
http://gitorious.org/microdatajs. It's not small or elegant, but at
least some spec issues have come up in the process.
What is the
Hixie wrote:
Finally on vCard, the final part of the extraction algorithm goes to
great trouble to guess what is the family name and what is the given
name. This guess will be broken for transliterated east Asian names
(CJKV that I know of, maybe others too). Just saying. Also, why is it
On Mon, Jan 18, 2010 at 7:58 AM, Ian Hickson i...@hixie.ch wrote:
I've made it redirect to the spec.
Could you say that the URL *should* provide human-readable information
about the vocabulary? We all know the problems with having
centrally-stored machine-readable data about your specs, but
Aryeh Gregor wrote:
On Mon, Jan 18, 2010 at 7:58 AM, Ian Hickson i...@hixie.ch wrote:
I've made it redirect to the spec.
Could you say that the URL *should* provide human-readable information
about the vocabulary? We all know the problems with having
centrally-stored machine-readable data
On Wed, 14 Oct 2009 13:53:46 +0200, Ian Hickson i...@hixie.ch wrote:
On Fri, 21 Aug 2009, Philip Jägenstedt wrote:
Shouldn't namedItem [6] be namedItems? Code like .namedItem().item(0)
would be quite confusing.
[6]
On Fri, 21 Aug 2009, Philip Jägenstedt wrote:
The spec says that properties can also themselves be groups of
name-value pairs, but this isn't exposed in a very convenient way in
the DOM API. The 'properties' DOM-property is a HTMLPropertyCollection
of all associated elements. Discovering
21 matches
Mail list logo
