Skip to content

APIFactory response #4

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
luigi-asprino opened this issue Oct 2, 2020 · 1 comment
Closed

APIFactory response #4

luigi-asprino opened this issue Oct 2, 2020 · 1 comment

Comments

@luigi-asprino
Copy link
Contributor

Hi,

I'm starting integrating the APIFactory response in the pipeline for generating and publishing data in RDF format.
In particular, I'm querying the activity_log dataset using the GET operation on /object/activity_log.
The API returned_me the following response (which I translated in TURTLE syntax)

<http://spice-apif.local/object/activity_log/5f7615001d44a45e997c63a3>
        a                    al:Browse , al:ActivityLogEntry ;
        al:datasetId         "activity_log" ;
        al:request           [ a                     al:HTTPRequest ;
                               al:agent              [ a       al:Agent ;
                                                       al:key  "datahub-admin"
                                                     ] ;
                               al:endpoint           "http://spice-apif.local/browse/activity_log" ;
                               al:httpRequestMethod  "al:GET" ;
                               al:payload            ""
                             ] ;
        al:summary           "Browse[GET] - http://spice-apif.local/browse/activity_log - Dataset:activity_log - Key:datahub-admin - Retrieve multiple documents via the browse interface" ;
        al:timestamp         2020 , 1601574144 ;
        al:timestamp_day     1 ;
        al:timestamp_hour    17 ;
        al:timestamp_minute  42 ;
        al:timestamp_second  24 .

There are two things that appear to me strange.

  1. The object of the al:httpRequestMethod associated with the http request, which is a literal, but I think that should be a resource. I expect as range of the property a controlled vocabulary of HTTP methods like al:GET, al:POST ecc.
  2. al:timestamp_year is missing, but there are two time stamps 2020 (which is the year) and 1601574144
@luigi-asprino
Copy link
Contributor Author

Concerning the second problem, the prefix of timestamp* properties in the JSON-LD response should be "al" instead of "_".

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant