Hi! From my perspective, I am also hesitant to adopt SPARQL, because it appears to me that no relevant commercial project has utilized it so far, really no popular database supports it (Oracle aside), and the machine learning and data analysis frameworks have not picked it up either. Having said that, it would be really nice to have an ad hoc programming-language representation of schema.org classes/objects and their properties. Should this be for PHP only? No, obviously not! How hard would it be to make your PHP-language approach generic? Let’s say there would be some implementation (no matter which language), which takes descriptions found on schema.org and turns them into code for any object oriented language? I have not looked at rewriting/transformation systems for a while (s.a. XSLT), but there should be some suitable frameworks/tools out there which allow this. Thoughts on this? Best wishes, Kim CODAMONO, Toronto, Ontario, Canada https://www.codamono.com On November 2, 2015 at 3:17:25 PM, Thad Guidry (thadguidry@gmail.com) wrote: Steven, When you say "common contract", what basis is this derived from ? Or is it that your organization has derived some best practices that define this common contract and you want to share it more outside of your existing Github account ? Or is it your intention that this common contract still needs more work or help from Schema.org stakeholders and experts to be proven as a best practice ? The reason I ask is that Schema.org is tech agnostic against tools, but when it concerns interfaces, well then that might open up discussion a bit more. I would ask for more detail from you in regard to: 1. How does your effort help or hinder PHP developers in working with Schema.org 2. Hod does your effort help or hinder Schema.org itself in relation to PHP programmatic use or access. Thad +ThadGuidry
Received on Monday, 2 November 2015 21:11:14 UTC