DR 09-0211: WML: Custom XML and Smart Tags

[Alex Brown]

I think this general question about whether Smart Tags are meant to
imply XML, is related to comment #08-00131.

Since the Standard states:

"The distinction between custom XML markup and smart tags is that custom
XML markup is based on a specified schema."

Then, if that is the *only* difference, it currently must be that smart
tags should always map exactly to well-formed XML content.

- Alex.

> -----Original Message-----
> From: Alex Brown [mailto:alexb at griffinbrown.co.uk]
> Sent: 29 May 2009 15:58
> To: Shawn Villaron; SC 34 WG4
> Subject: RE: DR 09-0211: WML: Custom XML and Smart Tags
> 
> As in the last email calling the names of these things "element names"
> implies that they correspond to XML constructs. If they do, fine (but
> that leaves the Namespace question of the last email open); if they
> don't perhaps the names should just be referred to as "names" ?
> 
> 
> 
> - Alex.
> 
> 
> 
> From: Shawn Villaron [mailto:shawnv at microsoft.com]
> Sent: 29 May 2009 15:21
> To: SC 34 WG4
> Subject: DR 09-0211: WML: Custom XML and Smart Tags
> 
> 
> 
> Nature of the Defect:
> 
> ParaThe second bullet on pp. 529 has, "This allows the smart tag to
> specify a name which identifies this type of smart tag within its
> namespace and again available to a consumer."
> 
> 
> 
> The standard should not attempt to explain the purpose of XML Element
> Type Names in normative text. Also, this sentence does not make sense.
> 
> 
> 
> Here is the proposed response for this DR:
> 
> The exact changes are as follows:
> 
> *         The second of these is the element name for this smart tag
> (contained in the element attribute). [Guidance: This allows the smart
> tag to specify a name which identifies this type of smart tag within
> its namespace and again available to a consumer. It is intended to be
> used to specify a unique name for this type of smart tag. end
guidance]
> [Example: In the sample above, the smart tag specifies that its data
is
> of style stockticker. end example]
> 
> I've like to suggest that we move this to LAST CALL.
> 
> 
> 
> shawn
> 
>