There really is no need for the snarky response. You asked a question, I provided an answer. Perhaps not the one you were looking for, but an answer nonetheless. I even went so far as to admit that the documentation could do for clarification, after having read it again… I agree that the documentation on order/placement of the # and ? symbols IS confusing. I’ve already fired off an email to the team (prior to my initial response) indicating that we need to discuss/clarify the Asset Addressing documentation on Monday morning (its Sunday evening here) and referenced this thread.
Your first post does not indicate that you have read beyond the first section and I cannot simply assume you have, given the number of times I’ve been asked questions by those who seemingly have not read much beyond the first sentence on a page let alone the first section. Your first post indicates that you are confused by the existence of a second colon… which, as I pointed out in my initial response, is described just beyond the first section, in the Object References section on the same page you linked to. Perhaps you missed it or perhaps you thought it was a typo (both are easily possible), I don’t know… but there are two colons in the structure example in that section…
[<scheme>:/]<node_path>:<file_path>#<asset_id>[?<property_path>]
... and not because I’ve changed it (see the revisions for yourself). Your comments regarding the “@selection/lBigToe” portion being part of the scheme is what caused me to think you hadn’t read the Object References section… either skimming past it (in the case that @selection is described in a different/later section) or not reading that far yet (in the case that @selection was intuitive to you).
-Rob
