Re: How to express a Person's height

Thanks for the enthusiastic replies though I'm well aware of how I can
resolve this by changes the values into inches (in this case) - and even
how to do this quick and dirty either via a spreadsheet editor or server
side solutions. I was just curious to know whether by now this exercise
could be completely bypassed altogether because there's something like a
'plus' or 'and' property/operator.

I guess my brain works in strange ways sometimes as I can imagine such a
functionality might be useful to be able to specify terms/properties that
don't exist in any other schema/ontology, eg: a property called
'skinFirmness' (a real life example for a site I'm working on at the
moment) - something which I currently describe as much as possible via the
'sameAs' property:

{
  "@type":"PropertyValue",
  "name":"skinFirmness,
  "sameAs":
  [
    "https://en.wikipedia.org/wiki/Human_skin",
    "https://www.wikidata.org/wiki/Q5259911",
    "http://dbpedia.org/page/Human_skin",
    "https://www.dictionary.com/browse/firmness",
    "https://dictionary.cambridge.org/dictionary/english/firmness"
  ],
  "value":
  {
    "@type":"StructuredValue",
    "name":"loose",
    "sameAs":
    [
      https://en.wikipedia.org/wiki/Excess_skin
      https://www.wikidata.org/wiki/Q24026721
      http://dbpedia.org/page/Excess_skin
    ]
  }
}

Though I'm highly doubtful that:

"sameAs":
  [
    "https://en.wikipedia.org/wiki/Human_skin",
    "https://www.wikidata.org/wiki/Q5259911",
    "http://dbpedia.org/page/Human_skin",
    "https://www.dictionary.com/browse/firmness",
    "https://dictionary.cambridge.org/dictionary/english/firmness"
  ],

will be understood as: Skin firmness.

Like with the height values mentioned earlier, defining 'concatenated'
values such that they're understood properly understood by 'merging' two
terms/values via a 'plus' or 'and' operator (thus making possible to
generate more complex terms/properties).

Now again, my brains walks strange paths sometimes, and I'm not even sure
whether there are any data consumers out there that would be interested in
mining such 'concatenated' property/value sets, I was just wondering
whether such things are even possible.



Op di 18 jun. 2019 om 11:32 schreef Martin Bean <martin@martinbean.co.uk>:

