Dr. Francis MUGUET | 12 Sep 03:37 2009
Picon
Picon

Re: Call for Tutorials - Fourth Asian Semantic Web Conference (ASWC 2009)


Sorry for this late annoucement






Opening the Namespace infrastructures to Competition
Open Questions : challenges and opportunities

Expert Workshop
http://net4d.org/18sep09-index.html

The current situation concerning the Domain Name System is raising more and more interest as the end of the ICANN JPA in September is approaching.

Instead of engaging into bitter debates on how to co-manage a quasi-monopoly, an informal workshop is organized to explore whether there are any technical alternatives for the development of future information networks ?. Is there an effective solution to open to competition name resolving services. ?

This informal workshop is organized in the context of the expert mission that has been recently contracted by ITU to Dr. Francis Muguet. after his presentation, last May, at the WSIS Forum : Opening to competition the namespace infrastructure

This expert mission is in line with the outcomes of the last ITU Council Working Group on WSIS , where ITU was requested to study the evolution of the future internet.
The informal expert workshop is hosted at ITU headquarters, on Friday 18 September, which happens to occur after the European Dialogue on Internet Governance ( Monday 14 - Tuesday. 15 September ) and the IGF planning meeting ( Wednesday 16- Thursday 17 September ) in Geneva

The workshop, organized by Dr. Francis Muguet, is going to include in the morning, presentations and a round table, and in the afternoon, open discussions.



  I proposed to implement classes, called semantic classes , where the legal and technological innovation lies in the fact that owners of domain names in TLDs in  those classes  are contractually obliged to follow the ontology specific to each TLD. ,  (SWTLD).
( or to lose their domain names.)
 It would be therefore possible to create semantic namespaces as zones where metadata may be trusted.

   it would be possible to implement semantic namespaces in a way independant from ICANN, 

As a consequence, it would, allow for far more relevant access to data than in full text and
 this would redefine the search engines' market and approach.
Each of those SWTLDs could constitute a very large open database and would empower M2M.

Logically it would seem that W3C shoud be entittled to co-manage  at least a few  of those semantic namespaces,
This would provide, by the way, some financial ressources for the W3C.

All the best

Francis Muguet





( WE APOLOGIZE IF YOU RECEIVE MULTIPLE COPIES OF THIS MESSAGE ) Call for Tutorials Fourth Asian Semantic Web Conference (ASWC 2009) 6-9 December, 2009 Shanghai, China http://www.aswc2009.org/


-- ------------------------------------------------------ Francis F. Ph.D MUGUET KNIS/ENSTA "Réseaux de la Connaissance et Société de l'Information" "Knowledge Networks & Information Society" (KNIS) ENSTA/KNIS http://knis.org 32 Blvd Victor 75739 PARIS cedex FRANCE Phone: (33)1 45 52 60 19 Fax: (33)1 45 52 52 82 muguet-6ow3RgI0P2c@public.gmane.org http://www.ensta.fr/~muguet Mobile France +33 6 71 91 42 10 Switzerland +41 78 927 06 97 Cameroun +237 96 55 69 62 ( mostly in July ) NET4D : http://www.net4D.org MDPI Foundation Open Access Journals http://www.mdpi.org http://www.mdpi.net muguet-bHvVSWwc4ag@public.gmane.org muguet-l5oiX7ktVs0@public.gmane.org World Summit On the Information Society (WSIS) Civil Society Working Groups Scientific Information : http://www.wsis-si.org chair Patents & Copyrights : http://www.wsis-pct.org co-chair Financing Mechanismns : http://www.wsis-finance.org web Info. Net. Govermance : http://www.wsis-gov.org web UNMSP : http://www.unmsp.org WTIS : http://www.wtis.org REUSSI : http://www.reussi.org ------------------------------------------------------
Tomás Vírseda | 12 Sep 23:50 2009
Picon

pimo:Tag vs nao:Tag

Hi,

I'm confused about pimo:Tag and nao:Tag classes described in their
respective ontology. Which is the difference between these two clases?
I'm reading the ontologies documentation but I can't still figure out
how they should be used. I'm developing a tagging system in a
application and I would like to use Nepomuk.

