- From: Thomas Passin <tpassin@tompassin.net>
- Date: Tue, 15 Feb 2022 10:34:21 -0500
- To: semantic-web@w3.org
On 2/15/2022 10:05 AM, David Booth wrote:
> On 2/15/22 07:02, Melvin Carvalho wrote:
>>> Am 15.02.2022 um 02:57 schrieb Nathan Rixham <nathan@webr3.org>:
> . . .
> >> I'd argue that having plain old JSON with some tiny spec
> >> which allows the complexity to be punted in to shared
> >> documents would be beneficial . . . .
>>
>> Here is one from 2011, though it could probably be updated for 2022
>> https://lists.w3.org/Archives/Public/public-rdf-wg/2011Mar/0565.html
>
> Nice proposal! I hadn't noticed it before. I like the line of thinking
> a lot. I think it merits serious consideration.
>
> David Booth
>
A nice feature of this format is that it could be manually written as an
indented list without all the commas, quotes and braces. A simple
script could convert this list to the actual JSON. This would be a very
quick and convenient way to author smallish instances.
Here's an example using a bit of one of the examples from the referenced
post:
"@vocab": "http://business.example.org/v/custom-gr-merged#",
"@base": "http://business.example.org/openinghours.html",
"@id": "#business",
"@type": "BusinessEntity",
"label": "Example Business, Inc.",
"legalName": "Example Business, Inc.",
"page": [
"http://business.example.com",
"http://business.example.org/openinghours.html"
],
"fn": "Example Business, Inc.",
Hand-written as an indented list:
@vocab: http://business.example.org/v/custom-gr-merged#
@base: http://business.example.org/openinghours.html
@id: #business
@type: BusinessEntity
label: Example Business Inc.
legalName: Example Business Inc.
page:
http://business.example.com
http://business.example.org/openinghours.html
fn: Example Business Inc.
Received on Tuesday, 15 February 2022 15:34:39 UTC