Reputation
1,899
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
7 20
Impact
~13k people reached

Jan
22
revised Preventing Keys from appearing in Query Output (+ the casting of Ascending/Descending operators)
added 87 characters in body
Jan
22
revised Preventing Keys from appearing in Query Output (+ the casting of Ascending/Descending operators)
added 87 characters in body
Jan
22
revised Preventing Keys from appearing in Query Output (+ the casting of Ascending/Descending operators)
added 87 characters in body
Jan
22
comment Preventing Keys from appearing in Query Output (+ the casting of Ascending/Descending operators)
forgot to accept, but as part of doing so now, for quick reference for others, perhaps you could include the "obvious" solution given in the first comment as the first line in your answer?
Jan
22
accepted Preventing Keys from appearing in Query Output (+ the casting of Ascending/Descending operators)
Jan
20
comment How to organically build up nested associations?
v.useful, succinct solution of what would seem to be a common idiom (perhaps justifying a system implementation to accommodate the OP's initial tendency: peopleFacts[["bob","hair","Length"]] = "red") Related to 2249 and implements the advocated use of Part to "Creatively Set" values in List`s/Association`s (or with operator form peopleFacts @= CreativeSet[{"bob", "hair", "Length"}, "red"] where CreativeSet[pos_,value_] := Function[a,RecurAssocMerge[a, pos,value]])
Jan
10
comment What is the recommended writing style for WDC pages?
The first style tends to act as a narrative on the subject area whereas the second style tends to narrate functions' capabilities/implementations. I find both useful - I've learnt new things in new domains via Mathematica functionality but equally, in more familiar areas I appreciate a focus on a function's scope/implementation. A sense of both can be given through sequencing examples but as a rule, I prefer the second approach in the "Function" pages and the first approach in the "Guide"/"Tutorial" pages.
Jan
10
comment Resolving my Entity* Crisis
Another example: EntityValue["WolframLanguageSymbol","EntityClasses"] gives supposedly all the entity classes for the EntityType WolframLanguageSymbol but not it seems EntityClass["WolframLanguageSymbol",{"FunctionalityArea","PlottingFunctions"}] referenced elsewhere? Another example: XXData output conflicts with the Entity framework not just in naming but in conflicting values as alluded to here
Jan
10
comment Resolving my Entity* Crisis
... EntityValue[Entity["Volcano","Kos"],"Elevation"] , 1) EntityValue[Entity["Volcano","Kos"],"Elevation","EntityPropertyAssociation"] seems reasonable as per your answer and the docs, while 2) EntityValue[Entity["Volcano","Kos"],"EntityPropertyAssociation"] doesn't but 1) produces Missing[]'s, while 2) is in the docs (UnitConvert in "Scope") but doesn't evaluate to its claimed output ...
Jan
10
comment Resolving my Entity* Crisis
Thanks for this; yes the picture is becoming clearer and the raising of EntityValue as a salient touchstone is certainly useful for constructing a broader narrative that IMO could more compellingly convey WDF's potential. I guess it makes it difficult when inconsistencies/bugs remain more commonly than one is used to (perhaps inevitably so given the audacious scope being attempted). Disentangling Missing responses as indicative of either missing understanding or else missing implementation/curation is an ongoing chore. For example, after ...
Jan
8
comment How does thing[“property”] syntax work?
@M.R. or @rhennigan: Does/did this implement the desired idiom as it seems somewhat different from PredictorFunction? For example, the FullForm of PredictorFunction contains not just the appearance related to BoxForm`ArrangeSummaryBox but also other information about, and for the running of, the model - a feature that would seem fundamental to this object-like approach?
Jan
6
awarded  Nice Question
Jan
6
comment Resolving my Entity* Crisis
Length@CountryData["Properties"] ( 223 ) while Length@EntityProperties[Entity["Country", "UnitedStates"]] ( 749 ) first noticed here
Jan
6
revised Resolving my Entity* Crisis
better flow
Jan
6
comment Resolving my Entity* Crisis
This helps. Part of the issue is looking for a "everything is an expression" visualization but WDF seems more nuanced. I'm visualizing: a concept as a tree root, its children as units (Entities). Concepts have properties realizable by its units with units also having properties beyond those associated with its concept (e.g. Country concept and United States unit) which raises the question of how the *Data fit in - perhaps "*" naming the concept while offering another syntax for realizing a value for its units/Entities and/or for defining an EntityClass amongst its units/Entities.
Jan
4
revised W|A or Mathematica for CountryData?
deleted 31 characters in body
Jan
4
revised W|A or Mathematica for CountryData?
edited body
Jan
4
asked W|A or Mathematica for CountryData?
Jan
2
awarded  Nice Answer
Jan
2
comment V10's Operator Forms - what are they good for?
@alancalvitti yes or even Select[Not@*MemberQ@a]@{{a, b, c}, a, z, {x, y, z}} to preserve the linguistic order but would be nice to have something similar for "compositions" where the operand is at greater depth.