asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hillery <>
Subject Re: json vs. JSON
Date Wed, 05 Aug 2015 23:10:10 GMT
On Wed, Aug 5, 2015 at 12:23 PM, Wail Alkowaileet <>

> 1- Line with *start* and *end* attributes give it a sense of "direction"
> which means {"start": [x1,y1], "end": [x2,y2]} != {"start": [x2,y2], "end":
> [x1,y1]}.

I take it that you think that's not correct? Is the ADM "line" explicitly

I had the same concern, honestly. As I said, my proposal was in part a
strawman, and this is exactly the kind of commentary I needed. Not clear
what better names would be... maybe just "a" and "b"?

> 2-Similarly for the rectangles, it seem there are some direction on the
> lines forming the rectangle.

Ditto the above. Just "a" and "b"? I was going to go with something like
"upper-left" and "lower-right", but that would require some logic in the
serializer to determine which was which that I don't think is appropriate.
It also wouldn't allow for a rectangle to be defined by the other two
corners, which I assume ADM is OK with.

> * I would suggest something similar to JTS (Java Topology Suites) where
> there are some generalization like for instance *rectangle *is-a *polygon
> *with
> two-points.

I think - kind of like GeoJSON (see next email) - that this suggestion is a
bit out of scope. That would be a good discussion to have regarding the
actual definition of the ADM types themselves, but it doesn't make sense
for the JSON serialization to somehow coerce the ADM meaning into some
other form. The serialization should be a very thin veneer over the actual
type definition.

aka Chris Hillery

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message