Re: Common programming interfaces for schema.org objects

The most common audience of programmers is still imperative programmers. I say that though I’d also appreciate the SPARQL constructs, and additionally would love it if a database existed that I could use locally for queries. (Best I could do last I tried was to just download RDF data from the page, I’ve thought about sticking that at least in a gem for easy of use but..)

Orthogonally, I recently made a tool to try to introduce more lowly imperative programmers to the benefits of Schema.org:

https://github.com/mooreniemi/semcheck <https://github.com/mooreniemi/semcheck>

Alex


> On Nov 1, 2015, at 4:43 PM, Martynas Jusevičius <martynas@graphity.org> wrote:
> 
> Steven,
> 
> much more reusable transformers would be in the form of SPARQL
> CONSTRUCT queries instead of imperative (PHP or other) source code:
> http://www.w3.org/TR/sparql11-query/#construct
> 
> Martynas
> graphityhq.com
> 
> On Fri, Oct 30, 2015 at 6:14 PM, Steven Maguire <stevenmaguire@gmail.com> wrote:
>> Greetings,
>> 
>> I am interested in discussing the possibility of building and hosting PHP
>> interfaces for Schema.org data structures within the
>> https://github.com/schemaorg organization. My goal is to provide a
>> repository of interfaces that will serve as the common "standard" for
>> building open source projects that interact with Schema.org data structures.
>> 
>> I have recently begun an open source project to aid in the aggregation and
>> normalization of job data available in dozens of independent job listing
>> APIs. Part of this project was to outline the definition of "normalized" job
>> data; we selected the Schema.org JobPosting data structure. The project,
>> built in PHP, currently offers implementations of a design based on the
>> Schema.org standards.
>> 
>> We have now turned to a new project of building common format transformers
>> of these normalized job objects, into things like XML, CSV, JSON-LD, Excel,
>> Google Docs, etc. This project is currently dependent on the aggregation
>> package mentioned above; I would like to remove this dependancy. In order to
>> remove this, I have planned to create interfaces for the JobPosting objects
>> and host them in a separate repository, then update both aggregation and
>> transformation packages to depend on these common interfaces.
>> 
>> Before moving forward, I thought that the Schema.org organization would be a
>> better host of these assets so I wanted to propose this conversation.
>> 
>> Thoughts, feedback, and input are invited. My goal is to have clarity on the
>> following question:
>> 
>> Can I be granted permissions to create a repository within the
>> https://github.com/schemaorg organization with the intent of publishing PHP
>> interfaces for Schema.org data structures?
>> 
>> Cheers!
>> 
>> Steven Maguire
>