[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Regards, Mark ------_=_NextPart_001_01C423C9.60A72914 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Message</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD> <BODY text=3D#000000 bgColor=3D#ffffff> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D319003915-16042004>Mark=20 Ellison posted this interesting article about notifications in the WSDM = group.=20 Since we are now looking at that in the PSTC, I thought it useful to = post it=20 here as well.</SPAN></FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Jeff Bohren</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Product = Architect</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>OpenNetwork Technologies,=20 Inc</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2></FONT> </DIV> <DIV align=3Dleft> <DIV><FONT face=3DArial size=3D2><SPAN = class=3D666091017-20102003><STRONG>Try the=20 industry's only 100% .NET-enabled identity management software.=20 Download your free copy of Universal IdP Standard Edition today. Go = to=20 </STRONG><A=20 href=3D"http://www.opennetwork.com/eval";><STRONG>www.opennetwork.com/eval= </STRONG></A><STRONG>.</STRONG></SPAN></FONT></DIV></DIV> <DIV align=3Dleft> </DIV> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> Mark Ellison=20 [mailto:ellison@ieee.org] <BR><B>Sent:</B> Friday, April 16, 2004 2:19=20 PM<BR><B>To:</B> wsdm@lists.oasis-open.org<BR><B>Subject:</B> [wsdm] = references=20 on topic- type-based notification = work<BR><BR></FONT></DIV>Hi,<BR><BR>There is a=20 good article in the March/April 2004 issue of IEEE Software, <A=20 href=3D"http://csdl.computer.org/comp/mags/so/2004/02/s2056abs.htm";>Distr= ibuted=20 Programming with Typed Events</A>, that provides a nice background on = the=20 publish-subscribe model based on subjects or topics. One of the = authors=20 published an earlier draft, <A=20 href=3D"http://www.daimi.au.dk/%7Ethomasr/Wearable/eugster-al_publish-sub= scribe.pdf">The=20 Many Faces of Publish/Subscribe</A>. These articles provide = addtional=20 references to publish/subscribe event distribution systems. = <BR><BR>The=20 following provides additional reference information not contained in the = above=20 articles.<BR><BR>SNMPv3 uses a crude form of topics. The =20 snmpTargetAddrTagList object, discussed in section 4.1.1, in <A=20 href=3D"http://www.rfc-editor.org/rfc/rfc3413.txt";>RFC 3413</A> (full = standard)=20 provides a means to specifiy _locally_coordinated_ topics, for example, = "acme",=20 "router", or "host". Essentially, a subscriber provides a list of = tags,=20 describing topics, for which they wish to receive notifications. There = is no=20 global coordination of topics and the values provided by instances = of the=20 snmpTargetAddrTagList object are application specific.<BR><BR>The <A=20 href=3D"http://www.ietf.org/html.charters/syslog-charter.html";>syslog = </A>working=20 group of the IETF has published <A=20 href=3D"http://www.rfc-editor.org/rfc/rfc3164.txt";>RFC 3164</A> = (informational),=20 describing the BSD syslog protocol. This syslog protocol uses = "facilities"=20 in the place of topics. Facilities are basically subsytems or = daemons=20 running on a UNIX host. This working group has a work-in-progress = draft=20 for a <A=20 href=3D"http://www.ietf.org/internet-drafts/draft-ietf-syslog-device-mib-= 05.txt">SYSLOG-MIB</A>=20 (uri subject to change over time...) that essentially models the = semantics of=20 the BSD syslog protocol as a MIB module. This MIB module also = serves to=20 montior the syslog daemon. There is also a work-in-progress = generalizing=20 <A=20 href=3D"http://www.ietf.org/internet-drafts/draft-ietf-syslog-protocol-03= .txt">the=20 syslog protocol</A>. Section 4.1.3 describes "facility" in a more = general=20 manner than the BSD syslog protocol, and states:<BR><PRE> The facility = is primarily a way to filter messages at the receiver. It is a numerical value. There exist some traditional facility code semantics for the codes in the range from 0 to 23. These semantics are not closely followed by all vendors, softwares and devices. Therefore, no specifc semantics for facility codes are implied in this document. FACILITY is just a sender-supplied numerical identifier that can be used for filtering by the receiver. The facility in itself does not have any semantics. Semantics MUST be applied by site configuration (through the site's administrator). Any implementation of this document MUST support free configuration of the FACILITY on the sender.</PRE>In the <A=20 href=3D"http://www.ietf.org/html.charters/disman-charter.html";>disman</A>= working=20 group of the IETF, as Andrea mentioned during the F2F, there is=20 work-in-progress, <A=20 href=3D"http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-1= 8.txt">disman-alarm-mib</A>,=20 harmonized with ITU work (M.3100, X.733, X.736). This MIB contains = a=20 couple of defintions- IANAItuProbableCause, that provides a list = of ITU=20 probable cause values, and, IANAItuEventType, that provides the ITU = event type=20 value. <BR><BR>From the W3C, <A=20 href=3D"http://www.w3.org/TR/2004/REC-owl-semantics-20040210/";>The OWL = Web=20 Ontology Language</A>, uses <A=20 href=3D"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/";>RDF</A>, to = define and=20 refine vocabulary. This is likely overkill for WSDM notification=20 topics. Likely there are CIMs from the DMTF (I understand that = Andrea will=20 provide references to these...) providing models that offer obvious base = (and=20 extensible ?) topics for WSDM event=20 notifications.<BR><BR>Regards,<BR><BR>Mark<BR><BR></BODY></HTML> =00 ------_=_NextPart_001_01C423C9.60A72914--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]