View Single Post
Posts: 356 | Thanked: 231 times | Joined on Oct 2007
#20
Originally Posted by benny1967 View Post
doesn't personinimage (no matter if in plain iptc or in the xmp version) refer to the name of the person only? (I only read the spec now after your post, so i don't really know for sure.)
Specification isn't in stone I suspect in future standard will be expanded to include more details about person in image in more ordered way. Now this tag is the best thing to use IMO. Of course you can even create your own namespace and put there data but there is NULL chance any popular software will be able to process it properly.
if so, my family couldn't use it to tag photos: my father and i, we have exactly the same name. if you tag photos with this name, you can't search for me and only me.
Traditional systems used two simply methods:
John Smith I, John Smith II (don't confuse with anglo-saxon John Smith 1st, John Smith 2nd, etc.) or
John Smith (date of birth, date of death) - hard to use with living persons.
I think in this usecase the best way is to use e-mail to differentiate persons and adjust software to make e-mail addresses clickable.

also, in the N900 use case, we have to expect that some people enter contacts as "dad", "home", "sweetheart" and "peter's office". while the name is useless in such a situation, they may still have a unique mail address or other unique properties for these contacts.
Well, for "Peter's Office" you have OrganisationInImageName
But unless to use your photos as stock material I don't see any obstacles to put there not only "proper" names but nicks, relationship descriptions, etc.

are there examples of how to use PersonInImage with information other than the persons name anywhere? sounds interesting if it's as flexible as you say in XMP.
XMP is flexible but it has to be implemented. Iptc4xmpExt is quite young standard.