- From: Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au>
- Date: Wed, 16 Feb 2022 22:50:41 +0000
- To: "public-sdwig@w3.org" <public-sdwig@w3.org>
- Message-ID: <ME2PR01MB288271FCC2AE3A659CF12BC388359@ME2PR01MB2882.ausprd01.prod.outlook.com>
Note this discussion over at Schema.org From: Mark Harrison <notifications@github.com> Sent: Thursday, 17 February, 2022 00:48 To: schemaorg/schemaorg <schemaorg@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [schemaorg/schemaorg] GeoShape's box specification is unclear on the expected order of the points (#1538) It would be really helpful if at least one real-world example can be included for * https://schema.org/polygon * https://schema.org/circle * https://schema.org/line * https://schema.org/box so that there is no ambiguity about 1. the expected format of the text string 2. whether latitude appears before longitude (noting that GeoJSON puts longitude before latitude) 3. whether elevation is included in the string 4. which delimiter is used between latitude and longitude (and elevation if present) - is that a space or a comma? 5. which delimiter is used between points - is that a space or a comma? Without such worked examples, such properties are effectively unusable to many people because the specification is insufficient. Thanks to @rcoup<https://github.com/rcoup> for the pointer to https://developers.google.com/search/docs/advanced/structured-data/dataset#space it looks like the answers are 1. "lat long lat long lat long ..." 2. latitude before longitude in all string values for schema.org/GeoShape properties 3. elevation is excluded from such strings 4. space between latitude and longitude 5. space between points I would be happy to develop examples and submit a pull request. — Reply to this email directly, view it on GitHub<https://github.com/schemaorg/schemaorg/issues/1538#issuecomment-1041509536>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEUQLYJHWMHS2CGT3BI7VTU3OTKTANCNFSM4DCB5Q2Q>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: <schemaorg/schemaorg/issues/1538/1041509536@github.com<mailto:schemaorg/schemaorg/issues/1538/1041509536@github.com>>
Received on Wednesday, 16 February 2022 22:51:36 UTC