Re: Schema.org models

Hello Talley,

I'll try to contribute, although I am not sure I understood 100% your aim.

Schema.org is a joint effort to define a vocabulary for a wide range of
models. You can use the Schema.org vocabulary with any format that suits
your need in order to exchange or query data.

For example, we store our own entities in a triples datastore using the
schema.org vocabulary. We can query the same datastore using SPARQL and
export data using a variety of formats, such as RDF, n-turtles, JSON-LD and
so forth.

We also use a *refactorer* in order to convert existing Linked Open Data
Cloud (such as DBpedia entities) to the schema.org vocabulary. This could
be used as well for any domain specific vocabularies.

Being schema.org an initiative sponsored by the major search engines, the
schema.org web site also suggests using the *microdata* mark-up language
for users to define and publish their entities on Web pages. Search engines
are supposed to identify and understand most of these entities providing
better search results.

Are you looking to adopt schema.org to exchange data between application
modules and/or systems, or also to publish these data on the Web?

Cheers,
David


On Thu, Mar 14, 2013 at 3:12 PM, Talley, Brooks <brooks.talley@intel.com>wrote:

>  Hello, everyone. I'm a product strategist with Intel’s Cloud Service
> Platform group. We're building a platform of cloud services that enables
> developers to write cross-platform, cross-garden apps. Our flagship product
> is Intel Identity Services, but the suite of services includes Location,
> Context, and Commerce, Recommendations, Catalog, and Curation. ****
>
> ** **
>
> I am experiencing the need for an open, platform-agnostic way of
> representing common objects such as books, movies, restaurants, and so on.
> It turns out that Schema.org addresses many of these needs… but with a firm
> linkage between the object models and their HTML representations.****
>
> ** **
>
> However, when you look at the underlying ontology/models that Schema.org
> implements, there is no reason that the object models and HTML
> representations need to be so welded together. ****
>
> ** **
>
> I am looking at adopting the object models for data interchange between
> applications and even between developers, relying on the underling OWL
> object descriptions but representing the data in HTML, XML, JSON, or other
> formats as appropriate (including storing in databases with schemas mapped
> to the Schema.org OWL definitions).****
>
> ** **
>
> Benefits to developers include ease of interchange between applications,
> ease of repurposing data for Schema.org-marked-up web pages, and a large
> number of well thought out object models.****
>
> ** **
>
> Does anyone have experience with this kind of application of the
> Schema.org models, or feedback/advice on this approach?****
>
> ** **
>
> -Brooks****
>
> ** **
>



-- 
David Riccitelli

-- check the Swagger for WordLift <http://bit.ly/VtoM5H>
********************************************************************************
InsideOut10 s.r.l.
P.IVA: IT-11381771002
Fax: +39 0110708239
---
LinkedIn: http://it.linkedin.com/in/riccitelli
Twitter: ziodave
---
Layar Partner Network<http://www.layar.com/publishing/developers/list/?page=1&country=&city=&keyword=insideout10&lpn=1>
********************************************************************************