- From: carmen r <_@whats-your.name>
- Date: 2008年8月15日 00:35:11 -0400
- To: semantic-web@w3c.org
- Message-ID: <20080815043511.GA27733@m.hsd1.ma.comcast.net>
> All I ask of you is the exposure of the Freebase URLs that are already in
> sight re. the current / basic Freebase pages. "javascript:{}" is neither
> URL nor URI.
Brendan disagrees, at least:
"They were a deliberate feature in this sense: I invented the javascript: URL along with JavaScript in 1995, and intended that javascript: URLs could be used as any other kind of URL, including being bookmark-able."
[1] wikipedia:bookmarklet
i'd agree javascript:{} is uninformative
how about some MQL JSON in there?
freebase:{} would be preferable, as well
the useragent can provide the context so such URIs do something useful
also GUIDs make baby jesus cry
>
> <<
> The ?people operated? side of things is the world we live in today. As
> David Huynh?s video discusses, we busy ourselves manually searching by
> keyword in multiple locations and then compile our results.
> >>
>
> Yes, we may be "less busy" as a result of nice UI (visualization or
> interaction) but the ultimate goal is stimulation of our inherent cognitive
> prowess. Thus, also offer users of these UIs an optional route to the raw
> data. On the Web that's simply about URIs or URLs. A stimulated human is an
> inquisitive human, and an inquisitive human will ultimately seek to explore
> dimensions associated with observation, perception, and comprehension.
>
>> (the talkback comments are also valuable)
> Can't comment on zdnet as they still require completion of a full
> subscription interview first, no OpenID or the like in sight :-(
>
>>
>> http://www.readwriteweb.com/archives/freebase_parallax_taunts_us_wi.php
> No comment, I think that article speaks for itself. From my vantage point,
> readwriteweb is still grappling with the fundamentals of what comes after
> REST APIs.
>
>>
>>
>> http://blog.futurefacts.net/2008/08/14/future-web-freebase-%E2%80%93-killing-google-with-semantic-precision/
> That article is another variant of the readwrite article re. overall
> comprehension.
>
> None of them answered the question re. Linked or Semantic Web relevance,
> because none of them seem to understand the essence of either. For
> instance, they don't see how "Networking" is the constant while points of
> reference (network entry points) vary over time; we started with Routers
> (eons ago) and now we are dealing with Entities across Data Spaces [1][2].
>>
>> Those are their opinions alone. I include them here to provide various
>> perspectives.
>
> Here is my basic opinion:
>
> I don't have an issue with the UI, it's nice, cool, and innovative. I just
> want it to be part of the Web. Being part of the Web is about accepting
> that "Linkage" is sacrosanct. Thus, no silos, no matter how pretty, cool,
> or innovative.
>
> Your visualization is how I would lead a user to a beachead point in the
> underlying graph so that they could beam a SPARQL + Full Text pattern query
> down the graph without them ever writing or seeing a line of SPARQL.
>
> Question: Is there any fundamental reason why you cannot expose URIs or
> URLs where you have "javascript:{}"? Would this break your work in anyway?
> If you expose the URIs, I would then be able to demonstrate what I mean
> using your nice UI, how about that?
>
> Links:
>
> 1.
> http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html#(15)
> -- Start
> 2.
> http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html#(22)
> -- Where we are headed
>
> Note:
> The presentation above is a remix of presentations by TimBL and I from the
> recent Linked Data Planet conference. You've forced my hand re. publication
> as this remix is also about demonstrating RDFa virtues amongst other things
> re. the Linked Data Web :-)
>
>>
>> Best,
>>
>> David
>>
>>
>
>
> --
>
>
> Regards,
>
> Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen
> President & CEO OpenLink Software Web: http://www.openlinksw.com
>
>
>
>
Received on Friday, 15 August 2008 04:36:01 UTC