Fwd: Tabulator issue

FYI: Reply from David Sheets about viewing WP SIOC data in Tabulator.

---------- Forwarded message ----------
From: David Sheets
Date: Aug 16, 2006 6:25 PM
Subject: Re: Tabulator issue
To: Uldis Bojars

Hi Uldis,

The first point you bring up is a design feature. Resource [1] does
not contain any triples describing itself and thus we can make no
statements about it when you load it into the tabulator. We do provide
a convenience, however, in the form of triples describing what classes
a resource mentions. In this way, you can navigate down from your
resource to the data that it contains but that may not necessarily be
about itself.

The two instance adding bug was resolved. See [2].

I'm not sure I understand or can replicate your third bug but I can
say that double-clicking has the special meaning of 'refocus' in the
outliner context. Try single clicking or giving us instructions so we
can replicate it.

Thank you very much for using the Tabulator. We will be releasing 0.8
soon. If you have any more questions or bug reports, please don't
hesitate to contact me, tabulator@csail.mit.edu, or our issue tracker
at [3].

Thank you,

David Sheets

[1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
[2] http://dig.csail.mit.edu/issues/tabulator/issue22
[3] http://dig.csail.mit.edu/issues/tabulator/

On 8/16/06, Uldis Bojars wrote:
> Hi David,
>
> Found this issue when trying out the Tabulator.
>
> When loading RDF data [1] from a blog the Tabulator behaves quite strange:
> - it only shows information about the class (Post) mentioned in RDF,
> but does not display the RDF instance data.
> - it adds 2 instances of this RDF data when asked to add to the outliner
> - after expanding the content once (and showing only reference to a
> Post class) it does not react to next requests to expand this item. if
> double-clicking on the triangle that'd expand the item, it just adds
> another copy of the same URL to the source list.
>
> For some more test data you can look at [2] and [3].
>
> [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
>
> [2] http://esw.w3.org/topic/SIOC/EnabledSites
> [3] http://www.geospatialsemanticweb.com/index.php?sioc_type=post&sioc_id=108
>
> Tried this with Tabulator 0.7 in Firefox.
> Also tried the same with the development version of Tabulator, but
> that did not help.
>
> Could you please let me know what is wrong?
>
> Best,
> Uldis
>
> [ http://captsolo.net/info/ ]
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev
-~----------~----~----~----~------~----~------~--~---

Fwd: Tabulator issue

Implementation suggestion:

See the "Design feature" part of David's mail. Here is what we should
add to each SIOC document to describe what it is about and as a
consequence have show up in the Tabulator:



Insert the URI of a resource this page is about in "URI".

Another interesting thing to do would be if we could assign a type of
document to foaf:Document(s). By default it just means any document
(not necessarily FOAF). This is not necessary to solve the issue
mentioned above but might have interesting uses (e.g., to write rules
that determine a type of a document).

Uldis

[ http://captsolo.net/info/ ]

> ---------- Forwarded message ----------
> From: David Sheets
> Date: Aug 16, 2006 6:25 PM
> Subject: Re: Tabulator issue
> To: Uldis Bojars
>
>
> Hi Uldis,
>
> The first point you bring up is a design feature. Resource [1] does
> not contain any triples describing itself and thus we can make no
> statements about it when you load it into the tabulator. We do provide
> a convenience, however, in the form of triples describing what classes
> a resource mentions. In this way, you can navigate down from your
> resource to the data that it contains but that may not necessarily be
> about itself.
>
> The two instance adding bug was resolved. See [2].
>
> I'm not sure I understand or can replicate your third bug but I can
> say that double-clicking has the special meaning of 'refocus' in the
> outliner context. Try single clicking or giving us instructions so we
> can replicate it.
>
> Thank you very much for using the Tabulator. We will be releasing 0.8
> soon. If you have any more questions or bug reports, please don't
> hesitate to contact me, tabulator@csail.mit.edu, or our issue tracker
> at [3].
>
> Thank you,
>
> David Sheets
>
> [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> [2] http://dig.csail.mit.edu/issues/tabulator/issue22
> [3] http://dig.csail.mit.edu/issues/tabulator/
>
> On 8/16/06, Uldis Bojars wrote:
> > Hi David,
> >
> > Found this issue when trying out the Tabulator.
> >
> > When loading RDF data [1] from a blog the Tabulator behaves quite strange:
> > - it only shows information about the class (Post) mentioned in RDF,
> > but does not display the RDF instance data.
> > - it adds 2 instances of this RDF data when asked to add to the outliner
> > - after expanding the content once (and showing only reference to a
> > Post class) it does not react to next requests to expand this item. if
> > double-clicking on the triangle that'd expand the item, it just adds
> > another copy of the same URL to the source list.
> >
> > For some more test data you can look at [2] and [3].
> >
> > [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> >
> > [2] http://esw.w3.org/topic/SIOC/EnabledSites
> > [3] http://www.geospatialsemanticweb.com/index.php?sioc_type=post&sioc_id=108
> >
> > Tried this with Tabulator 0.7 in Firefox.
> > Also tried the same with the development version of Tabulator, but
> > that did not help.
> >
> > Could you please let me know what is wrong?
> >
> > Best,
> > Uldis
> >
> > [ http://captsolo.net/info/ ]
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev
-~----------~----~----~----~------~----~------~--~---

Fwd: Tabulator issue

Brief question: what if the document in question is about multiple
subjects (topics)?
Just curious.
Thanks
Jack

On 8/21/06, Uldis Bojars wrote:
>
> Implementation suggestion:
>
> See the "Design feature" part of David's mail. Here is what we should
> add to each SIOC document to describe what it is about and as a
> consequence have show up in the Tabulator:
>
>
>
>

>
> Insert the URI of a resource this page is about in "URI".
>
> Another interesting thing to do would be if we could assign a type of
> document to foaf:Document(s). By default it just means any document
> (not necessarily FOAF). This is not necessary to solve the issue
> mentioned above but might have interesting uses (e.g., to write rules
> that determine a type of a document).
>
> Uldis
>
> [ http://captsolo.net/info/ ]
>
>
> > ---------- Forwarded message ----------
> > From: David Sheets
> > Date: Aug 16, 2006 6:25 PM
> > Subject: Re: Tabulator issue
> > To: Uldis Bojars
> >
> >
> > Hi Uldis,
> >
> > The first point you bring up is a design feature. Resource [1] does
> > not contain any triples describing itself and thus we can make no
> > statements about it when you load it into the tabulator. We do provide
> > a convenience, however, in the form of triples describing what classes
> > a resource mentions. In this way, you can navigate down from your
> > resource to the data that it contains but that may not necessarily be
> > about itself.
> >
> > The two instance adding bug was resolved. See [2].
> >
> > I'm not sure I understand or can replicate your third bug but I can
> > say that double-clicking has the special meaning of 'refocus' in the
> > outliner context. Try single clicking or giving us instructions so we
> > can replicate it.
> >
> > Thank you very much for using the Tabulator. We will be releasing 0.8
> > soon. If you have any more questions or bug reports, please don't
> > hesitate to contact me, tabulator@csail.mit.edu, or our issue tracker
> > at [3].
> >
> > Thank you,
> >
> > David Sheets
> >
> > [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> > [2] http://dig.csail.mit.edu/issues/tabulator/issue22
> > [3] http://dig.csail.mit.edu/issues/tabulator/
> >
> > On 8/16/06, Uldis Bojars wrote:
> > > Hi David,
> > >
> > > Found this issue when trying out the Tabulator.
> > >
> > > When loading RDF data [1] from a blog the Tabulator behaves quite strange:
> > > - it only shows information about the class (Post) mentioned in RDF,
> > > but does not display the RDF instance data.
> > > - it adds 2 instances of this RDF data when asked to add to the outliner
> > > - after expanding the content once (and showing only reference to a
> > > Post class) it does not react to next requests to expand this item. if
> > > double-clicking on the triangle that'd expand the item, it just adds
> > > another copy of the same URL to the source list.
> > >
> > > For some more test data you can look at [2] and [3].
> > >
> > > [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> > >
> > > [2] http://esw.w3.org/topic/SIOC/EnabledSites
> > > [3] http://www.geospatialsemanticweb.com/index.php?sioc_type=post&sioc_id=108
> > >
> > > Tried this with Tabulator 0.7 in Firefox.
> > > Also tried the same with the development version of Tabulator, but
> > > that did not help.
> > >
> > > Could you please let me know what is wrong?
> > >
> > > Best,
> > > Uldis
> > >
> > > [ http://captsolo.net/info/ ]
> > >
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev
-~----------~----~----~----~------~----~------~--~---

Fwd: Tabulator issue

Hi Jack,

In SIOC documents as generated by, e.g. a WordPress SIOC exporter,
there would usually be a main SIOC concept - a primary topic - that
others are related to.

When there are multiple topics (and hence there is no single primary
topic) you could use a foaf:topic [1]. Compare its definition with that
of a foaf:primaryTopic [2].

[1] http://xmlns.com/foaf/0.1/#term_topic
[2] http://xmlns.com/foaf/0.1/#term_primaryTopic

Best,
Uldis

[ http://captsolo.net/info/ ]

Jack Park wrote:
> Brief question: what if the document in question is about multiple
> subjects (topics)?
> Just curious.
> Thanks
> Jack
>
> On 8/21/06, Uldis Bojars wrote:
> >
> > Implementation suggestion:
> >
> > See the "Design feature" part of David's mail. Here is what we should
> > add to each SIOC document to describe what it is about and as a
> > consequence have show up in the Tabulator:
> >
> >
> >
> >

> >
> > Insert the URI of a resource this page is about in "URI".
> >
> > Another interesting thing to do would be if we could assign a type of
> > document to foaf:Document(s). By default it just means any document
> > (not necessarily FOAF). This is not necessary to solve the issue
> > mentioned above but might have interesting uses (e.g., to write rules
> > that determine a type of a document).
> >
> > Uldis
> >
> > [ http://captsolo.net/info/ ]
> >
> >
> > > ---------- Forwarded message ----------
> > > From: David Sheets
> > > Date: Aug 16, 2006 6:25 PM
> > > Subject: Re: Tabulator issue
> > > To: Uldis Bojars
> > >
> > >
> > > Hi Uldis,
> > >
> > > The first point you bring up is a design feature. Resource [1] does
> > > not contain any triples describing itself and thus we can make no
> > > statements about it when you load it into the tabulator. We do provide
> > > a convenience, however, in the form of triples describing what classes
> > > a resource mentions. In this way, you can navigate down from your
> > > resource to the data that it contains but that may not necessarily be
> > > about itself.
> > >
> > > The two instance adding bug was resolved. See [2].
> > >
> > > I'm not sure I understand or can replicate your third bug but I can
> > > say that double-clicking has the special meaning of 'refocus' in the
> > > outliner context. Try single clicking or giving us instructions so we
> > > can replicate it.
> > >
> > > Thank you very much for using the Tabulator. We will be releasing 0.8
> > > soon. If you have any more questions or bug reports, please don't
> > > hesitate to contact me, tabulator@csail.mit.edu, or our issue tracker
> > > at [3].
> > >
> > > Thank you,
> > >
> > > David Sheets
> > >
> > > [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> > > [2] http://dig.csail.mit.edu/issues/tabulator/issue22
> > > [3] http://dig.csail.mit.edu/issues/tabulator/
> > >
> > > On 8/16/06, Uldis Bojars wrote:
> > > > Hi David,
> > > >
> > > > Found this issue when trying out the Tabulator.
> > > >
> > > > When loading RDF data [1] from a blog the Tabulator behaves quite strange:
> > > > - it only shows information about the class (Post) mentioned in RDF,
> > > > but does not display the RDF instance data.
> > > > - it adds 2 instances of this RDF data when asked to add to the outliner
> > > > - after expanding the content once (and showing only reference to a
> > > > Post class) it does not react to next requests to expand this item. if
> > > > double-clicking on the triangle that'd expand the item, it just adds
> > > > another copy of the same URL to the source list.
> > > >
> > > > For some more test data you can look at [2] and [3].
> > > >
> > > > [1] http://b4mad.net/datenbrei/index.php?sioc_type=post&sioc_id=329
> > > >
> > > > [2] http://esw.w3.org/topic/SIOC/EnabledSites
> > > > [3] http://www.geospatialsemanticweb.com/index.php?sioc_type=post&sioc_id=108
> > > >
> > > > Tried this with Tabulator 0.7 in Firefox.
> > > > Also tried the same with the development version of Tabulator, but
> > > > that did not help.
> > > >
> > > > Could you please let me know what is wrong?
> > > >
> > > > Best,
> > > > Uldis
> > > >
> > > > [ http://captsolo.net/info/ ]
> > > >
> >
> >
> > >
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev
-~----------~----~----~----~------~----~------~--~---

sioc:Post, sioc:Container and baetle:Issue

A baetle:Issue is really very close to a awol:feed or a
sioc:Container. It has a title, a summary, and contains a number of
Posts [1]. One can easily imagine subscribing to a feed on an issue.

So this seems to suggest that a baetle:Issue could also be a
sioc:Container. I am not sure that makes sense as I have it
currently, since I also have a baetle:Issue be a subclass of a
wf:Task [2]. Any ideas how the two should be related?

Should a issue be a container that is related to a task?

Is a issuezilla instance a sioc:Forum ?

Any intuitions in the sioc community about this?

Henry

[1] Here is a good example
http://www.netbeans.org/issues/show_bug.cgi?id=14731
[2] see new UML here:
http://code.google.com/p/baetle/

Home page: http://bblfish.net/
Sun Blog: http://blogs.sun.com/bblfish/
Foaf name: http://bblfish.net/people/henry/card#me

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

foaf:Person, sioc:User, sioc:Role, doap:Project and baetle:Issu

In baetle we are using a number of ontologies [1] of which sioc, doap
and foaf.

In the current ontology I have started linking baetle:Issue(s) to
sioc:User(s) thinking it makes sense to reduce the need for user
identification. A sioc:User is a subclass of foaf:OnlineAccount, so
both of these are quite clearly distinct from foaf:Persons [2].

On the other hand doap:Projects are related to foaf:Person(s) via
the relationship doap:documenter, doap:maintainer, ...

So if I create links from baetle:Issue to sioc:User(s) will I have to
create a blank node to link doap:Projects to sioc:Users?

a doap:Project;
:developer [ a foaf:Person;
foaf:holdsAccount henry.story/>
]
.

I don't have any problem giving my foaf url (see my sig), but for
most people in say the NetBeans project we would only want to publish
account handles.

Interestingly enough sioc does have a notion of roles, as a class of
objects, instead of role relations between a foaf:Project and a
doap:Project, so one could fit in those roles, by creating subclass
relations for . Would it make sense to have doap URLs for Developer,
Translator, ... ?
They could be used like this:


sioc:has_function [ a doapx:Developer;
sioc:has_scope p/baetle/> ],
[ a doapx:Maintainer;
sioc:has_scope http://code.google.com/p/
baetle/>],
[ a doapx:Documenter;
sioc:has_scope http://code.google.com/p/
baetle/>] .

To remove the blank nodes each project would have its roles urls,
perhaps like this:

a doapx:Developer;
sioc:scope_of .

a doapx:Maintainer;
sioc:scope_of .

a doapx:Documenter;
sioc:scope_of .

And so my functions could be described like this

a sioc:User;
sioc:has_function roles#Developer>,
roles#Maintainer>,
roles#Documenter> .

So one could define the relationships between these like this in N3:

{ ?proj a doap:Project;
doap:developer ?p . }
<=>
{ ?p foaf:holdsAccount [ sioc:has_function ?devel ] .
?devel a sioc:Role, doapx:Developer;
sioc:scope_of ?proj . }

Btw, since mapping between ontologies can often be more complex than
what is expressible in OWL, I suggest they be written out in N3.
There may not be a lot of software around to read them, but I think
it helps make discussions a lot clearer. The decisions can be kept,
and later when a standard rule language emerges easily converted to
that language.

Henry

[1] http://code.google.com/p/baetle/
[2] Even if the comment on the sioc:last_name relation is somewhat
misleading

sioc:last_name a owl:DatatypeProperty,
owl:DeprecatedProperty;
:comment "Last (real) name of this user. Synonyms include
surname or family name.";
:domain sioc:User;
:isDefinedBy sioc:;
owl:versionInfo "This property is deprecated. Use foaf:name
or foaf:surname instead." .

How can one use foaf:surname on an account?

Home page: http://bblfish.net/
Sun Blog: http://blogs.sun.com/bblfish/
Foaf name: http://bblfish.net/people/henry/card#me

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---