AI 246

["Vambenepe, William N" <vbp@hp.com>]

I have an action item to check that subtopics in different namespaces
are still allowed by WS-Topics.

The answer is that the current draft of WS-Topics does not allow this,
but the group has made a decision to add this support, as illustrated by
the issue below. As you can see, the issue status is "open - approach
agreed" which means that the group has agreed on the resolution and the
editors need to reflect the resolution in the doc. This is being tracked
and won't get dropped.

Regards,

William




WSN4.4: Domain specific Extensions to Topic Spaces
There is no way for an industry to define a topic space and a
manufacturer defines some sub-topics of that space, but in its own
namespace. The only way to do it is to redefine the entire tree in your
own namespace. This makes it very cumbersome to extend a Topic Space.
Specifications
*	WS-Topics
Proposed Recommendations
Notes
During Jan/Feb 2005 F2F, this issue was discussed. The agreed approach
was:
WS-Topics specification to define mechanism for an individual root topic
to extend some topic from other TopicSpace by specifying a
ConcreteTopicPathExpression. This mechanism should allow
NotificationProducers to build relationships between independent topic
spaces without losing information about their individual namespaces.
	ConcreteTopicPathExpression and FullTopicPathExpression dialects
need modifications to allow namespace prefixes at any level in the
expression.  Prefix propagates right-wards until a new prefix appears in
the expression. Specifying null namespace requires an explicit syntax,
for example, expression "foo:bar/spam" expands to "foo:bar/foo:spam"
where as "foo:bar/:spam" indicates that the topic "spam" has no
namespace.
Status:   Open - approach agreed
Date: Feb 1, 2005
	Agreed Approach: See Jan/Feb 2005 F2F related comments in the
Notes section.

Contact: 
	Bryan Murray
Cross Reference: