Search by property

Jump to navigation Jump to search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Text"Text" is a predefined property that represents text of arbitrary length and is provided by Semantic MediaWiki." with value "Hi Richard, Thank you a lot for making the first comment to Semantic Nodix! :) About your thoughtful points: I don't like to use content negotiation in order to get the right resource (or rather, representation of a resource, which itself is a resource again). I prefer getting explicitly the resource I asked for, and I feel like that's why URLs are there for: to locate one specific resource. That's why I try to avoid that way. Anonymous nodes. My only reason against them is that they are not referenceable. You say, most of the time that's ok - I'd claim, well, most of the time you can't know if maybe someone will want to reference it in the future. Why making it impossible? Actually making URIs is very cheap (well, making good URIs isn't, but that's the point of this blogging series), so why not give a reference to every node? The web grew the way it did because we did not claim beforehand to know which resources need to be adressible and which not. It would be a totally different web today if the majority of resource out there were not adressable. Your last point was answered in the blog and comments of the previous part. Thanks on your comments, denny". Since there have been only a few results, also nearby values are displayed.

Showing below up to 2 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

    • What's in a name - Part 4 Comment 2  + (Hi Richard, Thank you a lot for making thHi Richard, Thank you a lot for making the first comment to Semantic Nodix! :) About your thoughtful points: I don't like to use content negotiation in order to get the right resource (or rather, representation of a resource, which itself is a resource again). I prefer getting explicitly the resource I asked for, and I feel like that's why URLs are there for: to locate one specific resource. That's why I try to avoid that way. Anonymous nodes. My only reason against them is that they are not referenceable. You say, most of the time that's ok - I'd claim, well, most of the time you can't know if maybe someone will want to reference it in the future. Why making it impossible? Actually making URIs is very cheap (well, making good URIs isn't, but that's the point of this blogging series), so why not give a reference to every node? The web grew the way it did because we did not claim beforehand to know which resources need to be adressible and which not. It would be a totally different web today if the majority of resource out there were not adressable. Your last point was answered in the blog and comments of the previous part. Thanks on your comments, dennyious part. Thanks on your comments, denny)