About pimo:Tag description:
"Tags in the context of PIMO. A marker class for Things that are used
to categorize documents (or other things). Tags must be a kind of
Thing and must have a unique label. Documents should not be Tags by
default."

About nao:Tag description:
"This class is useful for modelling conventional tagging practices.
The user can tag resources in conventional ways, automatically
creating an instance of this tag, which is then related to the
annotated resource via the nao:hasTag property. For more on tagging as
annotation see Section 2.3.". I've read this section and the
explanation is very convincing.

Thanks in advance.
Kind regards

--
Tomás Vírseda
Stéphane Laurière | 22 Sep 18:14 2009

Open World Forum 2009 - Open Semantic Desktop Conference

Hello everyone,

Mandriva is organizing a conference next week in Paris at the Open World
Forum 2009, October 1st 11am CEST, on the open semantic desktop:
http://openworldforum.org/program/envisioning-the-open-desktop-of-the-future

Envisioning the Open Semantic Desktop of the Future
====================================================
Semantic technologies are bringing a disruptive innovation to the
desktop: they empower the users to organize their work entirely around
the high-level concept of activities, giving birth to task oriented
desktops which are progressively reframing the desktop metaphor. The
semantic desktop vision is possibly one of the most important
breakthrough since the emergence of personal computing paradigm in the
early eighties. It paves the way for radically new ways in taming
information overload and in dealing with knowledge at the personal or at
the enterprise levels. This conference will present the latest
advancements of major open projects in this field and their future.

Semantic desktop history and future
-----------------------------------
Prof Stefan Decker, National University of Ireland

Zeitgeist: An event centric approach to the semantic desktop
-------------------------------------------------------------
Seif Lofty, Zeitgeist Founder, Alexander Gabriel, Information Technology
Graduated

The Scribo KDE task oriented desktop
--------------------------------------
Sebastian Trueg, Mandriva
====================================================

We hope to see you there!

Kind regards

Stéphane Laurière

--

-- 
Stéphane Laurière
Mandriva http://mandriva.com

Leo Sauermann | 25 Sep 18:30 2009
Picon

Re: [people] pimo:Tag vs nao:Tag

Hi,

as others may be interested in this discussion, I am also including xesam
(= the ontology developers list)

I was a bit slow to answer, sorry.

Tomás - what are you programming? do you have a url or a blogpost about 
your work?

nao:Tag is for systems that just use NAO/NIE and are fine with 
no-brainer solutions.
a nao:Tag has the semantic meaning of : the tag is a string. its unique.

pimo:Tag is for systems that want to achieve a highlevel integration of 
Addressbooks, Calendars, Websites, etc... into a semantic network. 
pimo:Tags are then not only tags, but can be also a pimo:Person - that 
is, you can use a person's name to tag something but - surprise - it is 
also a person.
now clicking on the person will get more...
a pimo:Tag has the semantic meaning of : the tag is a unique string 
which is also a Thing out of the real world which can have more attributes.

I also documented this here in the FAQ
https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebetweennao:Tagandpimo:Tag

best
Leo

It was Tomás Vírseda who said at the right time 12.09.2009 23:50 the 
following words:
> Hi,
>
> I'm confused about pimo:Tag and nao:Tag classes described in their
> respective ontology. Which is the difference between these two clases?
> I'm reading the ontologies documentation but I can't still figure out
> how they should be used. I'm developing a tagging system in a
> application and I would like to use Nepomuk.
>
> About pimo:Tag description:
> "Tags in the context of PIMO. A marker class for Things that are used
> to categorize documents (or other things). Tags must be a kind of
> Thing and must have a unique label. Documents should not be Tags by
> default."
>
> About nao:Tag description:
> "This class is useful for modelling conventional tagging practices.
> The user can tag resources in conventional ways, automatically
> creating an instance of this tag, which is then related to the
> annotated resource via the nao:hasTag property. For more on tagging as
> annotation see Section 2.3.". I've read this section and the
> explanation is very convincing.
>
> Thanks in advance.
> Kind regards
>
> --
> Tomás Vírseda
> _______________________________________________
> people mailing list
> people@...
> http://lists.semanticdesktop.org/mailman/listinfo/people
>
>   

-- 
_____________________________________________________
Dr. Leo Sauermann       http://www.dfki.de/~sauermann 

