Re: QAPage applicable properties @RDF #email #2018

Hi Jarno,

I tried to look at this from all directions but at the end of the day I believe this is the most reasonable way.

After all, if you have a QAPage it's only natural the main content of the page are Questions (Type), hence the question property (and answers) would fit perfectly and naturally (I add) - don't you think?

Isn't it a bit strange that a questions and answers page (QAPage) does not recognize question (property) and associated Question (Type)

Hope this helps clarify my line of thought,

Sante


 <applewebdata://7579052D-2406-4D5C-8AF2-AB0A47B3310B/0#>
ing.,Sante J. Achille - Multilingual Search Marketing Consulting & Services
a: Via Grotta di Navarra, 24 - 67100 L'Aquila - Italy m: +39 329.61.68.802 <tel:+39 329.61.68.802>
w: http://achille.name/ <http://achille.name/>  e: sante@achille.name <mailto:sante@achille.name>

 <https://www.facebook.com/sjachille>   <https://twitter.com/sjachille>   <https://www.linkedin.com/in/sjachille>   <https://plus.google.com/+SanteJAchille>
Sante is Chairman of SMXL Milan, 2018 <http://www.smxl.it/>
> On 23 Apr 2018, at 18:05, Jarno van Driel <jarnovandriel@gmail.com <mailto:jarnovandriel@gmail.com>> wrote:
> 
> Do we really need to expand the domain of these properties?
> 
> The way I see it a single Question could be chained to the page via either the 'mainEntity' or 'mainEntityOfPage' properties. And in case there are multiple Questions and Answer an ItemList of QorA's could be used and chained to the page via the properties I just mentioned.
> 
> Or am I crazy thinking along these routes?
> 
> 2018-04-23 16:27 GMT+02:00 Richard Wallis <richard.wallis@dataliberate.com <mailto:richard.wallis@dataliberate.com>>:
> Hi Sante,
> 
> I agree that it seems sensible that QAPage would have properties that would link to the Question(s) and Answer(s) Entities that are detailed on the page.  Also the simples way to implement this would be to expand the domains of the properties you mention (question <http://schema.org/question>, acceptedAnswer <http://schema.org/acceptedAnswer> and suggestedAnswer <http://schema.org/suggestedAnswer>).
> 
> I see this as being independent of your suggestion of expanding the domain speakable <http://schema.org/speakable>.  Speakable is a property of Article & WebPage and hence is available to be used on QAPage to identify the text of any element(s) on that page, including the text of a Question/Answer as being speakable.  I would assume that the text element of a Question or Answer would be speakable by default.
> 
> ~Richard.
> 
> 
> 
> Richard Wallis
> Founder, Data Liberate
> http://dataliberate.com <http://dataliberate.com/>
> Linkedin: http://www.linkedin.com/in/richardwallis <http://www.linkedin.com/in/richardwallis>
> Twitter: @rjw
> 
> On 23 April 2018 at 13:48, Sante J. Achille <sante@achille.name <mailto:sante@achille.name>> wrote:
> Hello,
> I believe it would make sense to introduce the question <http://schema.org/question>, acceptedAnswer <http://schema.org/acceptedAnswer> and suggestedAnswer <http://schema.org/suggestedAnswer> properties on QAPage <http://schema.org/QAPage> and make speakable <http://schema.org/speakable> a recognized property of Question <http://schema.org/Question>.
> 
> The way I see things, people ask questions and speakable <http://schema.org/speakable> is a signal to highlight those parts of a webpage which are identified as the most appropriate for an agent to use in providing vocal guidance/assistance and ultimately answer questions.
> 
> Thank you for your consideration - looking forward to reading feedback :)
> 
> Sante
> 
> 
>  <http://0.0.0.0/#>
> ing.,Sante J. Achille - Multilingual Search Marketing Consulting & Services
> a: Via Grotta di Navarra, 24 - 67100 L <https://maps.google.com/?q=Via+Grotta+di+Navarra,+24+-+67100+L+Aquila+-+Italy&entry=gmail&source=g>'Aquila - Italy <https://maps.google.com/?q=Via+Grotta+di+Navarra,+24+-+67100+L+Aquila+-+Italy&entry=gmail&source=g> m: +39 329.61.68.802 <tel:+39%20329.61.68.802>
> w: http://achille.name/ <http://achille.name/>  e: sante@achille.name <mailto:sante@achille.name>
> 
>  <https://www.facebook.com/sjachille>   <https://twitter.com/sjachille>   <https://www.linkedin.com/in/sjachille>   <https://plus.google.com/+SanteJAchille>
> Sante is Chairman of SMXL Milan, 2018 <http://www.smxl.it/>
> 
> 
>