Create Claim-example-taxonomic-treatment.json

[pbuttigieg]

Addressing #24

[gsautter]

@pbuttigieg could you take a look at plazi/treatmentBank#115 (comment) and plazi/treatmentBank#115 (comment) ?

The former refers to the open question of how to specifically embed the materials citations within this JSON framework, and yet more specifically any given coordinates, especially since my understanding was for the main goal to be sharing occurrence data.

Also, while working with the example, I got the impression the basis for the example was the HTML page proper ... in case it helps, there is the underlying XML document, which holds a good few more details than we can conveniently show in the HTML: https://tb.plazi.org/GgServer/xml/423BD1464079EE7844C5FE28FE592E10 (the HTML is produced from this XML via XSLT).

[pbuttigieg]

@pbuttigieg could you take a look at plazi/treatmentBank#115 (comment) and plazi/treatmentBank#115 (comment) ?

Will do

The former refers to the open question of how to specifically embed the materials citations within this JSON framework, and yet more specifically any given coordinates, especially since my understanding was for the main goal to be sharing occurrence data.

Should be solvable. Will comment there.

Also, while working with the example, I got the impression the basis for the example was the HTML page proper ... in case it helps, there is the underlying XML document, which holds a good few more details than we can conveniently show in the HTML: https://tb.plazi.org/GgServer/xml/423BD1464079EE7844C5FE28FE592E10 (the HTML is produced from this XML via XSLT).

We use the standard web architecture approach where the JSON-LD / schema.org (containing rich metadata, beyond what is usually shown on a web page) can be embedded in an HTML page. Your sitemap.xml can link out to the JSON-LD files directly too.

[gsautter]

We use the standard web architecture approach where the JSON-LD / schema.org (containing rich metadata, beyond what is usually shown on a web page) can be embedded in an HTML page. Your sitemap.xml can link out to the JSON-LD files directly too.

The sitemap wasn't the point ... was saying that there might be more data in the XML underlying each individual treatment than there is showing in the HTML we produce to display the treatments ... I'm absolutely aware that the JSON-LD will go into the header of that HTML page, but the source data we produce the the JSON-LD from might be more comprehensive in the underlying XML version of the treatment ... was basically saying "there might be some additional data in that other format, in case you want to include that in your modeling".

[pbuttigieg]

We use the standard web architecture approach where the JSON-LD / schema.org (containing rich metadata, beyond what is usually shown on a web page) can be embedded in an HTML page. Your sitemap.xml can link out to the JSON-LD files directly too.

The sitemap wasn't the point ... was saying that there might be more data in the XML underlying each individual treatment than there is showing in the HTML we produce to display the treatments ... I'm absolutely aware that the JSON-LD will go into the header of that HTML page, but the source data we produce the the JSON-LD from might be more comprehensive in the underlying XML version of the treatment ... was basically saying "there might be some additional data in that other format, in case you want to include that in your modeling".

I'm not clear on why you wouldn't include all the data from the XML into the JSON-LD. Naturally, that's your choice.

if you wish to link out to an XML document with more metadata, you could use the isBasedOn property to create the trace

[gsautter]

We use the standard web architecture approach where the JSON-LD / schema.org (containing rich metadata, beyond what is usually shown on a web page) can be embedded in an HTML page. Your sitemap.xml can link out to the JSON-LD files directly too.

The sitemap wasn't the point ... was saying that there might be more data in the XML underlying each individual treatment than there is showing in the HTML we produce to display the treatments ... I'm absolutely aware that the JSON-LD will go into the header of that HTML page, but the source data we produce the the JSON-LD from might be more comprehensive in the underlying XML version of the treatment ... was basically saying "there might be some additional data in that other format, in case you want to include that in your modeling".

I'm not clear on why you wouldn't include all the data from the XML into the JSON-LD. Naturally, that's your choice.

if you wish to link out to an XML document with more metadata, you could use the isBasedOn property to create the trace

The goal is very much to include all the data from the XML into the JSON-LD ... the reason I pointed you to the XML is that I was under the impression your example was lacking some of the details the XML holds available, basically only including what's visible in the HTML, so I wasn't sure you were aware of the XML and that it had yet more data available.