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

Re: Proper labeling of a Matroska file

From: Alice Wonder <alice@domblogger.net>
Date: Thu, 30 Nov 2017 03:50:06 -0800
To: public-schemaorg@w3.org
Message-ID: <0eee0cb2-0c54-5bba-760f-7ba8af3bbaa9@domblogger.net>
On 11/30/2017 02:20 AM, Stian Soiland-Reyes wrote:
> 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/",

Yes that's in the full json-ld that is generated

>
> 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.

Thanks, I'll put them lower case

>
> 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 :)
>
>
Received on Thursday, 30 November 2017 14:27:09 UTC

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