Community Page
- phildawes.net/blog/ Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Hi, Do you feel that your agility in Factor has improved since this post? Roger
- Thanks for the pointer - I've cleaned up the spam and regrettably added some moderation
- I'm loving the comments thread for this post. Can't decide whether to get my upholstery cleaned or do something about my fast food obesity.
- Cool - thanks Eric
- I pasted some code that does the moving sum in factor. http://paste.factorcode.org/paste?id=569#282
Jump to original thread »
Thanks to everybody that commented on my ‘global identifiers don’t scale‘ post (and especially for Seth and John’s responses). It’s obvious that I didn’t make myself very clear - sorry about that.
I think I made two main p ... Continue reading »
I think I made two main p ... Continue reading »
3 years ago
3 years ago
But when it comes to the SemWeb, you can *almost* already make the kind of no-URI descriptions you describe:
id::PhilDawes (weight 10st, date 24/12/2005)
id::PhilDawes (weight 10st 3lbs, date 26/12/2005)
consider id as a bnode, with associated properties maybe localId "PhilDawes", weight "10st", date "24/12/2005" etc.
Danbri's Identifying Things in FOAF post puts the case well for the indirected id idea.
However, there is quite a big *almost*. How do you identify the relationships between things? The value of "weight" property above is expressed as a string containing the units - that isn't likely to be a very common use of the term "weight". Although disambiguation of the same multi-reference form as the thing-identification could be done, if I remember correctly this led to one of the issues with the early Semantic Networks. You can build lovely big interconnected graphs, but then if you try to do anything with them (query, inference, transformation) you've got a problem. The use of global IDs for the relationships helps make these problems tractable.