Dear All
Firstly, apologies for cross posting.
A PhD studentship is available at ENS Mines Saint-Étienne.
He/she will be supervised by Professor Flavien Balbo and assistant
Professor Antoine Zimmermann (ISCOD team, iscod.emse.fr).
Scientific context:
Intelligent transportation systems
Hi Markus,
How about this:
/markus/friends/ rdfs:subClassOf schema:Person .
/alice a /markus/friends/ .
/markus schema:knows /alice .
Vuk Milicic
@faviki
On 24 Mar 2014, at 16:24, Markus Lanthaler markus.lantha...@gmx.net wrote:
Hi all,
We have an interesting discussion in the Hydra W3C
Vuk,
If URIs like /alice identify documents, then your example treats
documents as persons. In other words, you conflate information resources
and real-world resources.
Martynas
graphityhq.com
On Mar 25, 2014 11:35 AM, Vuk Milicic vuk.mili...@eurecom.fr wrote:
Hi Markus,
How about this:
Martynas,
From Markus' example I understood that /markus and /alice are instances of
schema:Person (/markus a schema:Person; schema:knows /alice...), thus
identifying people, not documents.
Vuk Milicic
@faviki
On 25 Mar 2014, at 14:10, Martynas Jusevičius marty...@graphity.org wrote:
Vuk,
On Monday, March 24, 2014 6:49 PM, Vuk Milicic wrote:
Hi Markus,
How about this:
/markus/friends/ rdfs:subClassOf schema:Person .
This would imply that /markus/friends is a schema:Person, which it is not.
It is a collection keeping references to persons.
/alice a /markus/friends/ .
On Tuesday, March 25, 2014 2:11 PM, Martynas Jusevičius wrote:
Vuk,
If URIs like /alice identify documents, then your example
treats documents as persons. In other words, you conflate
information resources and real-world resources.
Martynas, while this might be true, it doesn't really matter
+cc public-lod and public-hydra which you've removed Michael
On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
Would it be correct to summarize your question as, how do we enable
mechanical features like addressability and pagination to a value
collection in a way that doesn't
I find that so awkward since :knows is already a repeated property. Now we
have denormalized semantics and queries have to look at both properties...
and the only gain is the metadata about pagination. That's why I prefer an
orthogonal mechanism like knows/collection for just the metadata.
On
Hi,
Just thinking out loud here,
On Tue, Mar 25, 2014 at 4:57 PM, Markus Lanthaler
markus.lantha...@gmx.netwrote:
+cc public-lod and public-hydra which you've removed Michael
On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
Would it be correct to summarize your question as, how
10th International Conference on Semantic Systems
Leipzig, Germany September 4-5, 2014
http://www.semantics.cc
Important Dates (Research Application)
Abstract Submission Deadline: May 23, 2014
Paper Submission Deadline: May 30, 2014
Notification of Acceptance:
On Tuesday, March 25, 2014 5:00 PM, Pat Hayes wrote:
Seems to me that the, um, mistake that is made here is to use the same
property schema:knows for both the individual case and the list case.
Exactly.. it is especially problematic if rdfs:range is involved.
Why not invent a new property
On Tuesday, March 25, 2014 5:08 PM, Jason Douglas wrote:
I find that so awkward since :knows is already a repeated property.
Now we have denormalized semantics and queries have to look at both
properties... and the only gain is the metadata about pagination.
That's why I prefer an orthogonal
On Tue Mar 25 2014 at 9:36:21 AM, Markus Lanthaler markus.lantha...@gmx.net
wrote:
On Tuesday, March 25, 2014 5:08 PM, Jason Douglas wrote:
I find that so awkward since :knows is already a repeated property.
Now we have denormalized semantics and queries have to look at both
properties...
Let's see if I have this right.
You are encountering a situation where thenumber of people Markus knows is too
big (somehow). The proposed solution is to move this information to a
separate location. I don't see how this helps in reducing the size of the
information, which was the initial
Dear All,
We would like to invite submissions of late breaking research and
implementation news around ontologies as demos and posters. We encourage
submission from those working in both public and private sector, academic
and industrial, research and applied work and from across all fields
On 25 Mar 2014, at 16:48, Markus Lanthaler markus.lantha...@gmx.net wrote:
On Monday, March 24, 2014 6:49 PM, Vuk Milicic wrote:
Hi Markus,
How about this:
/markus/friends/ rdfs:subClassOf schema:Person .
This would imply that /markus/friends is a schema:Person, which it is not.
It
On Tuesday, March 25, 2014 5:49 PM, Peter F. Patel-Schneider wrote:
Let's see if I have this right.
You are encountering a situation where thenumber of people Markus knows
is too big (somehow). The proposed solution is to move this information
to a separate location. I don't see how this
Hi Peter,
On Mar 25, 2014, at 9:49 AM, Peter F. Patel-Schneider pfpschnei...@gmail.com
wrote:
Let's see if I have this right.
You are encountering a situation where thenumber of people Markus knows is
too big (somehow). The proposed solution is to move this information to a
separate
On 03/25/2014 10:40 AM, Markus Lanthaler wrote:
On Tuesday, March 25, 2014 5:49 PM, Peter F. Patel-Schneider wrote:
Let's see if I have this right.
You are encountering a situation where thenumber of people Markus knows
is too big (somehow). The proposed solution is to move this information
Hi Niklas,
On Tuesday, March 25, 2014 5:21 PM, Niklas Lindström wrote:
On Tue, Mar 25, 2014 at 4:57 PM, Markus Lanthaler wrote:
On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
Would it be correct to summarize your question as, how do we enable
mechanical features like
On Tuesday, March 25, 2014 5:44 PM, Jason Douglas wrote:
On Tue Mar 25 2014 at 9:36:21 AM, Markus Lanthaler wrote:
On Tuesday, March 25, 2014 5:08 PM, Jason Douglas wrote:
I find that so awkward since :knows is already a repeated property.
Now we have denormalized semantics and queries
On 03/24/2014 08:24 AM, Markus Lanthaler wrote:
Hi all,
[snip]
Thanks,
Markus
P.S.: I'm aware of how LDP handles this issue, but, while I generally like
the approach it takes, I don't like that fact that it imposes a specific
interaction model.
So LDP handles this issue, and is going
Well-summarized, Gregg.
On Tue Mar 25 2014 at 10:46:43 AM, Gregg Kellogg gr...@greggkellogg.net
wrote:
Hi Peter,
On Mar 25, 2014, at 9:49 AM, Peter F. Patel-Schneider
pfpschnei...@gmail.com wrote:
Let's see if I have this right.
You are encountering a situation where thenumber of
On Tuesday, March 25, 2014 7:04 PM, Peter F. Patel-Schneider wrote:
On 03/24/2014 08:24 AM, Markus Lanthaler wrote:
Hi all,
[snip]
Thanks,
Markus
P.S.: I'm aware of how LDP handles this issue, but, while I generally
like the approach it takes, I don't like that fact that it
Hi Markus,
On Tue, Mar 25, 2014 at 6:58 PM, Markus Lanthaler
markus.lantha...@gmx.netwrote:
Hi Niklas,
On Tuesday, March 25, 2014 5:21 PM, Niklas Lindström wrote:
On Tue, Mar 25, 2014 at 4:57 PM, Markus Lanthaler wrote:
On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
On 03/25/2014 11:21 AM, Markus Lanthaler wrote:
On Tuesday, March 25, 2014 7:04 PM, Peter F. Patel-Schneider wrote:
On 03/24/2014 08:24 AM, Markus Lanthaler wrote:
Hi all,
[snip]
Thanks,
Markus
P.S.: I'm aware of how LDP handles this issue, but, while I generally
like the approach it
On Mar 25, 2014, at 11:05 AM, Jason Douglas jasondoug...@google.com wrote:
Well-summarized, Gregg.
On Tue Mar 25 2014 at 10:46:43 AM, Gregg Kellogg gr...@greggkellogg.net
wrote:
Hi Peter,
On Mar 25, 2014, at 9:49 AM, Peter F. Patel-Schneider
pfpschnei...@gmail.com wrote:
Let's see
Markus,
OK.. this is quite similar to what we discussed in the Hydra CG (and what
LDP does):
/markus a schema:Person ;
/markus/friends/:manages [
:subject /markus ;
:property schema:knows
] ;
The thing I don't really like with these approaches is that you have
** apologies for cross-posting **
Open Position
Research Assistant –UI/ UX Developer for Life Sciences and Semantic Web
INSIGHT at NUI Galway (formerly DERI Galway)
In collaboration with our industrial partners, the successful applicant will
play a key role working for projects in the
29 matches
Mail list logo