> For an organisation with limited resources, marking up a person’s height
> in a complex value like a sum of values is going to be more complicated
> than just saying “The person is 5-foot-7, which is 170 centimetres.”
>
> You don’t have to use the same scale of measure for the Schema mark-up as
> you do your “visible” mark-up. As I mentioned in a reply to you, I do this
> with pro wrestling and martial arts websites for fighter profiles:
>
> <dt>Height</dt>
> <dd itemprop="height" itemscope itemtype="
> http://schema.org/QuantitativeValue">
>     <span>5</span> <abbr title="feet">ft</abbr> <span>7</span> <abbr
> title="inches">ins</abbr>
>     <meta itemprop="unitCode" content="CMT" />
>     <meta itemprop="value" content="170.18" />
> </dd>
>
> On Tue, 18 Jun 2019 at 10:08, Jarno van Driel <jarnovandriel@gmail.com>
> wrote:
>
>> I understand why neither an array of values (eg, first item in the array
>> covers feet, second item inches) or an 'ItemList' would do the job,
>> however, since I've been missing on this mailing list for some time now
>> (personal reasons) I was wondering whether by now there was something like
>> an 'and' or 'plus' operator/property so that one can express: 5 feet + 7
>> inches.
>>
>> Now I also understand why converting a value lik 5'7" to a single
>> measurement (like inches) would be the way to go for many here but
>> unfortunately this isn't feasible for every publisher, especially ones that
>> don't do a lot of inhouse development (aka, people/organizations with small
>> budgets). And thus was hoping the community had maybe come up with
>> something already like the 'and' or 'plus' operator/property I mentioned
>> above.
>>
>> But alas, it looks like I'll be manually converting a few hundred height
>> ranges to a single measurement value after all. Thanks for weighing in
>> nonetheless though.
>>
>> Op di 18 jun. 2019 om 09:10 schreef Elias Kaerle <elias.kaerle@sti2.at>:
>>
>>> Hi Jarno, all,
>>>
>>> the range of the height property is Distance or QuantitativeValue which
>>> means that you can also add an array of Distances or QuantitativeValues
>>> - for example to express the same value in different units (see example
>>> below). What imho does not work is to understand the elements of the
>>> array as terms of a sum. This behaviour is not in the implicit semantics
>>> of the array and would require explicit knowledge about it.
>>>
>>> Example: height in feet and centimeters
>>>
>>> {
>>> "@context": "http://schema.org",
>>> "@type": "Person",
>>> "name": "Jarno",
>>> "height": [
>>>   {"@type": "QuantitativeValue",
>>>   "value": "5.7",
>>>   "unitCode": "FOT"},
>>>   {"@type": "QuantitativeValue",
>>>   "value": "181",
>>>   "unitCode": "CM"}
>>> ]
>>> }
>>>
>>> Cheers, E.
>>>
>>> Am 18.06.2019 um 07:59 schrieb Cox, Simon (L&W, Clayton):
>>> > The structured representation of a quantity (e.g. ft/in, DD-MM-YYYY)
>>> is important for human users/display, but a simple scaled representation
>>> (inches, days, seconds) is better for transport/loading. It would normally
>>> be recommended to convert to the structured representation only when
>>> building a UI.
>>> >
>>> > From: Michael Andrews [mailto:nextcontent01@gmail.com]
>>> > Sent: Tuesday, 18 June, 2019 15:35
>>> > To: Jarno van Driel <jarnovandriel@gmail.com>
>>> > Cc: schema.org Mailing List <public-schemaorg@w3.org>
>>> > Subject: Re: How to express a Person's height
>>> >
>>> > Very good question - how does one represent complex values for
>>> existing properties that seem to expect a single value?  Another case would
>>> be for a MonetaryAmount that needs to indicate two values, for example, in
>>> Mauritania where each ouguiya constitutes five khoums (meaning "one
>>> fifth"). The Malagasy ariary, whose division units is also not based on a
>>> power of ten, in addition to various historical currencies including the
>>> British pound before decimalization.
>>> >
>>> > This is what I tried, without successful validation.  Perhaps I am
>>> missing a trick.
>>> >
>>> > First, I tried an itemList for break out feet and inches:
>>> >
>>> > {
>>> > "@context": "http://schema.org",
>>> > "@type": "Person",
>>> > "name": "Jarno",
>>> > "height": {
>>> > "@type": "ItemList",
>>> > "itemListElement": [
>>> > {"@type": "QuantitativeValue",
>>> > "value": "5",
>>> > "unitCode": "FOT"},
>>> > {"@type": "QuantitativeValue",
>>> > "value": "7",
>>> > "unitCode": "INH"}
>>> > ]
>>> > }
>>> > }
>>> >
>>> > Next I tried using the PropertyValue
>>> >
>>> > {
>>> > "@context": "http://schema.org",
>>> > "@type": "Person",
>>> > "name": "Jarno",
>>> > "height": [
>>> > {"@type": "PropertyValue",
>>> > "value": "5",
>>> > "unitCode": "FOT"},
>>> > {"@type": "PropertyValue",
>>> > "value": "7",
>>> > "unitCode": "INH"}
>>> > ]
>>> > }
>>> > }
>>> > In both cases, got a message that height didn't expect the itemList or
>>> PropertyValue.
>>> >
>>> >
>>> > On Tue, Jun 18, 2019 at 5:10 AM Jarno van Driel <
>>> jarnovandriel@gmail.com<mailto:jarnovandriel@gmail.com>> wrote:
>>> > As a Dutch native (metric centric) I have run into something that has
>>> me clueless, namely how to express a Person's height using US measurement
>>> values like: 5'7"
>>> >
>>> > Can anybody please tell me if and how I should use QuantitativeValue
>>> for this without converting the value to, for example, centimeters or just
>>> inches?
>>> >
>>> > ______________________________________________________________________
>>> > This email has been scanned by the Symantec Email Security.cloud
>>> service.
>>> > For more information please visit http://www.symanteccloud.com
>>> > ______________________________________________________________________
>>> >
>>>
>>> --
>>> Elias Kärle, MSc
>>> Semantic Technology Institute
>>> University of Innsbruck
>>>
>>> ICT - Technologie Park Innsbruck
>>> 2nd Floor, Room 3S02
>>> Technikerstrasse, 21a
>>> 6020 Innsbruck
>>> Austria
>>>
>>> Tel.: +43 (0) 512 507 53738
>>> Skype: elias.kaerle
>>>
>>>
>
> --
> *Martin Bean*
> Web developer, consultant, author, and speaker
>
> *Website:* martinbean.co.uk
> *Twitter:* @martinbean <http://twitter.com/martinbean>
> *LinkedIn:* http://www.linkedin.com/in/martinbean
> *Skype:* mcbwebdesign
>