Deutsches Forschungszentrum fuer 
Kuenstliche Intelligenz DFKI GmbH
Trippstadter Strasse 122
P.O. Box 2080           Fon:   +43 6991 gnowsis
D-67663 Kaiserslautern  Fax:   +49 631 20575-102
Germany                 Mail:  leo.sauermann@...

Geschaeftsfuehrung:
Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
_____________________________________________________

Evgeny Egorochkin | 25 Sep 18:43 2009
Picon

Re: [people] pimo:Tag vs nao:Tag

Basically I think the biggest concern here is interoperability between nao:Tag 
and pimo:Tag.

How can applications that use nao:Tag and pimo:Tag "talk" to each other?

В сообщении от Пятница 25 сентября 2009 19:30:58 автор Leo Sauermann написал:
> as others may be interested in this discussion, I am also including xesam
> (= the ontology developers list)
> 
> I was a bit slow to answer, sorry.
> 
> Tomás - what are you programming? do you have a url or a blogpost about
> your work?
> 
> nao:Tag is for systems that just use NAO/NIE and are fine with
> no-brainer solutions.
> a nao:Tag has the semantic meaning of : the tag is a string. its unique.
> 
> pimo:Tag is for systems that want to achieve a highlevel integration of
> Addressbooks, Calendars, Websites, etc... into a semantic network.
> pimo:Tags are then not only tags, but can be also a pimo:Person - that
> is, you can use a person's name to tag something but - surprise - it is
> also a person.
> now clicking on the person will get more...
> a pimo:Tag has the semantic meaning of : the tag is a unique string
> which is also a Thing out of the real world which can have more attributes.
> 
> I also documented this here in the FAQ
> https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebe
> tweennao:Tagandpimo:Tag
> 
> best
> Leo
> 
> 
> 
> It was Tomás Vírseda who said at the right time 12.09.2009 23:50 the
> 
> following words:
> > Hi,
> >
> > I'm confused about pimo:Tag and nao:Tag classes described in their
> > respective ontology. Which is the difference between these two clases?
> > I'm reading the ontologies documentation but I can't still figure out
> > how they should be used. I'm developing a tagging system in a
> > application and I would like to use Nepomuk.
> >
> > About pimo:Tag description:
> > "Tags in the context of PIMO. A marker class for Things that are used
> > to categorize documents (or other things). Tags must be a kind of
> > Thing and must have a unique label. Documents should not be Tags by
> > default."
> >
> > About nao:Tag description:
> > "This class is useful for modelling conventional tagging practices.
> > The user can tag resources in conventional ways, automatically
> > creating an instance of this tag, which is then related to the
> > annotated resource via the nao:hasTag property. For more on tagging as
> > annotation see Section 2.3.". I've read this section and the
> > explanation is very convincing.
> >
> > Thanks in advance.
> > Kind regards
> >
> > --
> > Tomás Vírseda
> > _______________________________________________
> > people mailing list
> > people <at> semanticdesktop.org
> > http://lists.semanticdesktop.org/mailman/listinfo/people
> 
_______________________________________________
Xesam mailing list
Xesam <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xesam
Siegfried Handschuh | 25 Sep 18:48 2009

Re: (no subject)

Hi,

Actually the philosophy in NAO is a bit different. You can also do there 
an annotation of Addressbooks, Calendars, Websites etc. But you would 
indeed not use nao:Tag.

NAO has a set of relations you can use to annotate a resource with 
another resource. To annotate a resource with pimo:Person you could use, 
for example, nao:isRelated.

just my two cents.

cheers
Siggi

  wrote:
