#artbase — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #artbase, aggregated by home.social.
-
Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.
-
Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.
-
Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.
-
Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.
-
Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.
-
This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:
https://github.com/rudof-project/rudof/issues/387
Amazing work by José Emilio Labra and the WESO team!!
-
This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:
https://github.com/rudof-project/rudof/issues/387
Amazing work by José Emilio Labra and the WESO team!!
-
This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:
https://github.com/rudof-project/rudof/issues/387
Amazing work by José Emilio Labra and the WESO team!!
-
This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:
https://github.com/rudof-project/rudof/issues/387
Amazing work by José Emilio Labra and the WESO team!!
-
This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:
https://github.com/rudof-project/rudof/issues/387
Amazing work by José Emilio Labra and the WESO team!!
-
I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/
-
I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/
-
I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/
-
I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/
-
I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/
-
-
-
-
-
-
Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.
This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.
-
Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.
This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.
-
Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.
This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.
-
Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.
This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.
-
Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.
This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.
-
Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅
-
Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅
-
Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅
-
Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅
-
Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅
-
With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>
For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!
-
With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>
For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!
-
With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>
For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!
-
With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>
For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!
-
With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>
For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!
-
For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.
-
For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.
-
For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.
-
For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.
-
For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.
-
So the renewed Artbase will be rendered by @abbe98's snowman <https://github.com/glaciers-in-archives/snowman>, a static site generator for SPARQL backends. As with most SSGs, the templating is super flexible (using gotemplates).
Which means the data model doesn't need to take into account the crutches required to read anything with Mediawiki's built-in Lua interpreter. Awesome!!
