FertilizationOperation schema questions

[arruda]

So as I was discussing with @JackJackUM , I noted some points that I think are a bit confusing on the FertilizationOperation schema.

From what I saw here on the ocsm-profile.ttl, the FertilizationOperation should contain the following fields:

• hasStartDateTime
• hasEndDateTime
  But right now I only see the "hasTimestamp" field on the schema.

I believe that these farm operations should indeed the these start/end time fields, right? @rapw3k @JackJackUM

Another point that I saw was regarding the field:

• plan
  which I cant seem to find in the ocsm-profile.ttl, nor the cross-domain.ttl

From the fertilization.yml it seems that this is part of te foodie ontology, but it doesn't really match what is in there. Should we just drop this "plan" field then?

[arruda]

So from my current implementation of the FertilizationOperation on the FarmCalendar, this is the example output I get when retrieving a specific fertilization operation:
GET /api/v1/FertilizationOperation/1/
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/ld+json
Vary: Accept

{
    "@context": [
        "https://w3id.org/ocsm/main-context.jsonld"
    ],
    "@graph": [
        {
            "@id": "1",
            "http://w3id.org/ocsm/operationType": {
                "@id": "http://localhost:8002/api/v1/FarmOperationTypes/1/"
            },
            "http://w3id.org/ocsm/description": "Fertilization of olive orchards",
            "http://w3id.org/ocsm/hasStartDatetime": "2024-09-24T03:08:00+00:00",
            "http://w3id.org/ocsm/hasEndDatetime": "2024-09-24T04:09:00+00:00",
            "http://w3id.org/ocsm/hasApplicationMethod": "dispersion",
            "http://w3id.org/ocsm/isOperatedOn": {
                "@id": "http://localhost:8002/api/v1/FarmParcels/1/"
            },
            "http://w3id.org/ocsm/usesFertilizer": {
                "@id": "http://localhost:8002/api/v1/Fertilizer/1/"
            },
            "@type": [
                "http://w3id.org/ocsm/FarmOperation"
            ]
        }
    ]
}

You can also visualise the current endpoint in the online SwaggerEditor by importing on it the URL to the schema.yml file from the farmCalendar (https://raw.githubusercontent.com/openagri-eu/farmcalendar/refs/heads/farm-operations-ocsm/schema.yml)
Again the end-endpoit for this example output is on the /api/v1/FertilizationOperation/{id}/ (just so that you know what to look for).

With this in mind, I have another question: Should the fields be as "http://w3id.org/ocsm/isOperatedOn" or should they be just isOperatedOn?

[JackJackUM]

Hi @arruda , nice! Did you know this website [JSON-LD playground(https://json-ld.org/playground/)? You can use it to check your JSON-LD specs/files.

One comment I have is that you now put all types and properties in the OCSM namespace "http://w3id.org/ocsm/". Actually, most of them come from other ontologies with a different namespace. For instance isOperatedOn comes from Ploutos and the IRI is: "https://www.tno.nl/agrifood/ontology/ploutos/common#isOperatedOn". I think the output for your FertilizationOperation should also contain these correct namespaces/IRIs.

Finally, the fertilization.yaml on the repo should be made in sync with your implementation. So, a third party can then see in the YAML what he/she can expect in JSON-LD format.

[arruda]

Hi @JackJackUM thanks for the feedback, this point on the namespace was also another question that I had. And it indeed seemed strange, like I was renaming the namespace by doing that.
I'll update the necessary things on the farm calendar side and I'll also check out the link you sent for the validation.

[rapw3k]

hi @arruda sorry about coming back so late with this issue.
I think this was already clarified, but just in case, i will iterate it again:

in the data payload, you dont actually need to use the namespace of the terms, e.g., http://w3id.org/ocsm/isOperatedOn (which in fact would be https://www.tno.nl/agrifood/ontology/ploutos/common#isOperatedOn).

That is exactly the purpose of having the context in JSON-LD, so that in your payload you only use the term name.

[rapw3k]

hi @arruda please confirm if we can close this