Custom XML Defect Reports Batch

[Alex Brown]

> Then, it looks good to go …



Whoops, not so fast, Alex ...



There still remains this issue over the namespaces (which are not Namespaces) specify by the “uri” attribute for smart tags. The current proposal is like this:



----
As shown above, the smart tag is delimited by the smartTag element, which surrounds the run (or runs) which contain the text which is part of the smart tag. end example]
The smartTag element has two required  attributes:


·         The uri attribute is used to specify the namespace, in terms of a vocabulary or classification scheme, of which the term specified for this smart tag is a member  [Example: In the above example, the smart tag  specifies http://www.example.com to identify the classification scheme. end example]


·         The element attribute, in combination with the uri attribute, specifies the classification for this smart tag  [Example: In the above example, the smart tag specifies the classification term stockticker from the identified namespace. end example]
----



I don’t think we should have a schism between smart tags and implied XML, so propose something like this:



----
As shown above, the smart tag is delimited by the smartTag element, which surrounds the run (or runs) which contain the text which is part of the smart tag. end example]
The smartTag element has two required  attributes:


·         The uri attribute is used to specify a URI implying an XML Namespace the namespace, in terms of a vocabulary or classification scheme, of which the term specified for this smart tag is a member  [Example: In the above example, the smart tag  specifies http://www.example.com to identify the classification scheme. end example]


·         The element attribute, in combination with the uri attribute, specifies a NCName the classification for this smart tag  [Example: In the above example, the smart tag specifies the classification term the local name “stockticker” from the identified Namespace. end example]
----



- Alex.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20100506/868048eb/attachment.htm>