Have a question for the community - how would you mark up a food drive? It's an event, but not really any type of event that is listed at https://schema.org/Event and I can see that there is a https://schema.org/DonateAction but that mostly covers who donations are being provided to and I am not clear on how I could incorporate that into the event markup.

Specifically looking to call out a charitable food drive event where I can explicitly call out that the items being collected are non-perishable food items.

So far I've got a pretty generic JSON-LD event listing with the following properties:
Name,
Description,
Location,
Start Date,
End Date

Has there been any chatter or thoughts around adding a CharitableEvent type to the current hierarchy?

Any thoughts on how I might be able to use an extension to fill in some of the blanks?

Thanks in advance!

Curious if there are plans to move this community to another platform with the news that this service is being sunsetted?

Post has attachment
Save the schema.org/startDate, eh? *

As I believe some members of this Community might have a passing familiarity with schema.org, you might be interested in hearing me talk about it if you happen to find yourself in London on Nov. 7.

The entire program is fabulous (including the two sessions on other tracks taking place during my presentation that I'll have to miss):
http://connected-data.london/

Also, I'm in on the 6th, so if anyone has any interest in getting together prior to the conference lemme know!

* I am Canadian

Post has attachment
"It is probably clear by now that Dataset Search is only as good as the metadata that exists on the Web pages for datasets"

A new post today on the Google AI Blog provides Google's deepest dive yet into their recently-released Dataset Search.

A few things to note for the semantically-minded.

Connecting replicas of datasets

The post describes how Google attempts to determine when two datasets are replicas of one another.

Mechanisms include use of schema.org/sameAs, the same canonical dataset source, two datasets pointing to the same canonical page, or two datasets with an identical Digital Object Identifier (DOI).

Note that hyperlinking "to new, recommended DOI resolver" is queued up for schema.org 3.4 (http://bit.ly/2xI2GKp).

Reconciling to the Google Knowledge Graph

I found this section, where the post talks about Google trying "to reconcile information mentioned in the metadata fields with the items in the Knowledge Graph" particularly interesting.

TL;DR (for me at least) > When Google encounters an entity it tries to reconcile it with the Knowledge Graph.

Ranking of Dataset results

TL;DR here is that, for the time being, Google is relying on "on Google Web ranking." However, as "ranking datasets is different from ranking Web pages" they're planning on using additional signals for Dataset ranking.

Open data

"The decision to rely on open standards (schema.org, W3C DCAT, JSON-LD, etc.) for markup is intentional, as Dataset Search can only be as good as the open-data ecosystem that it supports."

The post goes onto say that " Google Dataset Search aims to support a strong open data ecosystem by encouraging" adoption of open metadata standards, further development of these standards, "[the] culture of citing data the way we cite research publications" and the development of tools to leverage dataset metadata.

Thanks!

Just noting that +Dan Brickley gets a well-deserved shout out in the acknowledgements here. :)

#datasetsearch #datasets #schemaorg #structureddata

Post has attachment
"The Environmental Data Initiative (EDI) has just released an experimental implementation of the sitemaps.org and schema.org metadata to support search engine discovery and indexing"

This post provides links to the slides and a recording of a presentation that discusses this EDI initiative.

Moving forward, it seems, EDI will generate "schema.org metadata for all data landing pages on demand."

From what I've seen so far Dataset Search has been extremely well-received by publishers of datasets and are very much on board with exposing their datasets to Google, as per this EDI example.

I've memorialized this implementation on the Github page "Listing products and tools using schema.org" (http://bit.ly/2xVCPxX)

Would it make sense for us to choose two different entities as the main entities of a page? That is, on a webpage I have an article (Article) in which I talk about the drug Enantyum (Drug). In my opinion, both entities could be "mainEntity". Could I use the following?

"mainEntity": [{
"@type": "Article",
"headline": "Title of the article",
...
},
"@type": "Drug",
"name": "Enantyum",
...
}]

Thanks in advance.

Post has attachment
"Methods, systems, and apparatus, including computer programs encoded on computer storage media, for triggering rich results in response to queries"

Fascinating look at the Google patent "Rich Results Relevant to User Search Queries" from - who else? :) - the venerable +Bill Slawski.

Bill, I think your concluding thoughts with regard to the role of the Knowledge Graph are especially interesting.

KNOWLEDGE PANELS AS AN ALTERNATIVE FOR RICH RESULTS

Instead of a rich result, Google may have decided to show knowledge panels for books, which would be a business process decision that it could be faced with when it comes to other types of entities that it might show answers for. Here is a knowledge panel for the Book, The Sun Also Rises, which contains a lot of the things that this patent tells us a rich result would contain...

Indeed. I think one of the things we're witnessing now is Google gradually morphing from rich results/rich snippets to Knowledge Panels, as the Graph grows and information that was once restricted to rich results Google is able to percolate into Knowledge Panels.

Post has attachment
Google adds support for IPTC metadata in Google Images

"As part of a collaboration between Google, photo industry consortium CEPIC, and IPTC, the global technical standards body for the news media, you can now access rights-related image metadata in Google Images."

So, as of now, Google has "added Creator and Credit metadata whenever present to images on Google Images" with Copyright Notice metadata to be adding in the coming weeks.

I echo +Michael Andrews' sentiment about this on Twitter (http://bit.ly/2y3qwzN):

"This is cool, because it shows that search results use many vocabularies, not just schema.org (as important as that is!). Well done IPTC!"

#images #metadata #iptc #cepic #rightsmanagement

Post has attachment
Google makes several AMP-facing tweaks to their structured data requirements for article

On 20 Sept. 2018 Google's structured data guidelines for Article (http://bit.ly/2EX4Neu) were changed to accommodate and highlight AMP pages (Accelerated Mobile Pages), and in particular AMP stories.

* List of "enhanced features" for which an article might be eligible extends from "top stories carousel and rich result features" to "top stories carousel, host carousel, Visual stories, and rich result features (i.e. "host carousel" and "Visual stories" are new). "Visual stories" is a reference to AMP stories (https://www.ampproject.org/stories/).
* Markup examples, previously for "an Article object" and "a Video object" are now "an AMP page with Article object" and "an AMP page with Video object".
* Expanded guidelines, including further information on AMP logo guidelines and AMP story metadata (see further details about AMP story metadata with accompanying screenshots in the comments).
* Expanded guidelines about the use of the datePublished property (the date shouldn't change, use of hour information in the timestamp recommended, value for dateModified should be more recent than that of datePublished).
* Expanded guidelines about the use of the headline property ("For AMP stories, the headline should match the text in the first cover page in the AMP Story").
* Expanded guidelines about the use of the image property ("Due to format differences in search results, the followingAdditional image guidelines only apply to general AMP pages, not AMP stories. AMP stories have different requirements for images."). Again, see comments about AMP story metadata.
* More emphasis on the fact that video objects are only supported for AMP pages (from "Video objects are not supported on non-AMP pages" to "Video objects are only supported on AMP pages", with the declaration now in bold).

#amp #schemaorg #articles #ampstories
Photo

Post has attachment
Keyword research, meet semantics

What is a "keyword ontology" you ask?

"A keyword ontology is a knowledge graph describing relationships between the keywords your target audiences frequently use in search queries and the content about the products and services you sell."

A great deck from Mathewson, Priestly and Segal of IBM - required reading, I'd even say, for search marketers who have the ambition to become semantic search marketers. :)

#keywords #ontologies #taxonomies #machinelearning
Wait while more posts are being loaded