> Hi,
> 
> as others may be interested in this discussion, I am also including xesam
> (= the ontology developers list)
> 
> I was a bit slow to answer, sorry.
> 
> Tomás - what are you programming? do you have a url or a blogpost about 
> your work?
> 
> nao:Tag is for systems that just use NAO/NIE and are fine with 
> no-brainer solutions.
> a nao:Tag has the semantic meaning of : the tag is a string. its unique.
> 
> pimo:Tag is for systems that want to achieve a highlevel integration of 
> Addressbooks, Calendars, Websites, etc... into a semantic network. 
> pimo:Tags are then not only tags, but can be also a pimo:Person - that 
> is, you can use a person's name to tag something but - surprise - it is 
> also a person.
> now clicking on the person will get more...
> a pimo:Tag has the semantic meaning of : the tag is a unique string 
> which is also a Thing out of the real world which can have more attributes.
> 
> I also documented this here in the FAQ
> https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebetweennao:Tagandpimo:Tag
> 
> best
> Leo
> 
> 
> 
> It was Tomás Vírseda who said at the right time 12.09.2009 23:50 the 
> following words:
>> Hi,
>>
>> I'm confused about pimo:Tag and nao:Tag classes described in their
>> respective ontology. Which is the difference between these two clases?
>> I'm reading the ontologies documentation but I can't still figure out
>> how they should be used. I'm developing a tagging system in a
>> application and I would like to use Nepomuk.
>>
>> About pimo:Tag description:
>> "Tags in the context of PIMO. A marker class for Things that are used
>> to categorize documents (or other things). Tags must be a kind of
>> Thing and must have a unique label. Documents should not be Tags by
>> default."
>>
>> About nao:Tag description:
>> "This class is useful for modelling conventional tagging practices.
>> The user can tag resources in conventional ways, automatically
>> creating an instance of this tag, which is then related to the
>> annotated resource via the nao:hasTag property. For more on tagging as
>> annotation see Section 2.3.". I've read this section and the
>> explanation is very convincing.
>>
>> Thanks in advance.
>> Kind regards
>>
>> --
>> Tomás Vírseda
>> _______________________________________________
>> people mailing list
>> people@...
>> http://lists.semanticdesktop.org/mailman/listinfo/people
>>
>>   
> 
> 

--

-- 
Dr. Siegfried Handschuh
http://www.siegfried-handschuh.net/
+353 - 91 - 495085
Digital Enterprise Research Institute
    National University of Ireland, Galway.
Leo Sauermann | 25 Sep 19:07 2009
Picon

Re: [people] pimo:Tag vs nao:Tag

It was Evgeny Egorochkin who said at the right time 25.09.2009 18:43 the following words:
Basically I think the biggest concern here is interoperability between nao:Tag and pimo:Tag. How can applications that use nao:Tag and pimo:Tag "talk" to each other?
let the same instance be both a nao:tag and a pimo:Tag.

but our plan was:
* nao:Tag is piss-easy, we use it now to get KDE 4.0 off the ground (... this we said in ~Oct 2006)
* pimo:Tag is way cooler because your things in live are tags. We should update KDE for this (... uh....)

so, it will take some time to get there.

Sebastian Trüg actually worked on some ways to do this - I think.

did you?

best
Leo


В сообщении от Пятница 25 сентября 2009 19:30:58 автор Leo Sauermann написал:
as others may be interested in this discussion, I am also including xesam (= the ontology developers list) I was a bit slow to answer, sorry. Tomás - what are you programming? do you have a url or a blogpost about your work? nao:Tag is for systems that just use NAO/NIE and are fine with no-brainer solutions. a nao:Tag has the semantic meaning of : the tag is a string. its unique. pimo:Tag is for systems that want to achieve a highlevel integration of Addressbooks, Calendars, Websites, etc... into a semantic network. pimo:Tags are then not only tags, but can be also a pimo:Person - that is, you can use a person's name to tag something but - surprise - it is also a person. now clicking on the person will get more... a pimo:Tag has the semantic meaning of : the tag is a unique string which is also a Thing out of the real world which can have more attributes. I also documented this here in the FAQ https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebe tweennao:Tagandpimo:Tag best Leo It was Tomás Vírseda who said at the right time 12.09.2009 23:50 the following words:
Hi, I'm confused about pimo:Tag and nao:Tag classes described in their respective ontology. Which is the difference between these two clases? I'm reading the ontologies documentation but I can't still figure out how they should be used. I'm developing a tagging system in a application and I would like to use Nepomuk. About pimo:Tag description: "Tags in the context of PIMO. A marker class for Things that are used to categorize documents (or other things). Tags must be a kind of Thing and must have a unique label. Documents should not be Tags by default." About nao:Tag description: "This class is useful for modelling conventional tagging practices. The user can tag resources in conventional ways, automatically creating an instance of this tag, which is then related to the annotated resource via the nao:hasTag property. For more on tagging as annotation see Section 2.3.". I've read this section and the explanation is very convincing. Thanks in advance. Kind regards -- Tomás Vírseda _______________________________________________ people mailing list people-8FRlne0xlECvj1b/ULB3Z0B+6BGkLq7r@public.gmane.org http://lists.semanticdesktop.org/mailman/listinfo/people


