Applications are also free to attach any JSON(LD / RDF) to spatial objects using custom properties (but is not interpreted by this spec).
@@ -509,25 +514,24 @@ The XR Fragment-compatible browser can let the enduser access visual-meta(data)-
+------------------------------------------------------------------------------------+
-Unlike XML or JSON, the typeless, unnested, everything-is-text nature of BibTeX tags is a great advantage for introspection.
-In a way, the RDF project should welcome it as a missing sensemaking precursor to (eventual) extrospective RDF.
+It’s a missing sensemaking precursor to (eventual) extrospective RDF.
BibTeX-appendices are already used in the digital AND physical world (academic books, visual-meta), perhaps due to its terseness & simplicity.
-In that sense, it’s one step up from the .ini fileformat (which has never leaked into the physical book-world):
+In that sense, it’s one step up from the
- frictionless copy/pasting (by humans) of (unobtrusive) content AND metadata
@@ -568,6 +572,12 @@ In that sense, it’s one step up from the .ini fileformat (whi
no |
+
+| paperfriendly |
+bibs |
+no |
+
+
| leaves (dictated) text intact |
yes |
@@ -660,81 +670,121 @@ In that sense, it’s one step up from the .ini fileformat (whi
| nested structures |
-no |
+no (but: BibTex rulers) |
yes |
-XR Text (w. BibTeX) example parser
+XR Text example parser
-Here’s a naive XR Text (de)multiplexer in javascript (which also supports visual-meta start/end-blocks):
+
+- The XR Fragments spec does not aim to harden the BiBTeX format
+- However, respect multi-line BibTex values because of the core principle
+- Expand bibs and rulers (like
${visual-meta-start}) according to the tagbibs spec
+- BibTeX snippets should always start in the beginning of a line (regex: ^@), hence mimetype
text/plain;charset=utf-8;tag=^@
+
+
+Here’s an XR Text (de)multiplexer in javascript, which ticks all the above boxes:
xrtext = {
- decode: {
- text: (str) => {
- let meta={}, text='', last='', data = '';
- str.split(/\r?\n/).map( (line) => {
- if( !data ) data = last === '' && line.match(/^@/) ? line[0] : ''
- if( data ){
- if( line === '' ){
- xrtext.decode.bibtex(data.substr(1),meta)
- data=''
- }else data += `${line}\n`
- }
- text += data ? '' : `${line}\n`
- last=line
+ decode: (str) => {
+ // bibtex: ↓@ ↓<tag|tag{phrase,|{ruler}> ↓property ↓end
+ let pat = [ /@/, /^\S+[,{}]/, /},/, /}/ ]
+ let tags = [], text='', i=0, prop=''
+ var bibs = { regex: /(@[a-zA-Z0-9_+]+@[a-zA-Z0-9_@]+)/g, tags: {}}
+ let lines = str.replace(/\r?\n/g,'\n').split(/\n/)
+ for( let i = 0; !lines[i].match( /^@/ ); i++ ) text += lines[i]+'\n'
+
+ bibtex = lines.join('\n').substr( text.length )
+ bibtex.replace( bibs.regex , (m,k,v) => {
+ tok = m.substr(1).split("@")
+ match = tok.shift()
+ tok.map( (t) => bibs.tags[match] = `@${t}{${match},\n}\n` )
+ })
+ bibtex = Object.values(bibs.tags).join('\n') + bibtex.replace( bibs.regex, '')
+ bibtex.split( pat[0] ).map( (t) => {
+ try{
+ let v = {}
+ if( !(t = t.trim()) ) return
+ if( tag = t.match( pat[1] ) ) tag = tag[0]
+ if( tag.match( /^{.*}$/ ) ) return tags.push({ruler:tag})
+ t = t.substr( tag.length )
+ t.split( pat[2] )
+ .map( kv => {
+ if( !(kv = kv.trim()) || kv == "}" ) return
+ v[ kv.match(/\s?(\S+)\s?=/)[1] ] = kv.substr( kv.indexOf("{")+1 )
+ })
+ tags.push( { k:tag, v } )
+ }catch(e){ console.error(e) }
})
- return {text, meta}
- },
- bibtex: (str,meta) => {
- let st = [meta]
- str
- .split(/\r?\n/ )
- .map( s => s.trim() ).join("\n") // be nice
- .replace( /}@/, "}\n@" ) // to authors
- .replace( /},}/, "},\n}" ) // which struggle
- .replace( /^}/, "\n}" ) // with writing single-line BibTeX
- .split( /\n/ ) //
- .filter( c => c.trim() ) // actual processing:
- .map( (s) => {
- if( s.match(/(^}|-end})/) && st.length > 1 ) st.shift()
- else if( s.match(/^@/) ) st.unshift( st[0][ s.replace(/(-start|,)/g,'') ] = {} )
- else s.replace( /(\w+)\s*=\s*{(.*)}(,)?/g, (m,k,v) => st[0][k] = v )
- })
- return meta
- }
+ return {text, tags}
},
- encode: (text,meta) => {
- if( text === false ){
- if (typeof meta === "object") {
- return Object.keys(meta).map(k =>
- typeof meta[k] == "string"
- ? ` ${k} = {${meta[k]}},`
- : `${ k.match(/[}{]$/) ? k.replace('}','-start}') : `${k},` }\n` +
- `${ xrtext.encode( false, meta[k])}\n` +
- `${ k.match(/}$/) ? k.replace('}','-end}') : '}' }\n`
- .split("\n").filter( s => s.trim() ).join("\n")
- )
- .join("\n")
- }
- return meta.toString();
- }else return `${text}\n${xrtext.encode(false,meta)}`
+ encode: (text,tags) => {
+ let str = text+"\n"
+ for( let i in tags ){
+ let item = tags[i]
+ if( item.ruler ){
+ str += `@${item.ruler}\n`
+ continue;
+ }
+ str += `@${item.k}\n`
+ for( let j in item.v ) str += ` ${j} = {${item.v[j]}}\n`
+ str += `}\n`
+ }
+ return str
}
-
}
-
-var {meta,text} = xrtext.decode.text(str) // demultiplex text & bibtex
-meta['@foo{'] = { "note":"note from the user"} // edit metadata
-xrtext.encode(text,meta) // multiplex text & bibtex back together
+The above (de)multiplexes text/metadata, expands bibs, (de)serializes bibtex (and all fits more or less on one A4 paper)
+
-above can be used as a startingpoint for LLVM’s to translate/steelman to any language.
+above can be used as a startingpoint for LLVM’s to translate/steelman to a more formal form/language.
+str = `
+hello world
+
+@hello@greeting
+@{some-section}
+@flap{
+ asdf = {23423}
+}`
+
+var {tags,text} = xrtext.decode(str) // demultiplex text & bibtex
+tags.find( (t) => t.k == 'flap{' ).v.asdf = 1 // edit tag
+tags.push({ k:'bar{', v:{abc:123} }) // add tag
+console.log( xrtext.encode(text,tags) ) // multiplex text & bibtex back together
+
+
+@{references-start}
+@misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+}
+
+
+The above BibTeX-flavor can be imported, however will be rewritten to Dumb BibTeX, to satisfy rule 2 & 5, as well as the core principle
+
+@visual-meta{
+ version = {1.1},
+ generator = {Author 7.6.2 (1064)},
+ section = {visual-meta-header}
+}
+@misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+ section = {references}
+}
+
+
HYPER copy/paste
The previous example, offers something exciting compared to simple copy/paste of 3D objects or text.
diff --git a/doc/RFC_XR_Fragments.md b/doc/RFC_XR_Fragments.md
index dbbb07a..8c61208 100644
--- a/doc/RFC_XR_Fragments.md
+++ b/doc/RFC_XR_Fragments.md
@@ -265,8 +265,8 @@ This allows instant realtime tagging of objects at various scopes:
This empowers the enduser spatial expressiveness (see [the core principle](#core-principle)): spatial wires can be rendered, words can be highlighted, spatial objects can be highlighted/moved/scaled, links can be manipulated by the user.
The simplicity of appending BibTeX 'tags' (humans first, machines later) is also demonstrated by [visual-meta](https://visual-meta.info) in greater detail.
-1. The XR Browser needs to offer a global setting/control to adjust tag-scope with at least range: `[text, spatial, text+spatial, supra, omni, infinite]`
-1. The XR Browser should always allow the human to view/edit the BibTex metadata manually, by clicking 'toggle metadata' on the 'back' (contextmenu e.g.) of any XR text, anywhere anytime.
+1. The XR Browser needs to adjust tag-scope based on the endusers needs/focus (infinite tagging only makes sense when environment is scaled down significantly)
+1. The XR Browser should always allow the human to view/edit the metadata, by clicking 'toggle metadata' on the 'back' (contextmenu e.g.) of any XR text, anywhere anytime.
> NOTE: infinite matches both 'house' and 'houses' in text, as well as spatial objects with `"class":"house"` or name "house". This multiplexing of id/category is deliberate because of [the core principle](#core-principle).
@@ -280,25 +280,25 @@ The XR Fragment specification bumps the traditional default browser-mimetype
to a green eco-friendly:
-`text/plain;charset=utf-8;bibtex=^@`
+`text/plain;charset=utf-8;bib=^@`
-This indicates that any bibtex metadata starting with `@` will automatically get filtered out and:
+This indicates that [bibs](https://github.com/coderofsalvation/tagbibs) and [bibtags](https://en.wikipedia.org/wiki/BibTeX) matching regex `^@` will automatically get filtered out, in order to:
-* automatically detects textual links between textual and spatial objects
+* automatically detect links between textual/spatial objects
+* detect opiniated bibtag appendices ([visual-meta](https://visual-meta.info) e.g.)
-It's concept is similar to literate programming.
-Its implications are that local/remote responses can now:
+It's concept is similar to literate programming, which empower local/remote responses to:
-* (de)multiplex/repair human text and requestless metadata (see [the core principle](#core-principle))
-* no separated implementation/network-overhead for metadata (see [the core principle](#core-principle))
-* ensuring high FPS: HTML/RDF historically is too 'requesty' for game studios
+* (de)multiplex human text and metadata in one go (see [the core principle](#core-principle))
+* no network-overhead for metadata (see [the core principle](#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](#core-principle))
-* less network requests, therefore less webservices, therefore less servers, and overall better FPS in XR
+* netto result: less webservices, therefore less servers, and overall better FPS in XR
-> This significantly expands expressiveness and portability of human 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.).
+> 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.).
For all other purposes, regular mimetypes can be used (but are not required by the spec).
-To keep XR Fragments a lightweight spec, BibTeX is used for text-spatial object mappings (not a scripting language or RDF e.g.).
+To keep XR Fragments a lightweight spec, BibTeX is used for text/spatial tagging (not a scripting language or RDF e.g.).
> Applications are also free to attach any JSON(LD / RDF) to spatial objects using custom properties (but is not interpreted by this spec).
@@ -343,21 +343,20 @@ Example:
+------------------------------------------------------------------------------------+
```
-Attaching visualmeta as `src` metadata to the (root) scene-node hints the XR Fragment browser.
-3D object names and classes map to `name` of visual-meta glossary-entries.
+3D object names and/or classes map to `name` of visual-meta glossary-entries.
This allows rich interaction and interlinking between text and 3D objects:
-1. When the user surfs to https://.../index.gltf#AI the XR Fragments-parser points the enduser to the AI object, and can show contextual info about it.
-2. When (partial) remote content is embedded thru XR Fragment queries (see XR Fragment queries), its related visual-meta can be embedded along.
+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.
-## BibTeX as lowest common denominator for tagging/triples
+## Bibs-enabled BibTeX: lowest common denominator for tagging/triples
> "When a car breaks down, the ones **without** turbosupercharger are easier to fix"
Unlike XML or JSON, the typeless, unnested, everything-is-text nature of BibTeX tags is a great advantage for introspection.
-In a way, the RDF project should welcome it as a missing sensemaking precursor to (eventual) extrospective RDF.
+It's a missing sensemaking precursor to (eventual) extrospective RDF.
BibTeX-appendices are already used in the digital AND physical world (academic books, [visual-meta](https://visual-meta.info)), perhaps due to its terseness & simplicity.
-In that sense, it's one step up from the `.ini` fileformat (which has never leaked into the physical book-world):
+In that sense, it's one step up from the `.ini` fileformat (which has never leaked into the physical world like BibTex):
1. frictionless copy/pasting (by humans) of (unobtrusive) content AND metadata
1. an introspective 'sketchpad' for metadata, which can (optionally) mature into RDF later
@@ -368,6 +367,7 @@ In that sense, it's one step up from the `.ini` fileformat (which has never leak
| structure | fuzzy (sensemaking) | precise |
| space/scope | local | world |
| everything is text (string) | yes | no |
+| paperfriendly | [bibs](https://github.com/coderofsalvation/tagbibs) | no |
| leaves (dictated) text intact | yes | no |
| markup language | just an appendix | ~4 different |
| polyglot format | no | yes |
@@ -383,81 +383,90 @@ In that sense, it's one step up from the `.ini` fileformat (which has never leak
| implementation/network overhead | no | depends |
| used in (physical) books/PDF | yes (visual-meta) | no |
| terse non-verb predicates | yes | no |
-| nested structures | no | yes |
+| nested structures | no (but: BibTex rulers) | yes |
-## XR Text (w. BibTeX) example parser
+## XR Text example parser
-Here's a XR Text (de)multiplexer in javascript (which also consumes start/end-blocks like in visual-meta):
+
+1. The XR Fragments spec does not aim to harden the BiBTeX format
+2. However, respect multi-line BibTex values because of [the core principle](#core-principle)
+3. Expand bibs and rulers (like `${visual-meta-start}`) according to the [tagbibs spec](https://github.com/coderofsalvation/tagbibs)
+4. BibTeX snippets should always start in the beginning of a line (regex: ^@), hence mimetype `text/plain;charset=utf-8;tag=^@`
+
+Here's an XR Text (de)multiplexer in javascript, which ticks all the above boxes:
```
xrtext = {
decode: (str) => {
- let meta={}, text='', bibtex = [], cur = meta, section = ''
- regex= {
- bibtex: /^@/,
- section: { start: /@{(\S+)-start}/, suffix: /-(start|end)/},
- prop: { key: /=.*?{/ , stop: /},/ },
- tag: { start: /^@\S+[{,}]$/, stop: /}/ }
- }
- let reset = () => { bibtex = []; cur = meta }
- str.split(/\r?\n/).map( (line) => {
- if( Object.keys(meta).length == 0 && !line.match(regex.bibtex) )
- text += line+'\n'
- if( line.match(regex.section.start) )
- section = line.match(regex.section.start)
- if( bibtex.length ){
- bibtex.push(line)
- token = bibtex.join('')
- if( token.match( regex.prop.key ) && token.match(/},/) ){
- value = token.substr( token.indexOf('{')+1, token.lastIndexOf('}') )
- key = token.replace(/=.*/,'').trim()
- cur[ key ] = value.replace(regex.prop.stop,'').trim()
- token = token.lastIndexOf('}') == token.length-1
- ? ''
- : token.substr( token.lastIndexOf('},')+2 )
- bibtex = [ token + ' ']
- }else if( token.match(regex.tag.stop) ) reset()
- }else if( line.trim().match(regex.bibtex) ){
- bibtex = [' ']
- key = line.trim().match(regex.tag.start)[0]
- if( key.match(regex.section.suffix) ) return
- cur = ( cur[ key ] = {} )
- if( section ){
- cur.section = section[0].replace(regex.section.suffix,'')
- .replace(/[@}{]/g,'')
- }
- }
+ // bibtex: ↓@ ↓ ↓property ↓end
+ let pat = [ /@/, /^\S+[,{}]/, /},/, /}/ ]
+ let tags = [], text='', i=0, prop=''
+ var bibs = { regex: /(@[a-zA-Z0-9_+]+@[a-zA-Z0-9_@]+)/g, tags: {}}
+ let lines = str.replace(/\r?\n/g,'\n').split(/\n/)
+ for( let i = 0; !lines[i].match( /^@/ ); i++ ) text += lines[i]+'\n'
+
+ bibtex = lines.join('\n').substr( text.length )
+ bibtex.replace( bibs.regex , (m,k,v) => {
+ tok = m.substr(1).split("@")
+ match = tok.shift()
+ tok.map( (t) => bibs.tags[match] = `@${t}{${match},\n}\n` )
+ })
+ bibtex = Object.values(bibs.tags).join('\n') + bibtex.replace( bibs.regex, '')
+ bibtex.split( pat[0] ).map( (t) => {
+ try{
+ let v = {}
+ if( !(t = t.trim()) ) return
+ if( tag = t.match( pat[1] ) ) tag = tag[0]
+ if( tag.match( /^{.*}$/ ) ) return tags.push({ruler:tag})
+ t = t.substr( tag.length )
+ t.split( pat[2] )
+ .map( kv => {
+ if( !(kv = kv.trim()) || kv == "}" ) return
+ v[ kv.match(/\s?(\S+)\s?=/)[1] ] = kv.substr( kv.indexOf("{")+1 )
+ })
+ tags.push( { k:tag, v } )
+ }catch(e){ console.error(e) }
})
- return {text, meta}
+ return {text, tags}
},
- encode: (text,meta) => {
- str = text+"\n"
- for( let i in meta ){
- let item = meta[i]
- str += `${i}\n`
- for( let j in item ) str += ` ${j} = {${item[j]}}\n`
+ encode: (text,tags) => {
+ let str = text+"\n"
+ for( let i in tags ){
+ let item = tags[i]
+ if( item.ruler ){
+ str += `@${item.ruler}\n`
+ continue;
+ }
+ str += `@${item.k}\n`
+ for( let j in item.v ) str += ` ${j} = {${item.v[j]}}\n`
str += `}\n`
}
return str
}
-
}
-
-var {meta,text} = xrtext.decode(str) // demultiplex text & bibtex tags
-meta['@foo{'] = { "note":"note from the user"} // edit metadata
-out = xrtext.encode(text,meta) // multiplex text & bibtex tags back together
```
+The above (de)multiplexes text/metadata, expands bibs, (de)serializes bibtex (and all fits more or less on one A4 paper)
+
> above can be used as a startingpoint for LLVM's to translate/steelman to a more formal form/language.
-1. The XR Fragments spec (de)serializes does not aim to harden the BiBTeX format
-2. Dumb, unnested BiBTeX: always deserialize to a flat lookuptable of tags for speed & simplicity ([core principle](#core-principle))
-3. multi-line BibTex values should be supported
-4. BibTeX snippets should always start in the beginning of a line (regex: ^@), hence mimetype `text/plain;charset=utf-8;bibtex=^@`
-5. Be strict in sending (`encode()`) Dumb Bibtex (start/stop-section becomes a property) (*)
-6. Be liberal in receiving, hence a relatively bigger `decode()` (also supports [visual-meta](https://visual-meta.info) start/stop-sections e.g.)
+```
+str = `
+hello world
+
+@hello@greeting
+@{some-section}
+@flap{
+ asdf = {23423}
+}`
+
+var {tags,text} = xrtext.decode(str) // demultiplex text & bibtex
+tags.find( (t) => t.k == 'flap{' ).v.asdf = 1 // edit tag
+tags.push({ k:'bar{', v:{abc:123} }) // add tag
+console.log( xrtext.encode(text,tags) ) // multiplex text & bibtex back together
+```
```
@{references-start}
diff --git a/doc/RFC_XR_Fragments.txt b/doc/RFC_XR_Fragments.txt
index 0ff7be7..1d1aa9b 100644
--- a/doc/RFC_XR_Fragments.txt
+++ b/doc/RFC_XR_Fragments.txt
@@ -3,7 +3,7 @@
Internet Engineering Task Force L.R. van Kammen
-Internet-Draft 5 September 2023
+Internet-Draft 6 September 2023
Intended status: Informational
@@ -40,7 +40,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
- This Internet-Draft will expire on 8 March 2024.
+ This Internet-Draft will expire on 9 March 2024.
Copyright Notice
@@ -53,7 +53,7 @@ Copyright Notice
-van Kammen Expires 8 March 2024 [Page 1]
+van Kammen Expires 9 March 2024 [Page 1]
Internet-Draft XR Fragments September 2023
@@ -76,17 +76,17 @@ Table of Contents
8. Text in XR (tagging,linking to spatial objects) . . . . . . . 6
8.1. Default Data URI mimetype . . . . . . . . . . . . . . . . 9
8.2. URL and Data URI . . . . . . . . . . . . . . . . . . . . 10
- 8.3. BibTeX as lowest common denominator for tagging/
+ 8.3. Bibs-enabled BibTeX: lowest common denominator for tagging/
triples . . . . . . . . . . . . . . . . . . . . . . . . . 11
- 8.4. XR Text (w. BibTeX) example parser . . . . . . . . . . . 13
- 9. HYPER copy/paste . . . . . . . . . . . . . . . . . . . . . . 14
- 10. XR Fragment queries . . . . . . . . . . . . . . . . . . . . . 15
- 10.1. including/excluding . . . . . . . . . . . . . . . . . . 15
- 10.2. Query Parser . . . . . . . . . . . . . . . . . . . . . . 16
- 10.3. XR Fragment URI Grammar . . . . . . . . . . . . . . . . 17
- 11. Security Considerations . . . . . . . . . . . . . . . . . . . 17
- 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
- 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
+ 8.4. XR Text example parser . . . . . . . . . . . . . . . . . 13
+ 9. HYPER copy/paste . . . . . . . . . . . . . . . . . . . . . . 15
+ 10. XR Fragment queries . . . . . . . . . . . . . . . . . . . . . 16
+ 10.1. including/excluding . . . . . . . . . . . . . . . . . . 16
+ 10.2. Query Parser . . . . . . . . . . . . . . . . . . . . . . 17
+ 10.3. XR Fragment URI Grammar . . . . . . . . . . . . . . . . 18
+ 11. Security Considerations . . . . . . . . . . . . . . . . . . . 18
+ 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
+ 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
@@ -109,7 +109,7 @@ Table of Contents
-van Kammen Expires 8 March 2024 [Page 2]
+van Kammen Expires 9 March 2024 [Page 2]
Internet-Draft XR Fragments September 2023
@@ -165,7 +165,7 @@ Internet-Draft XR Fragments September 2023
-van Kammen Expires 8 March 2024 [Page 3]
+van Kammen Expires 9 March 2024 [Page 3]
Internet-Draft XR Fragments September 2023
@@ -192,6 +192,10 @@ Internet-Draft XR Fragments September 2023
| | is a person who lives in oklahoma") |
+---------------+---------------------------------------------+
| ◻ | ascii representation of an 3D object/mesh |
+ +---------------+---------------------------------------------+
+ | (un)obtrusive | obtrusive: wrapping human text/thought in |
+ | | XML/HTML/JSON obfuscates human text into a |
+ | | salad of machine-symbols and words |
+---------------+---------------------------------------------+
Table 1
@@ -215,17 +219,17 @@ Internet-Draft XR Fragments September 2023
| | | | or class mapping) |
+----------+---------+--------------+----------------------------+
- Table 2
-
- | xyz coordinates are similar to ones found in SVG Media Fragments
-
-van Kammen Expires 8 March 2024 [Page 4]
+van Kammen Expires 9 March 2024 [Page 4]
Internet-Draft XR Fragments September 2023
+ Table 2
+
+ | xyz coordinates are similar to ones found in SVG Media Fragments
+
5. List of metadata for 3D nodes
+=======+========+================+============================+
@@ -269,19 +273,21 @@ Internet-Draft XR Fragments September 2023
| |
+--------------------------------------------------------+
+
+
+
+
+van Kammen Expires 9 March 2024 [Page 5]
+
+Internet-Draft XR Fragments September 2023
+
+
An XR Fragment-compatible browser viewing this scene, allows the end-
user to interact with the buttonA and buttonB.
In case of buttonA the end-user will be teleported to another
location and time in the *current loaded scene*, but buttonB will
*replace the current scene* with a new one, like other.fbx.
-
-
-van Kammen Expires 8 March 2024 [Page 5]
-
-Internet-Draft XR Fragments September 2023
-
-
7. Embedding 3D content
Here's an ascii representation of a 3D scene-graph with 3D objects
@@ -324,20 +330,19 @@ Internet-Draft XR Fragments September 2023
Ideally metadata must come *later with* text, but not *obfuscate* the
text, or *in another* file.
+
+
+
+van Kammen Expires 9 March 2024 [Page 6]
+
+Internet-Draft XR Fragments September 2023
+
+
| Humans first, machines (AI) later (core principle (#core-
| principle)
This way:
-
-
-
-
-van Kammen Expires 8 March 2024 [Page 6]
-
-Internet-Draft XR Fragments September 2023
-
-
1. XR Fragments allows hasslefree XR text
tagging, using BibTeX metadata *at the end of content* (like
visual-meta (https://visual.meta.info)).
@@ -384,12 +389,7 @@ Internet-Draft XR Fragments September 2023
-
-
-
-
-
-van Kammen Expires 8 March 2024 [Page 7]
+van Kammen Expires 9 March 2024 [Page 7]
Internet-Draft XR Fragments September 2023
@@ -445,17 +445,17 @@ Internet-Draft XR Fragments September 2023
-van Kammen Expires 8 March 2024 [Page 8]
+van Kammen Expires 9 March 2024 [Page 8]
Internet-Draft XR Fragments September 2023
- 1. The XR Browser needs to offer a global setting/control to adjust
- tag-scope with at least range: [text, spatial, text+spatial,
- supra, omni, infinite]
+ 1. The XR Browser needs to adjust tag-scope based on the endusers
+ needs/focus (infinite tagging only makes sense when environment
+ is scaled down significantly)
2. The XR Browser should always allow the human to view/edit the
- BibTex metadata manually, by clicking 'toggle metadata' on the
- 'back' (contextmenu e.g.) of any XR text, anywhere anytime.
+ metadata, by clicking 'toggle metadata' on the 'back'
+ (contextmenu e.g.) of any XR text, anywhere anytime.
| NOTE: infinite matches both 'house' and 'houses' in text, as well
| as spatial objects with "class":"house" or name "house". This
@@ -473,48 +473,48 @@ Internet-Draft XR Fragments September 2023
to a green eco-friendly:
- text/plain;charset=utf-8;bibtex=^@
+ text/plain;charset=utf-8;bib=^@
- This indicates that any bibtex metadata starting with @ will
- automatically get filtered out and:
+ This indicates that bibs (https://github.com/coderofsalvation/
+ tagbibs) and bibtags (https://en.wikipedia.org/wiki/BibTeX) matching
+ regex ^@ will automatically get filtered out, in order to:
- * automatically detects textual links between textual and spatial
- objects
+ * automatically detect links between textual/spatial objects
+ * detect opiniated bibtag appendices (visual-meta (https://visual-
+ meta.info) e.g.)
- It's concept is similar to literate programming. Its implications
- are that local/remote responses can now:
+ It's concept is similar to literate programming, which empower local/
+ remote responses to:
- * (de)multiplex/repair human text and requestless metadata (see the
- core principle (#core-principle))
- * no separated implementation/network-overhead for metadata (see the
- core principle (#core-principle))
- * ensuring high FPS: HTML/RDF historically is too 'requesty' for
- game studios
+ * (de)multiplex human text and metadata in one go (see the core
+ principle (#core-principle))
+ * no network-overhead for metadata (see the core principle (#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 (#core-principle))
- * less network requests, therefore less webservices, therefore less
- servers, and overall better FPS in XR
+ * netto result: less webservices, therefore less servers, and
+ overall better FPS in XR
-
-
-van Kammen Expires 8 March 2024 [Page 9]
+van Kammen Expires 9 March 2024 [Page 9]
Internet-Draft XR Fragments September 2023
| This significantly expands expressiveness and portability of human
- | text, by *postponing machine-concerns to the end of the human
- | text* in contrast to literal interweaving of content and
+ | 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.).
For all other purposes, regular mimetypes can be used (but are not
required by the spec).
- To keep XR Fragments a lightweight spec, BibTeX is used for text-
- spatial object mappings (not a scripting language or RDF e.g.).
+ To keep XR Fragments a lightweight spec, BibTeX is used for text/
+ spatial tagging (not a scripting language or RDF e.g.).
| Applications are also free to attach any JSON(LD / RDF) to spatial
| objects using custom properties (but is not interpreted by this
@@ -557,7 +557,7 @@ Internet-Draft XR Fragments September 2023
-van Kammen Expires 8 March 2024 [Page 10]
+van Kammen Expires 9 March 2024 [Page 10]
Internet-Draft XR Fragments September 2023
@@ -575,32 +575,30 @@ Internet-Draft XR Fragments September 2023
| }` |
+------------------------------------------------------------------------------------+
- Attaching visualmeta as src metadata to the (root) scene-node hints
- the XR Fragment browser. 3D object names and classes map to name of
- visual-meta glossary-entries. This allows rich interaction and
- interlinking between text and 3D objects:
+ 3D object names and/or classes map to name of visual-meta glossary-
+ entries. This allows rich interaction and interlinking between text
+ and 3D objects:
- 1. When the user surfs to https://.../index.gltf#AI the XR
- Fragments-parser points the enduser to the AI object, and can
- show contextual info about it.
+ 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), its related visual-meta can be
- embedded along.
+ queries (see XR Fragment queries), indirectly related metadata
+ can be embedded along.
-8.3. BibTeX as lowest common denominator for tagging/triples
+8.3. Bibs-enabled BibTeX: lowest common denominator for tagging/triples
| "When a car breaks down, the ones *without* turbosupercharger are
| easier to fix"
Unlike XML or JSON, the typeless, unnested, everything-is-text nature
of BibTeX tags is a great advantage for introspection.
- In a way, the RDF project should welcome it as a missing sensemaking
- precursor to (eventual) extrospective RDF.
+ It's a missing sensemaking precursor to (eventual) extrospective RDF.
BibTeX-appendices are already used in the digital AND physical world
(academic books, visual-meta (https://visual-meta.info)), perhaps due
to its terseness & simplicity.
In that sense, it's one step up from the .ini fileformat (which has
- never leaked into the physical book-world):
+ never leaked into the physical world like BibTex):
1. frictionless copy/pasting (by
humans) of (unobtrusive) content AND metadata
@@ -613,157 +611,219 @@ Internet-Draft XR Fragments September 2023
-van Kammen Expires 8 March 2024 [Page 11]
+
+
+van Kammen Expires 9 March 2024 [Page 11]
Internet-Draft XR Fragments September 2023
- +====================+=================+=================+
- | characteristic | UTF8 Plain Text | RDF |
- | | (with BibTeX) | |
- +====================+=================+=================+
- | perspective | introspective | extrospective |
- +--------------------+-----------------+-----------------+
- | structure | fuzzy | precise |
- | | (sensemaking) | |
- +--------------------+-----------------+-----------------+
- | space/scope | local | world |
- +--------------------+-----------------+-----------------+
- | everything is text | yes | no |
- | (string) | | |
- +--------------------+-----------------+-----------------+
- | leaves (dictated) | yes | no |
- | text intact | | |
- +--------------------+-----------------+-----------------+
- | markup language | just an | ~4 different |
- | | appendix | |
- +--------------------+-----------------+-----------------+
- | polyglot format | no | yes |
- +--------------------+-----------------+-----------------+
- | easy to copy/paste | yes | up to |
- | content+metadata | | application |
- +--------------------+-----------------+-----------------+
- | easy to write/ | yes | depends |
- | repair for layman | | |
- +--------------------+-----------------+-----------------+
- | easy to | yes (fits on A4 | depends |
- | (de)serialize | paper) | |
- +--------------------+-----------------+-----------------+
- | infrastructure | selfcontained | (semi)networked |
- | | (plain text) | |
- +--------------------+-----------------+-----------------+
- | freeform tagging/ | yes, terse | yes, verbose |
- | annotation | | |
- +--------------------+-----------------+-----------------+
- | can be appended to | yes | up to |
- | text-content | | application |
- +--------------------+-----------------+-----------------+
- | copy-paste text | yes | up to |
- | preserves metadata | | application |
- +--------------------+-----------------+-----------------+
- | emoji | yes | depends on |
- | | | encoding |
- +--------------------+-----------------+-----------------+
- | predicates | free | semi pre- |
- | | | determined |
+ +================+=====================================+===============+
+ |characteristic |UTF8 Plain Text (with BibTeX) |RDF |
+ +================+=====================================+===============+
+ |perspective |introspective |extrospective |
+ +----------------+-------------------------------------+---------------+
+ |structure |fuzzy (sensemaking) |precise |
+ +----------------+-------------------------------------+---------------+
+ |space/scope |local |world |
+ +----------------+-------------------------------------+---------------+
+ |everything is |yes |no |
+ |text (string) | | |
+ +----------------+-------------------------------------+---------------+
+ |paperfriendly |bibs |no |
+ | |(https://github.com/coderofsalvation/| |
+ | |tagbibs) | |
+ +----------------+-------------------------------------+---------------+
+ |leaves |yes |no |
+ |(dictated) text | | |
+ |intact | | |
+ +----------------+-------------------------------------+---------------+
+ |markup language |just an appendix |~4 different |
+ +----------------+-------------------------------------+---------------+
+ |polyglot format |no |yes |
+ +----------------+-------------------------------------+---------------+
+ |easy to copy/ |yes |up to |
+ |paste | |application |
+ |content+metadata| | |
+ +----------------+-------------------------------------+---------------+
+ |easy to write/ |yes |depends |
+ |repair for | | |
+ |layman | | |
+ +----------------+-------------------------------------+---------------+
+ |easy to |yes (fits on A4 paper) |depends |
+ |(de)serialize | | |
+ +----------------+-------------------------------------+---------------+
+ |infrastructure |selfcontained (plain text) |(semi)networked|
+ +----------------+-------------------------------------+---------------+
+ |freeform |yes, terse |yes, verbose |
+ |tagging/ | | |
+ |annotation | | |
+ +----------------+-------------------------------------+---------------+
+ |can be appended |yes |up to |
+ |to text-content | |application |
+ +----------------+-------------------------------------+---------------+
+ |copy-paste text |yes |up to |
+ |preserves | |application |
+ |metadata | | |
+ +----------------+-------------------------------------+---------------+
-van Kammen Expires 8 March 2024 [Page 12]
+van Kammen Expires 9 March 2024 [Page 12]
Internet-Draft XR Fragments September 2023
- +--------------------+-----------------+-----------------+
- | implementation/ | no | depends |
- | network overhead | | |
- +--------------------+-----------------+-----------------+
- | used in (physical) | yes (visual- | no |
- | books/PDF | meta) | |
- +--------------------+-----------------+-----------------+
- | terse non-verb | yes | no |
- | predicates | | |
- +--------------------+-----------------+-----------------+
- | nested structures | no | yes |
- +--------------------+-----------------+-----------------+
+ |emoji |yes |depends on |
+ | | |encoding |
+ +----------------+-------------------------------------+---------------+
+ |predicates |free |semi pre- |
+ | | |determined |
+ +----------------+-------------------------------------+---------------+
+ |implementation/ |no |depends |
+ |network overhead| | |
+ +----------------+-------------------------------------+---------------+
+ |used in |yes (visual-meta) |no |
+ |(physical) | | |
+ |books/PDF | | |
+ +----------------+-------------------------------------+---------------+
+ |terse non-verb |yes |no |
+ |predicates | | |
+ +----------------+-------------------------------------+---------------+
+ |nested |no (but: BibTex rulers) |yes |
+ |structures | | |
+ +----------------+-------------------------------------+---------------+
- Table 5
+ Table 5
-8.4. XR Text (w. BibTeX) example parser
+8.4. XR Text example parser
- Here's a naive XR Text (de)multiplexer in javascript (which also
- supports visual-meta start/end-blocks):
+ 1. The XR Fragments spec does not aim to harden the BiBTeX format
+ 2. However, respect multi-line BibTex values because of the core
+ principle (#core-principle)
+ 3. Expand bibs and rulers (like ${visual-meta-start}) according to
+ the tagbibs spec (https://github.com/coderofsalvation/tagbibs)
+ 4. BibTeX snippets should always start in the beginning of a line
+ (regex: ^@), hence mimetype text/plain;charset=utf-8;tag=^@
+
+ Here's an XR Text (de)multiplexer in javascript, which ticks all the
+ above boxes:
xrtext = {
- decode: {
- text: (str) => {
- let meta={}, text='', last='', data = '';
- str.split(/\r?\n/).map( (line) => {
- if( !data ) data = last === '' && line.match(/^@/) ? line[0] : ''
- if( data ){
- if( line === '' ){
- xrtext.decode.bibtex(data.substr(1),meta)
- data=''
- }else data += `${line}\n`
- }
- text += data ? '' : `${line}\n`
- last=line
- })
- return {text, meta}
- },
- bibtex: (str,meta) => {
- let st = [meta]
- str
- .split(/\r?\n/ )
- .map( s => s.trim() ).join("\n") // be nice
- .replace( /}@/, "}\n@" ) // to authors
- .replace( /},}/, "},\n}" ) // which struggle
- .replace( /^}/, "\n}" ) // with writing single-line BibTeX
- .split( /\n/ ) //
- .filter( c => c.trim() ) // actual processing:
+ decode: (str) => {
+ // bibtex: ↓@ ↓ ↓property ↓end
+ let pat = [ /@/, /^\S+[,{}]/, /},/, /}/ ]
+ let tags = [], text='', i=0, prop=''
+ var bibs = { regex: /(@[a-zA-Z0-9_+]+@[a-zA-Z0-9_@]+)/g, tags: {}}
+ let lines = str.replace(/\r?\n/g,'\n').split(/\n/)
+ for( let i = 0; !lines[i].match( /^@/ ); i++ ) text += lines[i]+'\n'
+
+ bibtex = lines.join('\n').substr( text.length )
+ bibtex.replace( bibs.regex , (m,k,v) => {
+ tok = m.substr(1).split("@")
-van Kammen Expires 8 March 2024 [Page 13]
+van Kammen Expires 9 March 2024 [Page 13]
Internet-Draft XR Fragments September 2023
- .map( (s) => {
- if( s.match(/(^}|-end})/) && st.length > 1 ) st.shift()
- else if( s.match(/^@/) ) st.unshift( st[0][ s.replace(/(-start|,)/g,'') ] = {} )
- else s.replace( /(\w+)\s*=\s*{(.*)}(,)?/g, (m,k,v) => st[0][k] = v )
+ match = tok.shift()
+ tok.map( (t) => bibs.tags[match] = `@${t}{${match},\n}\n` )
+ })
+ bibtex = Object.values(bibs.tags).join('\n') + bibtex.replace( bibs.regex, '')
+ bibtex.split( pat[0] ).map( (t) => {
+ try{
+ let v = {}
+ if( !(t = t.trim()) ) return
+ if( tag = t.match( pat[1] ) ) tag = tag[0]
+ if( tag.match( /^{.*}$/ ) ) return tags.push({ruler:tag})
+ t = t.substr( tag.length )
+ t.split( pat[2] )
+ .map( kv => {
+ if( !(kv = kv.trim()) || kv == "}" ) return
+ v[ kv.match(/\s?(\S+)\s?=/)[1] ] = kv.substr( kv.indexOf("{")+1 )
+ })
+ tags.push( { k:tag, v } )
+ }catch(e){ console.error(e) }
})
- return meta
- }
+ return {text, tags}
},
- encode: (text,meta) => {
- if( text === false ){
- if (typeof meta === "object") {
- return Object.keys(meta).map(k =>
- typeof meta[k] == "string"
- ? ` ${k} = {${meta[k]}},`
- : `${ k.match(/[}{]$/) ? k.replace('}','-start}') : `${k},` }\n` +
- `${ xrtext.encode( false, meta[k])}\n` +
- `${ k.match(/}$/) ? k.replace('}','-end}') : '}' }\n`
- .split("\n").filter( s => s.trim() ).join("\n")
- )
- .join("\n")
- }
- return meta.toString();
- }else return `${text}\n${xrtext.encode(false,meta)}`
+ encode: (text,tags) => {
+ let str = text+"\n"
+ for( let i in tags ){
+ let item = tags[i]
+ if( item.ruler ){
+ str += `@${item.ruler}\n`
+ continue;
+ }
+ str += `@${item.k}\n`
+ for( let j in item.v ) str += ` ${j} = {${item.v[j]}}\n`
+ str += `}\n`
+ }
+ return str
}
-
}
-var {meta,text} = xrtext.decode.text(str) // demultiplex text & bibtex
-meta['@foo{'] = { "note":"note from the user"} // edit metadata
-xrtext.encode(text,meta) // multiplex text & bibtex back together
+ The above (de)multiplexes text/metadata, expands bibs, (de)serializes
+ bibtex (and all fits more or less on one A4 paper)
| above can be used as a startingpoint for LLVM's to translate/
- | steelman to any language.
+ | steelman to a more formal form/language.
+
+
+
+
+
+
+
+
+van Kammen Expires 9 March 2024 [Page 14]
+
+Internet-Draft XR Fragments September 2023
+
+
+str = `
+hello world
+
+@hello@greeting
+@{some-section}
+@flap{
+ asdf = {23423}
+}`
+
+var {tags,text} = xrtext.decode(str) // demultiplex text & bibtex
+tags.find( (t) => t.k == 'flap{' ).v.asdf = 1 // edit tag
+tags.push({ k:'bar{', v:{abc:123} }) // add tag
+console.log( xrtext.encode(text,tags) ) // multiplex text & bibtex back together
+
+ @{references-start}
+ @misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+ }
+
+ The above BibTeX-flavor can be imported, however will be rewritten to
+ Dumb BibTeX, to satisfy rule 2 & 5, as well as the core principle
+ (#core-principle)
+
+ @visual-meta{
+ version = {1.1},
+ generator = {Author 7.6.2 (1064)},
+ section = {visual-meta-header}
+ }
+ @misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+ section = {references}
+ }
9. HYPER copy/paste
@@ -774,18 +834,17 @@ xrtext.encode(text,meta) // multiplex text & bibtex ba
ways:
1. time/space: 3D object (current animation-loop)
- 2. text: TeXt object (including BibTeX/visual-meta if any)
- 3. interlinked: Collected objects by visual-meta tag
-
-
-van Kammen Expires 8 March 2024 [Page 14]
+van Kammen Expires 9 March 2024 [Page 15]
Internet-Draft XR Fragments September 2023
+ 2. text: TeXt object (including BibTeX/visual-meta if any)
+ 3. interlinked: Collected objects by visual-meta tag
+
10. XR Fragment queries
Include, exclude, hide/shows objects using space-separated strings:
@@ -831,17 +890,17 @@ Internet-Draft XR Fragments September 2023
| | property) |
+----------+-------------------------------------------------+
| - | removes/hides object(s) |
- +----------+-------------------------------------------------+
- | : | indicates an object-embedded custom property |
- | | key/value |
-van Kammen Expires 8 March 2024 [Page 15]
+van Kammen Expires 9 March 2024 [Page 16]
Internet-Draft XR Fragments September 2023
+ +----------+-------------------------------------------------+
+ | : | indicates an object-embedded custom property |
+ | | key/value |
+----------+-------------------------------------------------+
| . | alias for "class" :".foo" equals class:foo |
+----------+-------------------------------------------------+
@@ -886,18 +945,18 @@ Internet-Draft XR Fragments September 2023
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'
-van Kammen Expires 8 March 2024 [Page 16]
+van Kammen Expires 9 March 2024 [Page 17]
Internet-Draft XR Fragments September 2023
+ 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.
@@ -946,7 +1005,4 @@ Internet-Draft XR Fragments September 2023
-
-
-
-van Kammen Expires 8 March 2024 [Page 17]
+van Kammen Expires 9 March 2024 [Page 18]
diff --git a/doc/RFC_XR_Fragments.xml b/doc/RFC_XR_Fragments.xml
index 8826f55..5acc25c 100644
--- a/doc/RFC_XR_Fragments.xml
+++ b/doc/RFC_XR_Fragments.xml
@@ -129,6 +129,11 @@ This also means that the repair-ability of machine-matters should be human frien
◻ |
ascii representation of an 3D object/mesh |
+
+
+| (un)obtrusive |
+obtrusive: wrapping human text/thought in XML/HTML/JSON obfuscates human text into a salad of machine-symbols and words |
+
@@ -342,8 +347,8 @@ Ideally metadata must come later with text, but not obf
The simplicity of appending BibTeX 'tags' (humans first, machines later) is also demonstrated by visual-meta in greater detail.
-- The XR Browser needs to offer a global setting/control to adjust tag-scope with at least range: [text, spatial, text+spatial, supra, omni, infinite]
-- The XR Browser should always allow the human to view/edit the BibTex metadata manually, by clicking 'toggle metadata' on the 'back' (contextmenu e.g.) of any XR text, anywhere anytime.
+- The XR Browser needs to adjust tag-scope based on the endusers needs/focus (infinite tagging only makes sense when environment is scaled down significantly)
+- The XR Browser should always allow the human to view/edit the metadata, by clicking 'toggle metadata' on the 'back' (contextmenu e.g.) of any XR text, anywhere anytime.
NOTE: infinite matches both 'house' and 'houses' in text, as well as spatial objects with "class":"house" or name "house". This multiplexing of id/category is deliberate because of the core principle.
@@ -352,26 +357,26 @@ The simplicity of appending BibTeX 'tags' (humans first, machines later) is also
The XR Fragment specification bumps the traditional default browser-mimetype
text/plain;charset=US-ASCII
to a green eco-friendly:
-text/plain;charset=utf-8;bibtex=^@
-This indicates that any bibtex metadata starting with @ will automatically get filtered out and:
+text/plain;charset=utf-8;bib=^@
+This indicates that bibs and bibtags matching regex ^@ will automatically get filtered out, in order to:
-- automatically detects textual links between textual and spatial objects
+- automatically detect links between textual/spatial objects
+- detect opiniated bibtag appendices (visual-meta e.g.)
-It's concept is similar to literate programming.
-Its implications are that local/remote responses can now:
+It's concept is similar to literate programming, which empower local/remote responses to:
-- (de)multiplex/repair human text and requestless metadata (see the core principle)
-- no separated implementation/network-overhead for metadata (see the core principle)
-- ensuring high FPS: HTML/RDF historically is too 'requesty' for game studios
+- (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)
-- less network requests, therefore less webservices, therefore less servers, and overall better FPS in XR
+- netto result: less webservices, therefore less servers, and overall better FPS in XR
-This significantly expands expressiveness and portability of human 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.).
+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.).
For all other purposes, regular mimetypes can be used (but are not required by the spec).
-To keep XR Fragments a lightweight spec, BibTeX is used for text-spatial object mappings (not a scripting language or RDF e.g.).
+To keep XR Fragments a lightweight spec, BibTeX is used for text/spatial tagging (not a scripting language or RDF e.g.).
Applications are also free to attach any JSON(LD / RDF) to spatial objects using custom properties (but is not interpreted by this spec).
@@ -410,25 +415,24 @@ The XR Fragment-compatible browser can let the enduser access visual-meta(data)-
| }` |
+------------------------------------------------------------------------------------+
-Attaching visualmeta as src metadata to the (root) scene-node hints the XR Fragment browser.
-3D object names and classes map to name of visual-meta glossary-entries.
+3D object names and/or classes map to name of visual-meta glossary-entries.
This allows rich interaction and interlinking between text and 3D objects:
-- When the user surfs to https://.../index.gltf#AI the XR Fragments-parser points the enduser to the AI object, and can show contextual info about it.
-- When (partial) remote content is embedded thru XR Fragment queries (see XR Fragment queries), its related visual-meta can be embedded along.
+- 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.
+- When (partial) remote content is embedded thru XR Fragment queries (see XR Fragment queries), indirectly related metadata can be embedded along.
-BibTeX as lowest common denominator for tagging/triples
+Bibs-enabled BibTeX: lowest common denominator for tagging/triples
"When a car breaks down, the ones without turbosupercharger are easier to fix"
Unlike XML or JSON, the typeless, unnested, everything-is-text nature of BibTeX tags is a great advantage for introspection.
-In a way, the RDF project should welcome it as a missing sensemaking precursor to (eventual) extrospective RDF.
+It's a missing sensemaking precursor to (eventual) extrospective RDF.
BibTeX-appendices are already used in the digital AND physical world (academic books, visual-meta), perhaps due to its terseness & simplicity.
-In that sense, it's one step up from the .ini fileformat (which has never leaked into the physical book-world):
+In that sense, it's one step up from the .ini fileformat (which has never leaked into the physical world like BibTex):
- <b id="frictionless-copy-paste">frictionless copy/pasting</b> (by humans) of (unobtrusive) content AND metadata
@@ -468,6 +472,12 @@ In that sense, it's one step up from the .ini fileformat (which has nev
no |
+
+| paperfriendly |
+bibs |
+no |
+
+
| leaves (dictated) text intact |
yes |
@@ -560,77 +570,115 @@ In that sense, it's one step up from the .ini fileformat (which has nev
| nested structures |
-no |
+no (but: BibTex rulers) |
yes |
-XR Text (w. BibTeX) example parser
-Here's a naive XR Text (de)multiplexer in javascript (which also supports visual-meta start/end-blocks):
+XR Text example parser
+
+
+- The XR Fragments spec does not aim to harden the BiBTeX format
+- However, respect multi-line BibTex values because of the core principle
+- Expand bibs and rulers (like ${visual-meta-start}) according to the tagbibs spec
+- BibTeX snippets should always start in the beginning of a line (regex: ^@), hence mimetype text/plain;charset=utf-8;tag=^@
+
+Here's an XR Text (de)multiplexer in javascript, which ticks all the above boxes:
xrtext = {
- decode: {
- text: (str) => {
- let meta={}, text='', last='', data = '';
- str.split(/\r?\n/).map( (line) => {
- if( !data ) data = last === '' && line.match(/^@/) ? line[0] : ''
- if( data ){
- if( line === '' ){
- xrtext.decode.bibtex(data.substr(1),meta)
- data=''
- }else data += `${line}\n`
- }
- text += data ? '' : `${line}\n`
- last=line
+ decode: (str) => {
+ // bibtex: ↓@ ↓<tag|tag{phrase,|{ruler}> ↓property ↓end
+ let pat = [ /@/, /^\S+[,{}]/, /},/, /}/ ]
+ let tags = [], text='', i=0, prop=''
+ var bibs = { regex: /(@[a-zA-Z0-9_+]+@[a-zA-Z0-9_@]+)/g, tags: {}}
+ let lines = str.replace(/\r?\n/g,'\n').split(/\n/)
+ for( let i = 0; !lines[i].match( /^@/ ); i++ ) text += lines[i]+'\n'
+
+ bibtex = lines.join('\n').substr( text.length )
+ bibtex.replace( bibs.regex , (m,k,v) => {
+ tok = m.substr(1).split("@")
+ match = tok.shift()
+ tok.map( (t) => bibs.tags[match] = `@${t}{${match},\n}\n` )
+ })
+ bibtex = Object.values(bibs.tags).join('\n') + bibtex.replace( bibs.regex, '')
+ bibtex.split( pat[0] ).map( (t) => {
+ try{
+ let v = {}
+ if( !(t = t.trim()) ) return
+ if( tag = t.match( pat[1] ) ) tag = tag[0]
+ if( tag.match( /^{.*}$/ ) ) return tags.push({ruler:tag})
+ t = t.substr( tag.length )
+ t.split( pat[2] )
+ .map( kv => {
+ if( !(kv = kv.trim()) || kv == "}" ) return
+ v[ kv.match(/\s?(\S+)\s?=/)[1] ] = kv.substr( kv.indexOf("{")+1 )
+ })
+ tags.push( { k:tag, v } )
+ }catch(e){ console.error(e) }
})
- return {text, meta}
- },
- bibtex: (str,meta) => {
- let st = [meta]
- str
- .split(/\r?\n/ )
- .map( s => s.trim() ).join("\n") // be nice
- .replace( /}@/, "}\n@" ) // to authors
- .replace( /},}/, "},\n}" ) // which struggle
- .replace( /^}/, "\n}" ) // with writing single-line BibTeX
- .split( /\n/ ) //
- .filter( c => c.trim() ) // actual processing:
- .map( (s) => {
- if( s.match(/(^}|-end})/) && st.length > 1 ) st.shift()
- else if( s.match(/^@/) ) st.unshift( st[0][ s.replace(/(-start|,)/g,'') ] = {} )
- else s.replace( /(\w+)\s*=\s*{(.*)}(,)?/g, (m,k,v) => st[0][k] = v )
- })
- return meta
- }
+ return {text, tags}
},
- encode: (text,meta) => {
- if( text === false ){
- if (typeof meta === "object") {
- return Object.keys(meta).map(k =>
- typeof meta[k] == "string"
- ? ` ${k} = {${meta[k]}},`
- : `${ k.match(/[}{]$/) ? k.replace('}','-start}') : `${k},` }\n` +
- `${ xrtext.encode( false, meta[k])}\n` +
- `${ k.match(/}$/) ? k.replace('}','-end}') : '}' }\n`
- .split("\n").filter( s => s.trim() ).join("\n")
- )
- .join("\n")
- }
- return meta.toString();
- }else return `${text}\n${xrtext.encode(false,meta)}`
+ encode: (text,tags) => {
+ let str = text+"\n"
+ for( let i in tags ){
+ let item = tags[i]
+ if( item.ruler ){
+ str += `@${item.ruler}\n`
+ continue;
+ }
+ str += `@${item.k}\n`
+ for( let j in item.v ) str += ` ${j} = {${item.v[j]}}\n`
+ str += `}\n`
+ }
+ return str
}
-
}
-
-var {meta,text} = xrtext.decode.text(str) // demultiplex text & bibtex
-meta['@foo{'] = { "note":"note from the user"} // edit metadata
-xrtext.encode(text,meta) // multiplex text & bibtex back together
-above can be used as a startingpoint for LLVM's to translate/steelman to any language.
-
+The above (de)multiplexes text/metadata, expands bibs, (de)serializes bibtex (and all fits more or less on one A4 paper)
+above can be used as a startingpoint for LLVM's to translate/steelman to a more formal form/language.
+
+str = `
+hello world
+
+@hello@greeting
+@{some-section}
+@flap{
+ asdf = {23423}
+}`
+
+var {tags,text} = xrtext.decode(str) // demultiplex text & bibtex
+tags.find( (t) => t.k == 'flap{' ).v.asdf = 1 // edit tag
+tags.push({ k:'bar{', v:{abc:123} }) // add tag
+console.log( xrtext.encode(text,tags) ) // multiplex text & bibtex back together
+
+
+@{references-start}
+@misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+}
+
+The above BibTeX-flavor can be imported, however will be rewritten to Dumb BibTeX, to satisfy rule 2 & 5, as well as the core principle
+
+@visual-meta{
+ version = {1.1},
+ generator = {Author 7.6.2 (1064)},
+ section = {visual-meta-header}
+}
+@misc{emilyHegland/Edgar&Frod,
+ author = {Emily Hegland},
+ title = {Edgar & Frode Hegland, November 2021},
+ year = {2021},
+ month = {11},
+ section = {references}
+}
+
+