[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] Exciting development: XDI graph model documented - please indicate your syntax preferences!
On Apr 11, 2013, at 8:07 PM, Drummond Reed <drummond.reed@xdi.org> wrote:
I remember (but don't have source handy) that attributes vs entities is one of the biggest thing that developers disliked about XML, seeing it as unnecessary complication, that led them to embrace JSON. Another viewpoint is that JSON arrays are like children and JSON objects are like attributes. http://blog.technologyofcontent.com/2010/01/json-vs-xml/
Below I think you say that in XDI attributes can contain other attributes - if so this is not a difference between attributes and entities in XDI. So I am still trying to come up with why they need to be distinguished.
Yes - my idea was that the first and second address lines would continue to be addressable in XDI, even though the two values can potentially be set via a single statement, and also potentially retrieved collectively.
Another example I thought of later was that SQL declaration of fields states them to be of one of its basic types. However semantic specification seems to me to be mostly orthogonal to datatype specification. You can have either of them without the other - you could know that a field is an address, but find it useful to allow various kinds of data in it, string, list of string, number, etc. - or you could have a field which is semantically ambiguous or unspecified, but always a single string - or both or neither
I think it's the best so far for this purpose too. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]