-- _____________________________________________________ Dr. Leo Sauermann http://www.dfki.de/~sauermann Deutsches Forschungszentrum fuer Kuenstliche Intelligenz DFKI GmbH Trippstadter Strasse 122 P.O. Box 2080 Fon: +43 6991 gnowsis D-67663 Kaiserslautern Fax: +49 631 20575-102 Germany Mail: leo.sauermann-7kGu3w2zD6I@public.gmane.org Geschaeftsfuehrung: Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 _____________________________________________________
<div>
It was Evgeny Egorochkin who said at the right time 25.09.2009 18:43
the following words:
<blockquote cite="mid:200909251943.30134.phreedom.stdin@..." type="cite">
  Basically I think the biggest concern here is interoperability between nao:Tag 
and pimo:Tag.

How can applications that use nao:Tag and pimo:Tag "talk" to each other?

</blockquote>
let the same instance be both a nao:tag and a pimo:Tag.<br><br>
but our plan was:<br>
* nao:Tag is piss-easy, we use it now to get KDE 4.0 off the ground
(... this we said in ~Oct 2006)<br>
* pimo:Tag is way cooler because your things in live are tags. We
should update KDE for this (... uh....)<br><br>
so, it will take some time to get there.<br><br>
Sebastian Tr&uuml;g actually worked on some ways to do this - I think.<br><br>
did you?<br><br>
best<br>
Leo<br><br><br><blockquote cite="mid:200909251943.30134.phreedom.stdin@..." type="cite">

&#1042; &#1089;&#1086;&#1086;&#1073;&#1097;&#1077;&#1085;&#1080;&#1080; &#1086;&#1090; &#1055;&#1103;&#1090;&#1085;&#1080;&#1094;&#1072; 25 &#1089;&#1077;&#1085;&#1090;&#1103;&#1073;&#1088;&#1103; 2009 19:30:58 &#1072;&#1074;&#1090;&#1086;&#1088; Leo Sauermann &#1085;&#1072;&#1087;&#1080;&#1089;&#1072;&#1083;:

  <blockquote type="cite">
    as others may be interested in this discussion, I am also including xesam
(= the ontology developers list)

I was a bit slow to answer, sorry.

Tom&aacute;s - what are you programming? do you have a url or a blogpost about
your work?

nao:Tag is for systems that just use NAO/NIE and are fine with
no-brainer solutions.
a nao:Tag has the semantic meaning of : the tag is a string. its unique.

pimo:Tag is for systems that want to achieve a highlevel integration of
Addressbooks, Calendars, Websites, etc... into a semantic network.
pimo:Tags are then not only tags, but can be also a pimo:Person - that
is, you can use a person's name to tag something but - surprise - it is
also a person.
now clicking on the person will get more...
a pimo:Tag has the semantic meaning of : the tag is a unique string
which is also a Thing out of the real world which can have more attributes.

I also documented this here in the FAQ
<a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebe">https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferencebe</a>
tweennao:Tagandpimo:Tag

best
Leo

It was Tom&aacute;s V&iacute;rseda who said at the right time 12.09.2009 23:50 the

following words:

    <blockquote type="cite">
      Hi,

I'm confused about pimo:Tag and nao:Tag classes described in their
respective ontology. Which is the difference between these two clases?
I'm reading the ontologies documentation but I can't still figure out
how they should be used. I'm developing a tagging system in a
application and I would like to use Nepomuk.

About pimo:Tag description:
"Tags in the context of PIMO. A marker class for Things that are used
to categorize documents (or other things). Tags must be a kind of
Thing and must have a unique label. Documents should not be Tags by
default."

About nao:Tag description:
"This class is useful for modelling conventional tagging practices.
The user can tag resources in conventional ways, automatically
creating an instance of this tag, which is then related to the
annotated resource via the nao:hasTag property. For more on tagging as
annotation see Section 2.3.". I've read this section and the
explanation is very convincing.

