W3C home > Mailing lists > Public > semantic-web@w3.org > January 2006

Re: Announcement: Firefox Navibar Extension 0.10

From: <siebeneicher@oaklett.org>
Date: Thu, 12 Jan 2006 06:40:01 +0100
Message-ID: <43C5EBB1.2010608@oaklett.org>
To: Reto Bachmann-Gmür <reto@gmuer.ch>
CC: semantic-web@w3.org

>> During the design phase of the NNS Sitemap i decide to use a simple 
>> and "flat" tree representation only for practical reasons. I also 
>> thought of a navigation tool going a more semantic way. But hey... 
>> what damn does the "semantic way" mean? Today, i think this way is 
>> when users ask the internet a clever question and get a clever answer.
> Imho, things that are not the semantic web way in 
> http://navibar.oaklett.org/sitemap.rdf are:
> - Lack of type for the classes
> - Use of rdf:Seq which makes aggregation harder than with 
> parseType="Collection"
> - Using plain-literal URIs while in fact the named-resource is meant
> - Unnecessary naming of resources with URNs
> In my example:
> - The resources have a type (SiteMapEntry, but would probably better be 
> "NavigationEntry")
> - Instead of "identifier" a "page" property points to the page (which is 
> a resource)
> - parseType="Collection" instead of Seq
> - rdfs:label / dc:title: question of taste I guess, could live with 
> dc:title ;-)
> Like your vocabulary it supports an arbitrary graph-structures including 
> circles, and I don't think that it would be any harder to use for an 
> application like the current version of navibar, but more likely to be 
> of use for more generic aggregators.

This makes sense.

I would also extend the current Sitemap with the functionality to
include external resources, for example other Sitemaps or RSS files or
other interesting sources.

    <rdfs:label>Flight - Asylum - Integration</rdfs:label>
    <page rdf:resource="http://www.osar.ch/education" />
    <children rdf:parseType="Collection"
rdfs:seeAlso="http://www.osar.ch/eductation-sitemap" />

But i am not sure if rdfs:seeAlso is the right one for this purpose.

By the way, i plan for the next major release of Navibar, to make the
root elements of the tree general folders like: Sitemap, RSS, Links and
behind these root elements will follow the navigation elements of each
own format.

> Another use-case, where aggregability and graph structure become 
> important would be a tool (navibar 2 ?) to visualize an navigate through 
> a blog-discussion on multiple servers.

I like the use-case because of its website overlapping nature. How would 
you visualize the discussion and what source, exactly what markup do 
want to use? How concerns this to Navibar?

Received on Thursday, 12 January 2006 05:40:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:55 UTC