Specify GF client application

[FranckCo]

[francescadag]

The following document contains an analysis of how the client application for the GF pilot could be structured.
The mockups of the services of this application are also shared.
INTERTSTAT Client Applications Analysis - GF pilot.docx

GF pilot mockups.zip

[francescadag]

Correct the coordinates for the French facilities in the GraphDB gf-staging repository (the uploaded Latitude and Longitude values are swapped, see the Figure).

[francescadag]

Check the possibility to replace the ID of the Italian museum facilities with the original ID from the MiBACT end-point, so that it is possible to execute federated queries.

The figure shows some of these facilities with the IDs they currently have.

[francescadag]

Check the possibility to add the property igf: inLAU also for the Italian museum facilities otherwise it is not possible to display these points on the map starting from the Municipality selected by the user.

The figure shows one of these facilities and the properties it currently has, to which to add the property igf: inLAU, as all the other facilities in the repository

[francescadag]

The French facilities have only a code and the coordinates associated with them: it would be useful to also add the name of the facilities (and, if available, also a description, address and any other useful information present in the BPE database).

the figure shows a facility of this type and the properties it currently has

[romaintailhurat]

Correct the coordinates for the French facilities in the GraphDB gf-staging repository (the uploaded Latitude and Longitude values are swapped, see the Figure).

Hi Francesca!

We think it is the other way around. 😅

The WKT 2D Point we provide has both an X and a Y, and in the geodetical projection, X is for longitude and Y for latitude.

I corrected the code in order to have the italian points following this convention. You can switch to the gf-test repository to check, once you're ok i'll push to the staging repo. You only need a slight update to your code in order to be aligned with this semantic.

[romaintailhurat]

Check the possibility to replace the ID of the Italian museum facilities with the original ID from the MiBACT end-point, so that it is possible to execute federated queries.

The figure shows some of these facilities with the IDs they currently have.

We are using the last part of the subject property found in the original graph to produce our id property (see here).

What do you think we should use instead? If you want to link to the Mibact entity, we could use a owl:sameAs ?

[francescadag]

Check the possibility to replace the ID of the Italian museum facilities with the original ID from the MiBACT end-point, so that it is possible to execute federated queries.
The figure shows some of these facilities with the IDs they currently have.

We are using the last part of the subject property found in the original graph to produce our id property (see here).

What do you think we should use instead? If you want to link to the Mibact entity, we could use a owl:sameAs ?

Hi Romain, could you write the query you ran on the Mibact endpoint to get those results?
The query I make is this:

prefix geo:<http://www.w3.org/2003/01/geo/wgs84_pos#>
prefix cis:<http://dati.beniculturali.it/cis/>
prefix l0:<https://w3id.org/italia/onto/l0/>
SELECT DISTINCT ?LOD ?municipality ?ID ?cultural_facility ?address ?Email ?WebSite {
  ?LOD a cis:CulturalInstituteOrSite 
   ; cis:institutionalCISName ?cultural_facility
   ; cis:hasSite/cis:siteAddress ?addressSite .
  ?addressSite clvapit:fullAddress ?address 
   ; clvapit:hasCity/rdfs:label ?municipality .
?LOD cis:ISILidentifier ?ID .
    optional {
     ?LOD smapit:hasOnlineContactPoint ?contactPoint .
     optional { ?contactPoint smapit:hasTelephone [smapit:hasTelephoneType <https://w3id.org/italia/controlled-vocabulary/classifications-for-public-services/channel/031> ;
                                                   smapit:telephoneNumber ?Telefono] }
     optional { ?contactPoint smapit:hasTelephone [smapit:hasTelephoneType <https://w3id.org/italia/controlled-vocabulary/classifications-for-public-services/channel/033> ;
                                                   smapit:telephoneNumber ?Fax] }
     optional { ?contactPoint smapit:hasEmail [smapit:emailAddress ?Email] }
     optional { ?contactPoint smapit:hasWebSite [smapit:URL ?WebSite] }    
    } 
FILTER(str(?municipality)='Agrigento') .
 } 
ORDER BY ?cultural_facility

and the results are here.
As you can see the ID is different from the typology of ID you get from your query. I'll compare our two queries to understand how to make the results converge, thanks

[francescadag]

Correct the coordinates for the French facilities in the GraphDB gf-staging repository (the uploaded Latitude and Longitude values are swapped, see the Figure).

Hi Francesca!

We think it is the other way around. 😅

The WKT 2D Point we provide has both an X and a Y, and in the geodetical projection, X is for longitude and Y for latitude.

I corrected the code in order to have the italian points following this convention. You can switch to the gf-test repository to check, once you're ok i'll push to the staging repo. You only need a slight update to your code in order to be aligned with this semantic.

So you switched the Italian points to follow this convention and you left the French points as they appear in the image I had shared, is that correct?
Based on this I will do a test on the gf-test and I'll let you know, thanks