Requesting Semantic Web IG review of Microdata

# Léonie Watson (4 days ago)

Hello Semantic Web IG,

The WebPlat WG would welcome your review of the Microdata specification [1], as we head towards CR.

To help make the review as easy as possible, we've documented all substantive changes in the Changes section of the spec [2].

We're pursuing an energetic timeline for publication, so we'd appreciate comments no later than 28th July (sooner if at all possible). As usual, please file any issues on Github [3].

Thank you, as always, for your help.

Léonie.

[1] www.w3.org/TR/2017/WD-microdata-20170626 [2] www.w3.org/TR/2017/WD-microdata-20170626/#changes [3] w3c/microdata

-- @LeonieWatson @tink@w3c.social @tink@toot.cafe tink.uk Carpe diem

Contact us to advertise here
# Léonie Watson (4 days ago)

With apologies, I forgot to mention that we'd also welcome mention of any features you believe may be "at risk" in the spec.

# Dan Brickley (4 days ago)

Technically we're out of charter so we can't(*) really act as an Interest Group within W3C process (we should be transitioning to a Community Group later this year). That said, the tweaked Microdata spec would certainly benefit from attentive review from members of semantic-web@w3.org... Do please take a look and share your thoughts.

Dan

(*) channeling my inner Dan Connolly here

# Gregg Kellogg (4 days ago)

This looks like a great update for Microdata that simplifies some previous aspects of the spec. As I note below, we should probably coordinate an update to the Microdata to RDF Note to ensure that they remain consistent.

Some typo’s:

In 4.2 The basic syntax:

The itemprop attribute on a descendent element of an item's identifies a property of that item.

Should be “element of an item”.

In 5.2

The itemid attribute must not be specified on elements that do not have both an itemscope attribute and anitemtype attribute specified.

Note that Microdata to RDF makes no such restriction, and includes a process for crafting URIs for @itemprop values based on the document location. Either this restriction should be removed (requiring only @itemscope), or we’ll need to remove that mechanism from a future Microdata to RDF update. In the absence of either @itemid or @itemtype, a Microdata to RDF processor will generate triples using blank node identifiers. Either such a processor should not ever generate triples without seeing an @itemtype, or @itemid should be allowed without @itemtype.

In any case, the Microdata to RDF spec does make use of the previous Microdata DOM API, and will need an update to provide a different mechanism for getting the values of an element or attribute. It may be useful to coordinate a Third Edition of Microdata to RDF with this publication so that they are consistent.

Gregg Kellogg gregg@greggkellogg.net

# chaals is Charles McCathie Nevile (18 hours ago)

On 26/06/17 17:08, Gregg Kellogg wrote:

This looks like a great update for Microdata that simplifies some previous aspects of the spec. As I note below, we should probably coordinate an update to the Microdata to RDF Note to ensure that they remain consistent.

Some typo’s:

In 4.2 The basic syntax:

The itemprop attribute on a descendent element of an item's identifies a property of that item. Should be “element of an item”.

Thanks. Fixed.

In 5.2

The itemid attribute must not be specified on elements that do not have both an itemscope attribute and anitemtype attribute specified. Note that Microdata to RDF makes no such restriction, and includes a process for crafting URIs for @itemprop values based on the document location. Either this restriction should be removed (requiring only @itemscope), or we’ll need to remove that mechanism from a future Microdata to RDF update. In the absence of either @itemid or @itemtype, a Microdata to RDF processor will generate triples using blank node identifiers. Either such a processor should not ever generate triples without seeing an @itemtype, or @itemid should be allowed without @itemtype.

Yes, thank you for raising this as issue #57 - w3c/microdata#57

Want more features?

Request early access to our private beta of readable email premium.