<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252"> <META content=Word.Document name=ProgId> <META content="MSHTML 5.50.4611.1300" name=GENERATOR> <META content="Microsoft Word 9" name=Originator><LINK href="cid:filelist.xml@01C0DD3C.C95522B0" rel=File-List> <STYLE>@font-face { font-family: Wingdings; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } A:visited { COLOR: purple; TEXT-DECORATION: underline; text-underline: single } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; text-underline: single } P.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } LI.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } DIV.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle16 { COLOR: navy; mso-style-type: personal-reply; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US style="tab-interval: .5in" vLink=purple link=blue> <DIV> </DIV> <DIV>My $.01.  I think it should be called a nexus.  Mostly because I like that word and think it sounds really cool.  To a lesser degree it might even be more accurate.  Locus might work but I'm a Star Trek fan too.  </DIV> <DIV> </DIV> <DIV>Seriously, never have liked resource.  Mostly because it's difficult for me to think of a location as a resource.  Of course, if I owned a Starbuck franchise or two, I might change my mind.</DIV> <DIV> </DIV> <DIV>What about classifying things, like <A href="mailto:mike@jabber.com/device/pager">mike@jabber.com/device/pager</A> or <A href="mailto:mike@jabber.com/location/home">mike@jabber.com/location/home</A>.  I'm an old AI hacker too.</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>[Michael Bauer]   -----Original Message----- From: Emswiler, Mike [mailto:MEmswiler@protrader.com] Sent: Tuesday, May 15, 2001 11:44 AM To: 'jdev@jabber.org' Subject: RE: [JDEV] Renaming </DIV> <DIV class=Section1> Just my $.02 worth:<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> It is an interesting debate.  I started working with jabber some time ago thinking of resource as a location, but now that I’ve used Jabber more and more, I tend to think of it more of a device, as in pager, cell phone, or even email.<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> For example, in my client, I find it useful to be able to send a text message to <A href="mailto:mikee@jabber.com/workpc">mikee@jabber.com/workpc</A>, <A href="mailto:mikee@jabber.com/homepc">mikee@jabber.com/homepc</A>, <A href="mailto:mikee@jabber.com/pager">mikee@jabber.com/pager</A>,  <A href="mailto:mikee@jabber.com/mobile">mikee@jabber.com/mobile</A> or <A href="mailto:mikee@jabber.com/cell">mikee@jabber.com/cell</A> , or even <A href="mailto:mikee@jabber.com/email">mikee@jabber.com/email</A> (which just redirects to whatever email address I have programmed it to … during the day it might be my work email and at night it might be home email…)<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> Or I can just send to <A href="mailto:mikee@jabber.com">mikee@jabber.com</A> and let my client determine the resource to actually deliver to based on the schedule and delivery mechanism I (as the end-user of my client) provide.<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> Of course, my client is more voice-centric and acts more like a CB than anything else, so mostly it goes to homepc or workpc resources … too bad Nextel hasn’t published a gateway to their Direct Connect feature J yet.<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> Irregardless of the client usage, *I* think resource is the perfect name because it is truly generic, allowing it to be a location or a device, or just about anything else someone might envision 10 years from now.  <o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> However, in developing *your* client, you might find it useful to call it whatever you like … it’s just a display label you present to the user.  Besides, I can’t imagine the work involved in actually renaming the thing throughout all the <grin> documentation, web pages, etc. or even more evilly, the source itself J<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> Thanks,<o:p></o:p> MikeE<o:p></o:p></DIV></BLOCKQUOTE></BODY></HTML>