What steps will reproduce the problem? 1. Create a moment that contains target.url and target.description (these are minimal examples. this happens with target.url and any other valid schema.org data) 2. Save this moment using POST https://www.googleapis.com/plus/v1/people/me/moments/vault

If the target.url is omitted, the moment is generated without problems.

What is the expected output? What do you see instead? Expected that the moment would be created, using target.url as a link for the moment and either supplementing or overwriting the schema.org data used from there by the data that was explicitly provided in the moment target.* values.

Actual result returns 400 - Invalid value

What version of the product are you using? On what operating system? tested using both direct URL writes as well as the javascript library

Please provide any additional information below. There are situations where the target page may not be able to generate the snippet information, or may use javascript to dynamically create the data to display. In such cases, the googlebot would not be able to get the information, since it does not run javascript, but it would still be highly beneficial to have the page used as a URL target for moments when shown in the vault, but to have the values explicitly set when creating the moment.

See this post about a 'real life' example of this issue: https://plus.google.com/110708326411316526253/posts/gxZzwuaZqSS