[foaf-dev] foaf:mbox but not IFP?

What should I use instead of foaf:mbox when the property should NOT be
an Inverse Functional Property?  Example: I'm starting an address book
(and more) webapp for my family and my Aunt and Uncle both use the same
email address.

http://xmlns.com/foaf/spec/#term_mbox says "Note that there are many
mailboxes (eg. shared ones) which are not the foaf:mbox of anyone" but
it doesn't say what they should be.

What's my best option?

http://www.w3.org/2000/10/swap/pim/contact#mailbox is an IFP also.

http://www.w3.org/2001/vcard-rdf/3.0#EMAIL seems verbose

http://norman.walsh.name/2005/12/05/vcard looks better but probably
isn't widely used.

http://rdfs.org/sioc/ns#email looks good

Thanks!

--

-- 
Dave Brondsema : dave@...
http://www.brondsema.net : personal
http://www.splike.com : programming
               <><

Re: [foaf-dev] foaf:mbox but not IFP?

Hi Dave,

How about http://www.w3.org/2006/vcard/ns#email ?
(or maybe http://www.w3.org/2006/vcard/ns#personalEmail )

cheers,

2008/1/3, Dave Brondsema <dave@...>:
> What's my best option?
>
> http://www.w3.org/2000/10/swap/pim/contact#mailbox is an IFP also.
>
> http://www.w3.org/2001/vcard-rdf/3.0#EMAIL seems verbose
>
> http://norman.walsh.name/2005/12/05/vcard looks better but probably
> isn't widely used.
>
> http://rdfs.org/sioc/ns#email looks good

--

-- 
 <at> prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name
"KANZAKI Masahide", "神崎正英"; :email "mkanzaki@..."].

Re: [foaf-dev] foaf:mbox but not IFP?

On Jan 3, 2008 5:16 AM, Dave Brondsema <dave@...> wrote:
>
> What should I use instead of foaf:mbox when the property should NOT be
> an Inverse Functional Property?  Example: I'm starting an address book
> (and more) webapp for my family and my Aunt and Uncle both use the same
> email address.
>
> http://xmlns.com/foaf/spec/#term_mbox says "Note that there are many
> mailboxes (eg. shared ones) which are not the foaf:mbox of anyone" but
> it doesn't say what they should be.

Why not using it for a foaf:Group which includes your Aunt and Uncle ?
So, the mbox will be an IFP for a group consisting of both of them.
It will be OK, since the domain of this property is a foaf:Agent, not
a foaf:Person, unless "ie. an Internet mailbox associated with exactly
one owner, the first owner of this mailbox." means that the owner
should be only a single person ( but in that case the domain should be
changed in the specs).
IMHO, using a group makes sense.

Best,

Alex.

> What's my best option?
>
> http://www.w3.org/2000/10/swap/pim/contact#mailbox is an IFP also.
>
> http://www.w3.org/2001/vcard-rdf/3.0#EMAIL seems verbose
>

[foaf-dev] foaf impact?

Is foaf having any (positive) impact - as presumably it should - on the dynamics being expressed in the
article at http://www.news.com/8301-13577_3-9839474-36.html?tag=nefd.top

Re: [foaf-dev] foaf:mbox but not IFP?

+1 for Alex's solution.

Henry

On 4 Jan 2008, at 05:44, Alexandre Passant wrote:

>>
>> http://xmlns.com/foaf/spec/#term_mbox says "Note that there are many
>> mailboxes (eg. shared ones) which are not the foaf:mbox of anyone"  
>> but
>> it doesn't say what they should be.
>
> Why not using it for a foaf:Group which includes your Aunt and Uncle ?
> So, the mbox will be an IFP for a group consisting of both of them.
> It will be OK, since the domain of this property is a foaf:Agent, not
> a foaf:Person, unless "ie. an Internet mailbox associated with exactly
> one owner, the first owner of this mailbox." means that the owner
> should be only a single person ( but in that case the domain should be
> changed in the specs).
> IMHO, using a group makes sense.
>
> Best,
>
> Alex.

_______________________________________________
foaf-dev mailing list

Re: [foaf-dev] foaf:mbox but not IFP?

On 04/01/2008, Alexandre Passant <alex@...> wrote:
> On Jan 3, 2008 5:16 AM, Dave Brondsema <dave@...> wrote:
> >
> > What should I use instead of foaf:mbox when the property should NOT be
> > an Inverse Functional Property?  Example: I'm starting an address book
> > (and more) webapp for my family and my Aunt and Uncle both use the same
> > email address.
> >
> > http://xmlns.com/foaf/spec/#term_mbox says "Note that there are many
> > mailboxes (eg. shared ones) which are not the foaf:mbox of anyone" but
> > it doesn't say what they should be.
>
> Why not using it for a foaf:Group which includes your Aunt and Uncle ?
> So, the mbox will be an IFP for a group consisting of both of them.
> It will be OK, since the domain of this property is a foaf:Agent, not
> a foaf:Person, unless "ie. an Internet mailbox associated with exactly
> one owner, the first owner of this mailbox." means that the owner
> should be only a single person ( but in that case the domain should be
> changed in the specs).
> IMHO, using a group makes sense.

