Re: Toward easier RDF: a proposal


Thanks for gathering the aspects on
As a developer who was involved in online course creation about Semantic
Web I want to give this issue a different spin. A few ideas:

   - If I want to start on new technologies, sometimes I just lack the good
   ideas that motivate me to start creating something - how about a list of
   small to advanced features/projects that help you learn? (open source
   projects one can fork and start off)
   - a collection of resources on how to get started is also not quite
   prominent out there yet, good solid resources. (I recently use a lot because of my current needs -> not
   related to semantic web)
   - I would also follow something like live coding sessions (idea:


On Mon, 10 Dec 2018 at 18:09, Franconi Enrico <> wrote:

> Hi,
> I believe that, in order to properly/correctly solve this issue, SPARQL
> implementations could provide a mean to get for each bnode in a SPARQL
> query answer the data graph node **bound** to it, e.g., for each SPARQL
> query result  there could be a table with bindings: <result-bnode,
> data-graph-node>.
> IMHO it would be wrong (and not necessary, in this case) to give
> persistent identifiers to bnodes.
> cheers
> --e.
> On 10 Dec 2018, at 17:30, David Booth <> wrote:
> On 12/10/18 5:34 AM, Michael Brunnbauer wrote:
> I'd really like to see mandatory persistent blank node identifiers in
> SPARQL - so I can easily do followup queries for blank nodes from a SPARQL
> result. Is this a big deal? I think some triples stores can already do
> this.
> Which issue do I upvote to get this?
> Blank nodes #19:
> David Booth


Software Engineer @Semantic Web Company <>
Diversity Lead @GDGVienna <> & @
WomenTechmakersVienna <>

Received on Tuesday, 11 December 2018 16:47:37 UTC