* = #q=-/cube hides object cube only in the root-scene (not nested cube objects)
#q=-cube hides both object cube in the root-scene <b>AND</b> nested skybox objects |

1. create an associative array/object to store query-arguments as objects
2. detect object id's & properties foo:1 and foo (reference regex: /^.*:[><=!]?/ )
3. detect excluders like -foo,-foo:1,-.foo,-/foo (reference regex: /^-/ )
4. detect root selectors like /foo (reference regex: /^[-]?\// )
5. detect class selectors like .foo (reference regex: /^[-]?class$/ )
6. detect number values like foo:1 (reference regex: /^[0-9\.]+$/ )
7. expand aliases like .foo into class:foo
8. for every query token split string on :
9. create an empty array rules
10. then strip key-operator: convert "-foo" into "foo"
11. add operator and value to rule-array
12. therefore we we set id to true or false (false=excluder -)
13. and we set root to true or false (true=/ root selector is present)
14. we convert key '/foo' into 'foo'
15. finally we add the key/value to the store like store.foo = {id:false,root:true} e.g.

An example query-parser (which compiles to many languages) can be found here

Example: ://foo.com/my3d.gltf#pos=1,0,0&prio=-5&t=0,100

• utf-8 is supported by default
• hashtagbibs are expanded to bibtags
• lines matching regex ^@ will automatically get filtered out, in order to:
• links between textual/spatial objects can automatically be detected
• bibtag appendices (visual-meta can be interpreted e.g.

for more info on this mimetype see bibs

• out-of-the-box (de)multiplex human text and metadata in one go (see the core principle)
• no network-overhead for metadata (see the core principle)
• ensuring high FPS: HTML/RDF historically is too 'requesty'/'parsy' for game studios
• rich send/receive/copy-paste everywhere by default, metadata being retained (see the core principle)
• netto result: less webservices, therefore less servers, and overall better FPS in XR

This significantly expands expressiveness and portability of human tagged text, by postponing machine-concerns to the end of the human text in contrast to literal interweaving of content and markupsymbols (or extra network requests, webservices e.g.).

additional tagging using bibs: to tag spatial object note_canvas with 'todo', the enduser can type or speak @note_canvas@todo

1. When the user surfs to https://.../index.gltf#rentalhouse the XR Fragments-parser points the enduser to the rentalhouse object, and can show contextual info about it.
2. When (partial) remote content is embedded thru XR Fragment queries (see XR Fragment queries), indirectly related metadata can be embedded along.

"When a car breaks down, the ones without turbosupercharger are easier to fix"

1. <b id="frictionless-copy-paste">frictionless copy/pasting</b> (by humans) of (unobtrusive) content AND metadata
2. an introspective 'sketchpad' for metadata, which can (optionally) mature into RDF later

To keep XR Fragments a lightweight spec, BibTeX is used for rudimentary text/spatial tagging (not JSON, RDF or a scripting language because they're harder to write/speak/repair.).

1. The XR Fragments spec does not aim to harden the BiBTeX format
2. respect multi-line BibTex values because of the core principle
3. Expand hashtag(bibs) and rulers (like ${visual-meta-start}) according to the hashtagbibs spec
4. BibTeX snippets should always start in the beginning of a line (regex: ^@), hence mimetype text/plain;charset=utf-8;bib=^@

above can be used as a startingpoint for LLVM's to translate/steelman to a more formal form/language.

when an XR browser updates the human text, a quick scan for nonmatching tags (@book{nonmatchingbook e.g.) should be performed and prompt the enduser for deleting them.