[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mapguide-internals
Subject:    RE: [mapguide-internals] MapGuide RFC 53 Review
From:       Steve Dang <steve.dang () autodesk ! com>
Date:       2008-09-15 17:34:20
Message-ID: E904795F247888499B9A49F88DEBA1DE3CE9E7F022 () ADSK-NAMSG-01 ! MGDADSK ! autodesk ! com
[Download RAW message or body]

Hi list,

I've not heard any comment/suggestion on this issue so I assume we want to stick with \
the simple approach of using the "." delimiter for class names. Please let me know if \
there is a problem.

Thanks,
Steve.

-----Original Message-----
From: Steve Dang
Sent: Tuesday, August 19, 2008 5:10 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 53 Review

I have discussed with our MapGuide Development team about an alternative way to \
format/encode a comma delimited string.

Here is our proposal: The class name will be enclosed by double quotes if it contains \
any comma, and any double quote inside this class name will be double quoted.

For example, for the following list of class names:

Class1,
Class2
Class3"
",Class4

The comma delimited string of these class names will look like:

"Class1,",Class2,Class3",""",Class4"

Comments/suggestions?

Thanks,
Steve.

-----Original Message-----
From: mapguide-internals-bounces@lists.osgeo.org \
                [mailto:mapguide-internals-bounces@lists.osgeo.org] On Behalf Of \
                Steve Dang
Sent: Monday, August 18, 2008 2:15 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 53 Review

Comma or tab was one of my choices I had in mind but unfortunately they are not \
reserved characters for class names because FDO separates schema and class name by \
":", and class and property name by ".".

Thanks,
Steve.

-----Original Message-----
From: mapguide-internals-bounces@lists.osgeo.org \
                [mailto:mapguide-internals-bounces@lists.osgeo.org] On Behalf Of Zac \
                Spitzer
Sent: Monday, August 18, 2008 12:59 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] MapGuide RFC 53 Review

Is there a reason for using a period and not a comma to seperate class names?

CLASSNAMES=Class1.Class2.Class3
  vs
CLASSNAMES=Class1,Class2,Class3

z


On Tue, Aug 19, 2008 at 4:39 AM, Jason Birch <Jason.Birch@nanaimo.ca> wrote:
> Can't comment on the implementation, but this is an important addition
> to MapGuide when interacting with DBMS-based feature sources.
> 
> I'm assuming that you will be testing the command capabilities to
> determine which providers to call the old mechanism for?
> 
> Jason
> 
> -----Original Message-----
> From: Steve Dang
> Subject: [mapguide-internals] MapGuide RFC 53 Review
> 
> Please review MapGuide RFC 53 (DescribeSchema, DescribeSchemaAsXml,
> GetSchemas and GetClasses API Enhancements),
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc53, and send any comment
> to this mail list.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 



--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


[prev in list] [next in list] [prev in thread] [next in thread]