search

dbpedia / databus-maven-plugin

Databus Maven Plugin: Aligning Data and Software Lifecycle with Maven
GNU Affero General Public License v3.0
6 stars 10 forks source link

filtering info in URLs #141

Open m1ci opened 3 years ago

m1ci commented 3 years ago

Hi,

Currently, the artifact URLs are fixed and they dont change w.r.t. the selected filters (e.g. language, format, etc.). This makes it difficult (impossible) to share URL of an exact artifact.

Suggestion, include the filtering option in the URL, e.g. for selected "en" provide:

https://databus.dbpedia.org/dbpedia/generic/infobox-properties/2020.10.01?language=en

Similarly, can be added the filtering option for the formats, compressions, etc.

JJ-Author commented 3 years ago

@holycrab13 I think we discussed sth. like this already. maybe you could paste our ideas here so that Milan can comment?

kurzum commented 3 years ago

This makes it difficult (impossible) to share URL of an exact artifact. @m1ci The artifact can be pinpointed exactly, also the version:

As I see it, the use case you are describing is to pinpoint a specific set of files/distributions inside a version of an artifact.

The design up to now uses sparql for this. In addition, we are also implementing GET for linked data. To realize this feature, we would need to implement the most frequent features (e.g. https://databus.dbpedia.org/dbpedia/generic/infobox-properties/LATEST) used in SPARQL, which might be quite difficult and maybe unnecessary, since there is SPARQL AND collections. So this would be a convenience feature, but it is not essential.

@m1ci https://databus.dbpedia.org/yasgui offers a link sharing option. The query can be exported from the query tab at the artifact/version.

Jan is working on making collections more modular, i.e. not one big query, but more <datadependency> maven style description:

<dependency>
      <account>dbpedia</account>
      <group>generic</group>
      <artifact>infobox-properties</artifact>
      <version>LATEST/2016.10.10</version>
      <selector>lang=en;formatExtension=ttl</selector>
</dependency>

I think that we should do this first. Especially, since we still need to formalize the content variants and make them consistent.