Re: event subscribe operation SET-PROPERTY ?

perhaps I misunderstand something,but in LaserFrameLFB definition of model 
draft,the eventTarget section include severl eventPathType definitions,that 
confuse me,if that is allowed,why don't we use the common method to enclose 
them,just enclose each eventPathType with <eventTargetField> and 
<\eventTargetField>(just for example,we can use other names).I quoted the 
LaserFrameLFB as follows:
           <event eventID="5"> 
                <name>FrameCircuitChanged</name> 
                <synopsis> 
                    the state of an Fr circuit on a frequency  
                    has changed 
                </synopsis> 
                <eventTarget> 
                  <eventField>FrequencyInformation</eventField> 
                  <eventSubscript>_FrequencyIndex_</eventSubscript> 
                  <eventField>FrameRelayCircuits</eventField> 
                  <eventSubscript>FrameCircuitIndex</eventSubscript> 
                  <eventField>CircuitStatus</eventField> 
                </eventTarget> 
                <eventChanged/> 
                <eventReports> 
                  <eventReport> 
                    <eventField>FrequencyInformation</eventField> 
                    <eventSubscript>_FrequencyIndex_</eventSubscript> 
                    <eventField>FrameRelayCircuits</eventField> 
                    <eventSubscript>FrameCircuitIndex</eventSubscript> 
                    <eventField>CircuitStatus</eventField> 
                  </eventReport> 
                  <eventReport> 
                    <eventField>FrequencyInformation</eventField> 
                    <eventSubscript>_FrequencyIndex_</eventSubscript> 
                    <eventField>FrameRelayCircuits</eventField> 
                    <eventSubscript>FrameCircuitIndex</eventSubscript> 
                    <eventField>DLCI</eventField> 
                  </eventReport> 
                </eventReports> 
Yours,Fenggen
>From: "Joel M. Halpern" <[email protected]>
>To: Jia Fenggen <[email protected]>,[email protected]
>Subject: Re: event subscribe operation  SET-PROPERTY ?
>Date: Fri, 29 Sep 2006 07:13:05 -0400
>
>You are right about SET-PROPERTY and GET-PROPERTY!  Protocol Team, 
>is that being added to the protocol document.  (This is not a recent 
>change.)
>
>
>I am not sure I understand the other question.
>A given event definition can have only one event target.
>An event definition is the event name, the event target, the event 
>Condition (which describes the specific condition under which the 
>event is triggered) and the event Report (which indicates what is 
>reported.
>A given definition has a single target, a single condition, and a 
>single reports (which has a list of fields to report.
>We do not need "eventTargets" or "eventConditions", because each 
>event has one target and one conidition.
>
>If we had allowed multiple conditions in an event definition, then 
>the occurrence of the event would have to have some way of 
>indicating which condition had occurred.  Similarly, if there could 
>be multiple targets we would need to indicate which target had 
>detected the problem.  Withthe current structure, that problem does 
>not arise.
>
>
>At 01:40 AM 9/29/2006, Jia Fenggen wrote:
>>I notified in model draft when one wants to subcribe to an event,he 
>>uses SET-PROPERTY operation and use the path composed of event base 
>>id plus event id,here is a problem because we haven't defined 
>>operation SET-PROPERTY in protocol draft,and even a broader 
>>question,how should we do to get and set LFB element 
>>properities,how should the path be used,if I misunderstand 
>>something here,I am sorry.
>>And another question,because i am not an xml expert,i don't know 
>>why we not define <eventTarget> element as follows:
>><eventTargets>
>>   <eventTarget>
>>      <eventField>..</eventField>
>>      <eventSubscript>..</eventSubcript>
>>   </eventTarget>
>>   <eventTarget>
>>      <eventField>..</eventField>
>>      <eventSubscript>..</eventSubcript>
>>   </eventTarget>
>>    ...
>></eventTarget>
>>and the same question to <events> Element Conditions declaration.
>>Yours,Fenggen
>>
>>_________________________________________________________________
>>浜ㄤ涓澶х靛欢绯荤 MSN Hotmail  
>>http://www.hotmail.com
>

_________________________________________________________________
浜ㄤ涓澶х靛欢绯荤 MSN Hotmail  http://www.hotmail.com