W3C home > Mailing lists > Public > public-schemaorg@w3.org > November 2017

Re: Proper labeling of a Matroska file

From: Stian Soiland-Reyes <stain@apache.org>
Date: Thu, 30 Nov 2017 10:20:25 +0000
Message-ID: <20171130102025.GD15575@biggie>
To: Alice Wonder <alice@domblogger.net>
Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
On Wed, 29 Nov 2017 17:51:13 -0800, Alice Wonder <alice@domblogger.net> wrote:
> Matroska audio that has three streams: AAC, Opus, and SRT
> 
> The question I have relates to how to properly add structured data for 
> the encodingFormat.
> 
> Is this json-ld kosher?
> 
> {"@type":"AudioObject",

You'll want to add also at the top:

  "@context":"http://schema.org/",

Then you can test it at https://json-ld.org/playground/

See "N-Quads" or "Compacted" and make sure all your properties are
represented as you intend.
  
Not sure what is the proper use of encodingFormat here - as you
indirectly point out Matroska is really a container format of multiple encoded
streams (possibly in several encoding formats).

Yet http://schema.org/encodingFormat also lists "mpeg4" as example,
which is also a container format like Matroska..

As encodingFormat just takes any text - then are there any convention
on how to name these formats? You used "AAC", "Matroska" etc, but the 
examples on http://schema.org/encodingFormat are just lowercase strings. 

This hints to me that there is basically no semantics expected here, so
my opinionated feeling is that listing all of your formats (both
container and embedded) are OK :)


-- 
Stian Soiland-Reyes
The University of Manchester
http://www.esciencelab.org.uk/
http://orcid.org/0000-0001-9842-9718
Received on Thursday, 30 November 2017 10:25:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:37 UTC