- From: Martin Hepp <mfhepp@gmail.com>
- Date: Thu, 3 Sep 2015 11:43:28 +0300
- To: arnaudmarquis@bluewin.ch
- Cc: public-schemaorg@w3.org
From a Web architecture perspective, it is sufficient to encode the URL of the resource in schema.org, since the media type in the response header will tell you the type of document. Matching between preferences for document formats and available formats is IMO best left to HTTP content negotiation at the protocol level and not added to schema.org meta-data. Plus, there is http://schema.org/encodingFormat for http://schema.org/MediaObject which could be used for the envisioned purpose. Martin ----------------------------------- martin hepp http://www.heppnetz.de mhepp@computer.org @mfhepp > On 02 Sep 2015, at 10:42, arnaudmarquis@bluewin.ch wrote: > > Hi, > > We have a case where we need structured data for publications. Each publication is a node on the website with a title, a short description, a date, an author and a link to the publication itself which is a PDF document. We could also imagine that we would have different types of documents (PDF, Word, Excel, etc.). What would be the way to reference such linked documents and what item type would best fit such a piece of content? > > > In my opinion, the Article type would fit our needs, but we should have a property such as “relatedDocument” (URL) and “relatedDocumentType” (Text) to allow for a distinction between the different file types. The related/linked document, in our case, is the core content of the node. > > > Regards, > Arnaud >
Received on Thursday, 3 September 2015 08:44:08 UTC