Yup, I was about to suggest Group, which you can just write as
<Agent>, since all groups are agents. There are some properties which
are Person-only (see http://xmlns.com/foaf/spec/images/foafspec.jpg
(unless you've tabulator installed, sorry)) but in general that should
work.

It is possible to be fancy and enumerate the contents of the group,
but for a simple addressbook, just writing "Agent" with name, mbox and
other applicable properties should make sense.

[foaf-dev] RDFa for HTML imagemap accessibility and clipart?

Hi folks

Digging out an old hack here, to see how it looks in the light of RDFa.

I'd like someone to explain to me how current RDFa could be used to 
extract info from imagemap markup. I'll try to find out myself using the 
.js parser, but I'm not currently intimate with the subtle details of 
the spec.

HTML has a somewhat neglected notation for describing regions of images, 
and associating them with links. Here's a picture of me markup up in 
this way, using YokMap, a Shareware MacOSX imagemap editor:

http://danbri.org/2008/imagemap/real.html

The markup is small enough I'll include it inline here:

<map name="da8bb51_b" id="da8bb51_b">
<area 
shape="POLY"
coords="463,662,450,633,441,604,433,573,429,561,431,542,431,531,439,503,446,487,465,460,476,435,486,407,500,382,511,363,528,348,543,315,549,301,581,288,629,279,652,275,668,275,681,263,693,257,710,250,706,248,700,240,697,221,696,204,691,198,688,186,691,173,693,167,693,158,697,146,699,135,706,128,702,123,709,113,710,104,722,101,723,93,742,93,756,92,766,86,767,93,778,85,803,82,803,88,813,89,813,95,826,104,842,113,853,123,864,145,871,160,879,172,875,176,881,184,879,190,882,199,879,213,877,222,869,229,866,234,859,256,853,267,866,282,875,284,923,283,936,284,941,290,948,295,962,301,969,310,977,328,986,338,990,350,1008,368,1015,373,1021,382,1012,526,1022,744,1007,741,982,721,962,732,949,731,947,767,517,767,520,759,488,720,475,697,466,681" 

   href="http://danbri.org/" />
</map> <img  src="2169955372_503da8bb51_b.jpg"  width="1024" 
height="770" usemap="#da8bb51_b" />

A few years ago, both in the FOAF project and as part of the EU 
SWAD-Europe project some of us were experimenting with using this as 
metadata in RDF, and as something that can be transformed and visually 
presented with SVG.

[foaf-dev] Re: RDFa for HTML imagemap accessibility and clipart?

Hi Dan,

I made a run at it; it is actually pretty close to Niklas' second 
version. What I guess you wanted to achieve was:

_:a a foaf:Person;
     foaf:name "Dan Brickley".
<#area> ex:depicts _:a.
<http://danbri.org> foaf:primaryTopic :_a.

According to the latest status of the group's discussions (not the 
syntax document as published, though), the following encoding does the 
trick:

<div instanceof="foaf:Person"
   property="foaf:name" content="Dan Brickley">
   <map name="da8bb51_b" id="da8bb51_b">
     <area id="area1"
       shape="POLY" coords="463,662,..."
       rev="foaf:primaryTopic" href="http://danbri.org/"/>
   </map>
   <span rev="foaf:depicts" resource="#area1"/>
   <img src="2169955372_503da8bb51_b.jpg"
      width="1024" height="770" usemap="#da8bb51_b"/>
</div>

The reason why a separate <span> is necessary is because for many use 
cases the special interpretation of  <at> src is necessary, and does get a 
special usage in RDFa (essentially, it behaves like an  <at> about). That is 
why the  <at> rev and  <at> resource pair could not be put on the <img> element. 

[foaf-dev] Re: RDFa for HTML imagemap accessibility and clipart?

Ivan Herman wrote:
> Hi Dan,
> 
> I made a run at it; it is actually pretty close to Niklas' second 
> version. What I guess you wanted to achieve was:
> 
> _:a a foaf:Person;
>     foaf:name "Dan Brickley".
> <#area> ex:depicts _:a.
> <http://danbri.org> foaf:primaryTopic :_a.
> 

Sorry, I meant _:a

> According to the latest status of the group's discussions (not the 
> syntax document as published, though), the following encoding does the 
> trick:
> 
> <div instanceof="foaf:Person"
>   property="foaf:name" content="Dan Brickley">
>   <map name="da8bb51_b" id="da8bb51_b">
>     <area id="area1"
>       shape="POLY" coords="463,662,..."
>       rev="foaf:primaryTopic" href="http://danbri.org/"/>
>   </map>
>   <span rev="foaf:depicts" resource="#area1"/>
>   <img src="2169955372_503da8bb51_b.jpg"
>      width="1024" height="770" usemap="#da8bb51_b"/>
> </div>

[foaf-dev] Re: RDFa for HTML imagemap accessibility and clipart?

Ivan Herman wrote:
> I made a run at it; it is actually pretty close to Niklas' second 
> version.

Thanks Ivan, Niklas, Karl, ...

We're getting there!

> What I guess you wanted to achieve was:
> 
> _:a a foaf:Person;
>     foaf:name "Dan Brickley".
> <#area> ex:depicts _:a.
> <http://danbri.org> foaf:primaryTopic :_a.

Yup, but I was hoping also to get the details of the area and the image 
URL into triples too, so a SPARQL store can be a self-contained 
photographic addressbook / clipart db.

I put your example into http://danbri.org/2008/imagemap/ivan.html and 
ran the latest GetN3 .js bookmarklet on it. Results:

_:n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> 
<http://xmlns.com/foaf/0.1/Person> .
_:n0 <http://xmlns.com/foaf/0.1/name> "Dan Brickley" <at> en .

<http://danbri.org/2008/imagemap/ivan.html#area1> 
<http://xmlns.com/foaf/0.1/depicts> _:n0 .

hmm it's not getting the primaryTopic. Maybe the .js is out of date?