[mapguide-internals] MapGuide RFC 17 - Map Space Line Widths

[Chris Claydon]

I thought about that as I was writing up the RFC. If we rev the schema
version, it shouldn't be necessary, since whatever tool is used to
update existing repositories would add the new element.

And...

If we don't rev the schema, it would go into an <ExtendedData1> element,
which is optional anyway - though <SizeContext> should strictly be
optional inside that element in case the schema needs to be extended
still further.

Chris.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Robert
Bray
Sent: February 26, 2007 11:07 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] MapGuide RFC 17 - Map Space Line
Widths

Chris,

Should the <SizeContext> element be optional with an assumed default to 
device space for compatibility reasons?

Thanks,
Bob

Chris Claydon wrote:
> The draft RFC 17 specification is now ready for review:
> 
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc17 
> 
> Please post any comments to this mailing list.
> 
> Thanks,
> 
> Chris Claydon.
> 
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals