saref4city issueshttps://labs.etsi.org/rep/saref/saref4city/-/issues2019-12-03T15:08:07Zhttps://labs.etsi.org/rep/saref/saref4city/-/issues/1The ':' prefix is wrong2019-12-03T15:08:07ZRaul Garcia-CastroThe ':' prefix is wrongThe following prefix declaration is wrong:
```
@prefix : <https://w3id.org/def/saref4bldg#> .
```
It should be:
```
@prefix : <https://w3id.org/def/saref4city#> .
```The following prefix declaration is wrong:
```
@prefix : <https://w3id.org/def/saref4bldg#> .
```
It should be:
```
@prefix : <https://w3id.org/def/saref4city#> .
```https://labs.etsi.org/rep/saref/saref4city/-/issues/3Update the namespaces for compatibility with SAREF v32020-04-01T08:26:27ZRaul Garcia-CastroUpdate the namespaces for compatibility with SAREF v3The namespaces of SAREF4CITY have to be updated for compatibility with SAREF v3:
* https://saref.etsi.org/core/
* https://saref.etsi.org/saref4city/The namespaces of SAREF4CITY have to be updated for compatibility with SAREF v3:
* https://saref.etsi.org/core/
* https://saref.etsi.org/saref4city/https://labs.etsi.org/rep/saref/saref4city/-/issues/2The range of s4city:hasCalculationPeriod should be time:TemporalDuration2020-04-08T09:23:57ZRaul Garcia-CastroThe range of s4city:hasCalculationPeriod should be time:TemporalDurationThe range of s4city:hasCalculationPeriod should be time:TemporalDuration instead of time:TemporalEntity.
A temporal entity is either a time instant or a time interval. However, the period refers to some time duration independently of th...The range of s4city:hasCalculationPeriod should be time:TemporalDuration instead of time:TemporalEntity.
A temporal entity is either a time instant or a time interval. However, the period refers to some time duration independently of the interval.https://labs.etsi.org/rep/saref/saref4city/-/issues/4geo:location both as rdf:Property and owl:ObjectProperty2020-04-13T13:38:16ZRaul Garcia-Castrogeo:location both as rdf:Property and owl:ObjectPropertygeo:location is currently defined both as rdf:Property and as owl:ObjectProperty.
It should only be defined as rdf:Property, similarly as with the other geo: properties.geo:location is currently defined both as rdf:Property and as owl:ObjectProperty.
It should only be defined as rdf:Property, similarly as with the other geo: properties.https://labs.etsi.org/rep/saref/saref4city/-/issues/5adapt example uri to new convention2020-04-27T12:29:20ZMaria Povedaadapt example uri to new conventionAs agreed in the saref4envi extension, the example URI should follow:
<https://saref.etsi.org/saref4city/v1.1.2/example/<<<name_of_the_example>>>/>As agreed in the saref4envi extension, the example URI should follow:
<https://saref.etsi.org/saref4city/v1.1.2/example/<<<name_of_the_example>>>/>https://labs.etsi.org/rep/saref/saref4city/-/issues/8ERROR in SAREF Pipeline: .SAREF4CITY v1.1.2 - Issues in TS 103 673 Clause 9.4.22024-03-05T12:07:31ZMaxime LefrançoisERROR in SAREF Pipeline: .SAREF4CITY v1.1.2 - Issues in TS 103 673 Clause 9.4.2If a prefix declaration has prefix `geo`, then the namespace shall be equal to <http://www.opengis.net/ont/geosparql#>`. Got: `<http://www.w3.org/2003/01/geo/wgs84_pos#>`. See Clause 9.4.2 in TS 103 673.If a prefix declaration has prefix `geo`, then the namespace shall be equal to <http://www.opengis.net/ont/geosparql#>`. Got: `<http://www.w3.org/2003/01/geo/wgs84_pos#>`. See Clause 9.4.2 in TS 103 673.