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

[Innovimax SARL]

On Wed, Jun 17, 2009 at 7:01 AM, Shawn Villaron <shawnv at microsoft.com>wrote:

> What's the migration story for files which pre-date 29500?  For example,
> suppose I have a binary wordprocessing document and it contains the
> equivalent @uri value of something like "c:\users\shawnv\desktop"?
>
then the migration is "file://c:/users/shwanv/desktop"


> Are you suggesting that there is no upgrade path to Strict for such files?
>
>

no see above


> Wouldn't this bring is into direct conflict with the existing scope of
> 29500?
>
>
>
> I wonder if there is the opportunity to slightly shift your proposal:
>
>
>
> ·         In "transitional", we offer no guidance
>
> ·         In "strict", we offer guidance that *should* use a namespace
> name
>
>
>
> The data type is going to be similarly tricky, for the same reasons.
>
>
>
>
>
> -----Original Message-----
> From: MURATA Makoto (FAMILY Given) [mailto:eb2m-mrt at asahi-net.or.jp]
> Sent: Saturday, June 13, 2009 6:11 AM
> To: SC 34 WG4
> Subject: Re: DR 09-0210: WML: Custom XML and Smart Tags
>
>
>
> > I would like to explicitly state @uri shall specify a namespace name
>
> > and @element shall specify a local name.  (BTW, "element type" as
>
> > defined in XML 1.0 is a string containing prefixses  (optional), ":"
>
> > (optional), and local names.  "Local name" is the best terminology.)
>
>
>
>
>
> Smart tags and custom XML markup should represent embedded foreign XML
> elements.  However, during the last teleconf, Shawn reported that foreign
> "elements" embedded in existing binary documents contain illegal namespace
> names.  Thus, if we would like to capture existing binary documents, we
> cannot disallow illegal namespace names for the uri attribute.  This
> observation does not apply to local names of embedded foreign elements.
>
>
>
> Having heard this observation, I would change my proposal.
>
>
>
> In "strict", we should require that @uri specify a namespace name.
>
> The schema in Part 1 should specify xsd:anyURI.
>
>
>
> In "transitional", we should recommend that @uri specify a namespace name..
>
>
> The schema in Part 1 should specify xsd:string.
>
>
>
> In both classes, we should require that @element shall specify a local
> name.  The schema in Part 1 should specify xsd:NCName.
>
>
>
> Cheers,
>
> Makoto
>
>
>



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090617/d5017fbb/attachment.htm>