Thanks in advance.
Kind regards

--
Tom&aacute;s V&iacute;rseda
_______________________________________________
people mailing list
<a class="moz-txt-link-abbreviated" href="mailto:people <at> semanticdesktop.org">people@...</a>
<a class="moz-txt-link-freetext" href="http://lists.semanticdesktop.org/mailman/listinfo/people">http://lists.semanticdesktop.org/mailman/listinfo/people</a>

    </blockquote>
  </blockquote>

  
</blockquote>
<br><br>-- 
_____________________________________________________
Dr. Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 

Deutsches Forschungszentrum fuer 
Kuenstliche Intelligenz DFKI GmbH
Trippstadter Strasse 122
P.O. Box 2080           Fon:   +43 6991 gnowsis
D-67663 Kaiserslautern  Fax:   +49 631 20575-102
Germany                 Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@...">leo.sauermann@...</a>

Geschaeftsfuehrung:
Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
_____________________________________________________

</div>
Siegfried Handschuh | 25 Sep 18:55 2009

Re: pimo:Tag vs nao:Tag

Hi,

so this time, with the right subject ;)

Actually the philosophy in NAO is a bit different. You can also do
there an annotation of Addressbooks, Calendars, Websites etc. But you
would indeed not use nao:Tag.

NAO has a set of relations you can use to annotate a resource with
another resource. To annotate a resource with pimo:Person you could
use, for example, nao:isRelated.

just my two cents.

cheers
Siggi
Evgeny Egorochkin | 25 Sep 19:27 2009
Picon

Re: [people] pimo:Tag vs nao:Tag

В сообщении от Пятница 25 сентября 2009 20:07:51 автор Leo Sauermann написал:
> It was Evgeny Egorochkin who said at the right time 25.09.2009 18:43 the
> 
> following words:
> > Basically I think the biggest concern here is interoperability between
> > nao:Tag and pimo:Tag.
> >
> > How can applications that use nao:Tag and pimo:Tag "talk" to each other?
> 
> let the same instance be both a nao:tag and a pimo:Tag.
> 
> but our plan was:
> * nao:Tag is piss-easy, we use it now to get KDE 4.0 off the ground (...
> this we said in ~Oct 2006)
> * pimo:Tag is way cooler because your things in live are tags. We should
> update KDE for this (... uh....)
> 
> so, it will take some time to get there.
> 
> Sebastian Trüg actually worked on some ways to do this - I think.
> 
> did you?

Basically since "cheap pimo:Thingification"[1] is agreed on in principle, I 
believe kde could move to using pimo:Tag anytime.

[1] https://sourceforge.net/apps/trac/oscaf/ticket/45

> > В сообщении от Пятница 25 сентября 2009 19:30:58 автор Leo
Sauermann 
написал:
> >> as others may be interested in this discussion, I am also including
> >> xesam (= the ontology developers list)
> >>
> >> I was a bit slow to answer, sorry.
> >>
> >> Tomás - what are you programming? do you have a url or a blogpost about
> >> your work?
> >>
> >> nao:Tag is for systems that just use NAO/NIE and are fine with
> >> no-brainer solutions.
> >> a nao:Tag has the semantic meaning of : the tag is a string. its unique.
> >>
> >> pimo:Tag is for systems that want to achieve a highlevel integration of
> >> Addressbooks, Calendars, Websites, etc... into a semantic network.
> >> pimo:Tags are then not only tags, but can be also a pimo:Person - that
> >> is, you can use a person's name to tag something but - surprise - it is
> >> also a person.
> >> now clicking on the person will get more...
> >> a pimo:Tag has the semantic meaning of : the tag is a unique string
> >> which is also a Thing out of the real world which can have more
> >> attributes.
> >>
> >> I also documented this here in the FAQ
> >> https://sourceforge.net/apps/trac/oscaf/wiki/PIMO/FAQ#Whatisthedifferenc
> >>ebe tweennao:Tagandpimo:Tag
> >>
> >> best
> >> Leo
> >>
> >>
> >>
> >> It was Tomás Vírseda who said at the right time 12.09.2009 23:50 the
> >>
> >> following words:
> >>> Hi,
> >>>
> >>> I'm confused about pimo:Tag and nao:Tag classes described in their
> >>> respective ontology. Which is the difference between these two clases?
> >>> I'm reading the ontologies documentation but I can't still figure out
> >>> how they should be used. I'm developing a tagging system in a
> >>> application and I would like to use Nepomuk.
> >>>
> >>> About pimo:Tag description:
> >>> "Tags in the context of PIMO. A marker class for Things that are used
> >>> to categorize documents (or other things). Tags must be a kind of
> >>> Thing and must have a unique label. Documents should not be Tags by
> >>> default."
> >>>
> >>> About nao:Tag description:
> >>> "This class is useful for modelling conventional tagging practices.
> >>> The user can tag resources in conventional ways, automatically
> >>> creating an instance of this tag, which is then related to the
> >>> annotated resource via the nao:hasTag property. For more on tagging as
> >>> annotation see Section 2.3.". I've read this section and the
> >>> explanation is very convincing.
> >>>
> >>> Thanks in advance.
> >>> Kind regards
> >>>
> >>> --
> >>> Tomás Vírseda
> >>> _______________________________________________
> >>> people mailing list
> >>> people <at> semanticdesktop.org
> >>> http://lists.semanticdesktop.org/mailman/listinfo/people
> 
_______________________________________________
Xesam mailing list
Xesam <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xesam
Ivan Frade | 26 Sep 09:55 2009
Picon

