- From: Richard Wallis <richard.wallis@dataliberate.com>
- Date: Mon, 31 Jul 2017 10:44:49 +0100
- To: Vladimir Alexiev <vladimir.alexiev@ontotext.com>
- Cc: public-schemabibex@w3.org
Received on Monday, 31 July 2017 09:45:25 UTC
Thanks for your thoughts, especially on the property name. The nice thing about Schema.org properties is that they can all default to a Text value and in many of the cases you describe I am sure they will. Introducing QuantitativeValue however provides the opportunity for specificity when it arrises, as per some of the archive oriented examples such as a number of folders or lengths of shelving. ~Richard. Richard Wallis Founder, Data Liberate http://dataliberate.com Linkedin: http://www.linkedin.com/in/richardwallis Twitter: @rjw On 31 July 2017 at 10:08, Vladimir Alexiev <vladimir.alexiev@ontotext.com> wrote: > This is definitely needed. > > I like that the name materialExtent is specific, because in museum work > this means something very different: > Part of object or work contributed by an agent, measured in a dimension, > or described by a subject, or to which a material or technique statement > applies. > > I'm just not sure QuantitativeValue is useful in this case because: > - in my experience the extent texts are very unstructured and varied > - it's not likely one would want to search or sum by extent value (unless > you're planning a warehouse or something) > > Cheers! > >
Received on Monday, 31 July 2017 09:45:25 UTC