Re: [wsrp] Wildcards and QNames

[Subbu Allamaraju <subbu@bea.com>]

I prefer to leave the local name as is, and introduce a boolean as you 
were suggesting at the start of this thread. Picking up a char from 
NCName seems like a hack.

Subbu

Rich Thompson wrote:
> 
> The localpart of a QName is an NCName, defined at 
> http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName
> 
> Rich
> 
> 
> *Rich Thompson/Watson/IBM@IBMUS*
> 
> 05/08/06 08:35 PM
> 
> 	
> To
> 	wsrp@lists.oasis-open.org
> cc
> 	
> Subject
> 	Re: [wsrp] Wildcards and QNames
> 
> 
> 	
> 
> 
> 
> 
> 
> 
> The current spec has both able to specify wildcards. It is likely more 
> useful on handledEvents, but if the Portlet is referring to third party 
> event names, I can see use cases for it on publishedEvents as well.
> 
> Rich
> 
> *Subbu Allamaraju <subbu@bea.com>*
> 
> 05/08/06 01:50 PM
> 
> 	
> To
> 	wsrp@lists.oasis-open.org
> cc
> 	
> Subject
> 	Re: [wsrp] Wildcards and QNames
> 
> 
> 
> 	
> 
> 
> 
> 
> 
> 
> To be clear, does this boolean exist only on handledEvents, or both
> publshedEvents and handledEvents?
> 
> Subbu
> 
> Rich Thompson wrote:
>  >
>  > It would just be moving the semantics we currently have regarding
>  > wildcarding for event names to this new structure. Namely; if
>  > wildcarding is in use, it requires only that a QName match on the URI
>  > part and start with the local part. When wildcarding is not use, an
>  > exact match on both parts is required.
>  >
>  > Rich
>  >
>  >
>  > *Subbu Allamaraju <subbu@bea.com>*
>  >
>  > 05/08/06 01:00 PM
>  >
>  >                  
>  > To
>  >                  Rich Thompson/Watson/IBM@IBMUS
>  > cc
>  >                  wsrp@lists.oasis-open.org
>  > Subject
>  >                  Re: [wsrp] Wildcards and QNames
>  >
>  >
>  >                  
>  >
>  >
>  >
>  >
>  >
>  > Could you elaborate on the boolean part?
>  >
>  > Subbu
>  >
>  > Rich Thompson wrote:
>  >  >
>  >  > Richard had raised a question about whether the wildcard scheme for
>  >  > publishedEvents and handledEvents results in a valid QName; in
>  >  > particular, can the localPart of the name contain a '*'. In digging
>  >  > through the relevant RFC, it is clear that the localPart can not 
> contain
>  >  > a '*'.
>  >  >
>  >  > Unless someone has a better idea, I will introduce a type to carry the
>  >  > QName and a boolean flag with the semantics that defines the QName to
>  >  > match any other QName with the same URI part and starting with the
>  >  > supplied local part.
>  >  >
>  >  > Rich
>  >  > 
> --------------------------------------------------------------------- To
>  >  > unsubscribe from this mail list, you must leave the OASIS TC that
>  >  > generates this mail. You may a link to this group and all your TCs in
>  >  > OASIS at:
>  >  > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>  >
>  >
>  >
>  > --------------------------------------------------------------------- To
>  > unsubscribe from this mail list, you must leave the OASIS TC that
>  > generates this mail. You may a link to this group and all your TCs in
>  > OASIS at:
>  > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> --------------------------------------------------------------------- To 
> unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail. You may a link to this group and all your TCs in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> --------------------------------------------------------------------- To 
> unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail. You may a link to this group and all your TCs in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.