RT @angelalinghuang: ...aand mapped some textile stuff... Maps + textiles = Great friday! 🧵🌍❤️
#EuropeThroughTextiles
#manymapsmakemehappy…
RT @angelalinghuang: ...aand mapped some textile stuff... Maps + textiles = Great friday! 🧵🌍❤️
#EuropeThroughTextiles
#manymapsmakemehappy…
We have extended the #nodegoat Documentation & Guides
https://nodegoat.net/documentation
https://nodegoat.net/guides
More info in this blog post: https://nodegoat.net/blog.s/57/extended-nodegoat-documentation--guides
@marnixvb @mmmenno @CREATE_UvA @webmappery @HuygensING Bedankt, het werkt weer!
@mmmenno @CREATE_UvA @HuygensING @marnixvb Dan hopen we samen!
@HxxxKxxx @ERC_Research @LMU_Muenchen @nodegoat Thanks! 4 years and over 20 people involved.
@mmmenno @CREATE_UvA @HuygensING OK! Enig idee wie daar over gaat? cc @marnixvb
The @ERC_Research project 'METROMOD' at the @LMU_Muenchen has launched their @nodegoat public user interface: https://archive.metromod.net/
More info in this blog post: https://lab1100.com/update.s/51/launch-of-metromod-archive
#digitalarthistory #dataviz #digitalhumanities
@CREATE_UvA @webmappery @mmmenno is http://tiles.amsterdamtimemachine.nl ter ziele gegaan, of zijn de tiles elders te vinden?
New partnership established with Bölcsészettudományi Kutatóközpont
#HGIS #researchinfrastructure #nodegoat
https://lab1100.com/update.s/50/new-partnership-established-with-blcsszettudomnyi-kutatkzpont
RT @retro_conflicts: Pictorial summary of today's paper 14:30 CET:
#merchantsmarks @nodegoat https://twitter.com/retro_conflicts/status/1428658107283132416
The #nodegoat #LOD workshop series ‘Linking your Historical Sources to Open Data’ is happening next week!
More info and registration here: https://nodegoat.net/blog.s/56/linking-your-historical-sources-to-open-data-workshop-series-organised-by-cost-action-nep4dissent
RT @HxxxKxxx: Check out my team's results in “Cultural Data Science” here:
➡️http://dahss21.harald-klinke.de/
#DAHSS21 #datascience #arthistory #di…
@conzept__ This was a prototype, the live version runs at https://manto.unh.edu/. There is no public list of all projects available.
@conzept__ Not completely sure what you mean, however, every query or object has its own URL, e.g. https://ernie.uva.nl/viewer.p/21/56/filter/0-OR:grimm/grid/. It depends on the project what kind of parameters are exposed.
@conzept__ Technically this is no problem at all as you can query any nodegoat project via an API: https://nodegoat.net/blog.s/26/nodegoat-api However, not many projects choose to publish their data like this.
Contact Guido Abbattista to see how GSR plans to publish their data https://disu.units.it/it/dipartimento/persone/abbattista-guido/1714
How can your project make use of #LinkedOpenData resources? Register for the workshop ‘Linking your Historical Sources to Open Data’ to find out!
@nep4dissent @COSTprogramme @wikidata #LOD https://twitter.com/nep4dissent/status/1425749068253437952
RT @nep4dissent: #Nep4Dissent in cooperation with @LAB1100 invites to participate in a workshop series "Linking your Historical Sources to…
RT @PelagiosNetwork: New week = new partner! Today we welcome the good folks @nodegoat (and their goat-wranglers @LAB1100) as one of the la…
RT @PelagiosNetwork: New week = new partner! Today we welcome the good folks @nodegoat (and their goat-wranglers @LAB1100) as one of the la…
@lorenzo251193 @nrchtct @nodegoat @w3c Sounds very reasonable. From a historical perspective we missed the opportunity to express relational date statements with ISO8601 / EDTF, see https://www.youtube.com/watch?v=N3NAJ7CfmAU
Congrats! Very happy to see a #nodegoat installation serve #wikidata like this https://twitter.com/GretaHawes/status/1415944576800460802
@nrchtct @nodegoat @lorenzo251193 @w3c Our implementation is based on logical operators, which would map to different ontologies when needed. We foresee @nodegoat ChronoJSON to be able to do what we want to do, and map to a generic ChronoJSON format for exchange, see https://nodegoat.net/guides/chronologystatements
@nrchtct @nodegoat @lorenzo251193 @w3c Thanks. We’ve recently been notified about http://chronojson.org. We would be happy to talk about how a streamlined ChronoJSON would relate to http://w3.org/TR/owl-time/ and other ontologies and vocabularies.
RT @angelalinghuang: Great day! Not only because I got a #nodegoat sticker, but we officially kick-started our research environment with @L…
RT @angelalinghuang: Great day! Not only because I got a #nodegoat sticker, but we officially kick-started our research environment with @L…
#HNRResHist2021 Slides of our presentation on @nodegoat #ChronoJSON:
https://docs.google.com/presentation/d/1ZzqcFPWdXpz8VJj2aw7-BzxpYzpD_OGRh44dQG61Ibc/present https://twitter.com/HNR_org/status/1410942632927412229
RT @infoclio: Die Tagung "From source to visualization" vereinte am 4.6.21 Forschende aus ganz Europa, die mit der virtuellen Forschungsumg…
RT @ahmadzakijp: Politics of Visualizationというのは確かにあります。Nodegoatとかを使って、(生存者の)Mapping Memory Landscapesを試みています。記憶、というのは扱いが難しいはずですが、だからこそデータの量…
@docuracy @nodegoat Yes, but your example is actually possible using the relationality in the statements, which in @nodegoat indeed entails a lookup.
@docuracy @nodegoat Right! So the syntagma is there, but we need to extend the paradigm to support definable algorithms. It's on the suggested features list!