Ticket #406 (closed task: fixed)

Opened 4 months ago

Last modified 7 weeks ago

why is nco#imID not a subpropery of nie:identifier?

Reported by: leosauermann Owned by: antonimylka
Priority: normal Milestone:
Component: ontology-nie Version:
Keywords: Cc: mylka@…

Description

see http://www.semanticdesktop.org/ontologies/nco/#imID

should be a nie:identifier? or?

Change History

Changed 4 months ago by antonimylka

  • owner changed from AntoniMylka to antonimylka

Indeed. It would especially useful for contacts obtained by crawling IM contact list, where the IM identifier is acutally the identifier of the contact.

Will do

Changed 2 months ago by antonimylka

  • status changed from new to closed
  • resolution set to wontfix

I looked at it. Actually not. nie:identifier is a property of an informationElement. imID is not a property of a contacdt, but a property of a contact medium, the same way a telephone number (also a unique identifier, for which a well-defined standardized URI scheme exists RFC 3966) is not a nie:identifier, but a property of a contact medium (TelephoneNumber)

This was a design decision. Right now making this change would force all IMAccounts to be information elements. Too big a consequence.

I close this as wontfix

Changed 2 months ago by leosauermann

  • status changed from closed to reopened
  • resolution deleted

hm, I am happy about the answer, but not content :-)

ok, so informationelement is wrong, ack.

but still we can make nco:imId a sub-property of nao:identifier ?!

this would be a first step to make the ContactMedium a way to match people together.

Changed 7 weeks ago by antonimylka

done, in revs [8930], [8931] and [8932] please confirm

Changed 7 weeks ago by leosauermann

  • status changed from reopened to closed
  • resolution set to fixed

I reviewed, changes are fine, PIMO got jumbled. I close this ticket and us two know how to fix the HTML rendering of PIMO "later" :-)

Note: See TracTickets for help on using tickets.