what to do
with the attribute will simply store it. The existing link attribute
syntax is probably better than my proposed syntax as it wouldn't break
any other wikis that weren't using the GraphReferenceManager (and any
sub-processors that handle the ontology-related stuff), i.e., the pages
Hi Murray,
Just a quick note, current wiki syntax allows a second | in order to
support link attributes, e.g., [Page|MyPage|title='Page']. Markdown syntax
allows the same thing using [](){}, IIRC, so perhaps
[Subject|Predicate::Object] (or something like that) could be used instead?
cheers,
juan
On 2022/07/29 6:01, Juan Pablo Santos Rodríguez wrote:
Hi Murray,
ahh ok, now I see, so I guess we could start by making the reference
manager pluggable through a wiki property, so anyone wishing to use it can
do so easily.
Hi Juan Pablo,
The one pseudo-proposal I'm considering adding to the
gt;
> On 26/07/22 6:30 am, Juan Pablo Santos Rodríguez wrote:
> > Hi Murray!
> >
> > nice to see you on the dev list again :-)
>
> Yes, thanks, good to see you as well. Many years... .. .
>
> > lots of interesting points on your email, my POV on them:
> >
On 26/07/22 6:30 am, Juan Pablo Santos Rodríguez wrote:
Hi Murray!
nice to see you on the dev list again :-)
Yes, thanks, good to see you as well. Many years... .. .
lots of interesting points on your email, my POV on them:
- re. GraphReferenceManager: I fail to see how it works
Hi Murray!
nice to see you on the dev list again :-)
lots of interesting points on your email, my POV on them:
- re. GraphReferenceManager: I fail to see how it works, would you mind
sharing a concrete example? it is not clear to me if it needs a syntax
change or not, or if the current syntax
re
of links between Pages, Attachments, as well as external links. With some
default predicates that could be expanded so that wiki links could take the
form of subject-predicate-object, i.e., actual tuples. The implementation is
called GraphReferenceManager.
A link in this system co