Re: [people] pimo:Tag vs nao:Tag

Hi,

On Fri, Sep 25, 2009 at 7:30 PM, Leo Sauermann <leo.sauermann-7kGu3w2zD6I@public.gmane.org> wrote:
nao:Tag is for systems that just use NAO/NIE and are fine with
no-brainer solutions.
a nao:Tag has the semantic meaning of : the tag is a string. its unique. 

pimo:Tag is for systems that want to achieve a highlevel integration of
Addressbooks, Calendars, Websites, etc... into a semantic network.
pimo:Tags are then not only tags, but can be also a pimo:Person - that
is, you can use a person's name to tag something but - surprise - it is
also a person

Out of curiosity: so "pimo:Tag" is then a generic "link" between two resources?

It sounds like we could replace all properties between concepts (exclusing inheritance) as tags: "music piece belongs to an album" could be a Tag, Contact sent an email..." another tag, "Contact has postal address" another tag....

.
now clicking on the person will get more...
a pimo:Tag has the semantic meaning of : the tag is a unique string
which is also a Thing out of the real world which can have more attributes.

Then it is opening the door to all kind of "custom properties". A pimo:Tag is like a property between two things that the user can label... it sounds pretty dangerous.

Regards,,

Ivan

<div>
<p>Hi,<br><br></p>
<div class="gmail_quote">On Fri, Sep 25, 2009 at 7:30 PM, Leo Sauermann <span dir="ltr">&lt;<a href="mailto:leo.sauermann@...">leo.sauermann@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
nao:Tag is for systems that just use NAO/NIE and are fine with<br>
no-brainer solutions.<br>
a nao:Tag has the semantic meaning of : the tag is a string. its unique.&nbsp;<br>
</blockquote>
<blockquote class="gmail_quote">
<br>
pimo:Tag is for systems that want to achieve a highlevel integration of<br>
Addressbooks, Calendars, Websites, etc... into a semantic network.<br>
pimo:Tags are then not only tags, but can be also a pimo:Person - that<br>
is, you can use a person's name to tag something but - surprise - it is<br>
also a person</blockquote>
<div>
<br>Out of curiosity: so "pimo:Tag" is then a generic "link" between two resources? <br><br>It sounds like we could replace all properties between concepts (exclusing inheritance) as tags: "music piece belongs to an album" could be a Tag, Contact sent an email..." another tag, "Contact has postal address" another tag....<br><br>
</div>
<blockquote class="gmail_quote">.<br>
now clicking on the person will get more...<br>
a pimo:Tag has the semantic meaning of : the tag is a unique string<br>
which is also a Thing out of the real world which can have more attributes.<br>
</blockquote>
<div>
<br>Then it is opening the door to all kind of "custom properties". A pimo:Tag is like a property between two things that the user can label... it sounds pretty dangerous.<br><br>Regards,,<br><br>Ivan</div>
</div>
<br>
</div>

Gmane