RE: [tag] Requirement: component like a tag but for 'namespace'

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Tags will have names - we could have a set of predefined tag names, and
one of them could be what you are looking for. Would that work?
Also if named "namespace" would that be only for use with XML material?
 We need to make the case this naming problem is a general enough issue
that deserves a mention in the guidelines, independently from XML.

Jacques  

-----Original Message-----
From: stephen.green@systml.co.uk [mailto:stephen.green@systml.co.uk] 
Sent: Friday, May 23, 2008 4:54 AM
To: tag@lists.oasis-open.org
Subject: [tag] Requirement: component like a tag but for 'namespace'

Apologies it is such a late stage (and maybe too late for guidelines so
maybe something for adjunct document):
I feel there is need for another component (optional but possibly
important) in a TA: something like a namespace to create a TA package. I
suggest it is an upper level of grouping.
Rationale: when TAs are otherwise atomic and possibly self-contained,
there needs to be a way to associate TAs with a group, like tagging but
a bit more authoritative. It is a special kind of tag which is the same
in function as a namespace in XML/code and a package in modeling/code
but as with XML namespaces it can confer authority in that the authors
can reserve use of the namespace to their own work, say. Whether it
would include a version id is a special discussion as there may be
special problems with this like those in XML where there may be a need
to add TAs and/or introduce a new version without having to use a new
namespace. Maybe it is a type of tag particularly relevant to a header.

If it isn't to be added as a TA component, maybe it could be added as
metadata to the TA(s) - not to be confused with test metadata of course.

Again, apologies for the lateness.