- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Tue, 07 Jan 2014 17:24:06 -0500
- To: public-propertygraphs@w3.org
Hi Patrick: I agree that we are staring to see more and more data whose structure fits Property Graphs. I also agree that the models used by vendors are often idiosyncratically different. So, yes, standardization of strings to UTF-8 among other things would be very useful. But if we add support for datatypes we may leave JSON-LD behind and there may be some objection to this. All the best, Ashok On 1/7/2014 4:30 PM, Patrick Durusau wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Greetings! > > There seems little doubt that property graphs are gaining ground but I > am less certain that the interchange of property graphs is quite as > well settled. > > For example, one of the non-participants thus far in the > propertygraphs discussion supports label and property name characters > outside the ASCII character set if and only if each character is > preceded by a back tick. Creating the first family of "back tick" > languages I suppose. > > Could that be transformed? Perhaps. I don't know how you would apply > the various Unicode algorithms since those are dependent upon order i > the original string. (Thinking of zero-spacing characters.) > > Declarations about serializations that mandates the use of UTF-8 would > be a step in the right direction. Possibly enumerate the other aspects > of a property graph in the abstract that may or may not be supported. > > Allow multiple properties on nodes? Edges? Multiple nodes to one edge? > etc. > > Not mandating any serialization but giving serializations an outline > of what they may or may not choose to support. > > I can't imagine serious players using labels and property names that > don't support Unicode. (Remember name characters and start name > characters? Why repeat a mistake?) > > Hope everyone is having a great week! > > Patrick > > - -- > Patrick Durusau > patrick@durusau.net > Technical Advisory Board, OASIS (TAB) > Co-Chair, OpenDocument Format TC (OASIS) > Editor, OpenDocument Format TC, Project Editor ISO/IEC 26300 > Former Chair, V1 - US TAG to JTC 1/SC 34 > Convener, JTC 1/SC 34/WG 3 (Topic Maps) > Co-Editor, ISO 13250-5 (Topic Maps) > > Another Word For It (blog): http://tm.durusau.net > Homepage: http://www.durusau.net > Twitter: patrickDurusau > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJSzHH7AAoJEAudyeI2QFGo/RwP/2NR8MN20+GsmOT48PJPR5y/ > KeZzJAkdxndskojZrtcgpJZvYXt87z43mBD1CWYq3WA1DYN555YXyajBmvpPlrNZ > t03ELwaPHQN/IRlKfz1toYFHBTejv4KiUu8aLmQBwiVMxu1p5MqzweX1rbCh8pWs > QS3Lsl0Sfcaxz4R8KFx6grvLxBtEq+iRDTZW6uavf1vbIcR0ZhBb8jUR8fdzbA51 > XjuxMsRrJPO3t7fBcPvzAgwTrZZ9k0vhikuhFvbWG8Y/IvO2SxyimhKmQ3CmKBRk > 2rIKsFHG1kDF4UJ5nWQ24a+Z8+5+GbzUul/sIx3eYh8scJxQqdq+GcKHaOC3nS+U > eiuM6mtJk3bEiimZlCVsHqhnKkUiwx3k0sQC7LO1U/2j0PKN04blMX/gDgBEiqZL > rZMxEUuQLDV/D7szOBqXX+furgNZ41WhsBGi8W21qvJnX97X7M0HbU+ehGrHq4mO > QQlP0uYhvaM/YGxjmNlMIOvCDkXPpTYcm0HiKYkWu+WVFCgmWm6V6dtLCZETLeYd > 6sY8s2HgBJjOUpP7nekmIiQVRKWkC4OnooyW3tlrS2pMXCkNHnWoEYcL2MU/wy0L > UC5w4fuhxSX7mYR9fYHpEYCyQijg4z3Zt2RvTwYuZuhysc2sMQwXICtqk4S0R3CE > Ixwxwu9mNOEup+2UQgvH > =n9cD > -----END PGP SIGNATURE----- >
Received on Tuesday, 7 January 2014 22:24:38 UTC