Content referencing

[Russell Greene]

Local labels also provide a possible maintenance issue, say if a label is
deemed more appropriate to be on a different page, then it would be more
difficult without a complex tracking system to track down where that label
went and update it.

Global labels don't propose this issue because they aren't page-bound; the
system could easily update the reference internally without any work needed.

-Russell

On Wed, Feb 3, 2016 at 3:00 PM Davide Valsecchi <
valsecchi.davide94 at gmail.com> wrote:

> Speaking with Riccardo, we have to carefully considerate if we want to
> create global or "local" labels.
>
> Global label would have a format like:  namespace/label.
> Otherwise local label would be linked to the name of the page:
> page_name/label.
>
> The global alternative has the pro that it would be really useful for
> user, who wouldn't have to remember the page name, but it would be against
> mediawiki structure.
> On the contrary local labels would be only a magic word for anchors,
> usable by ocg, but would be more direct.
>
> Personally I'm for global labels with strict rules for namespaces. Another
> alternative could be using only the root page name.
> For example if I have to link:   Mechanics/Newton/Force/equation1 we could
> use label=Mechanics/equation1.
>
> Davide
>
> 2016-01-31 5:22 GMT+01:00 Russell Greene <russellgreene8 at gmail.com>:
>
>> So the design we decided on was a global database that holds the "labels"
>> that define important concepts/definitions/theorem/etc. These can easily be
>> referenced by doing: <ref label="your label">...</ref>.
>>
>> I have made quite a lot of progress on this. (also see
>> https://phabricator.kde.org/T746)
>>
>> There are a few concerns though:
>>
>> - VisualEditor. We would want to implement a way to let VisualEditor know
>> that this exists.
>> - Breaking references accidentally. This seems like it could become a
>> maintenance burden, but at the same time the system should be smart enough
>> to move references on page moves and warn on page delete.
>>
>> Is this a feature that would be useful? Give me your input.
>>
>> -Russell
>>
>> On Mon, Jan 18, 2016 at 8:48 AM Riccardo Iaconelli <riccardo at kde.org>
>> wrote:
>>
>>> On Monday, January 18, 2016 10:00:37 AM Gianluca Rigoletti wrote:
>>> > However, this method could lead to problems when the
>>> > referencing pages aren't in the same book, so for now I don't know, it
>>> > was just a thought.
>>>
>>> This should be OK, if you don't include references, things will break
>>> (this
>>> also happens logically, if you reference some text that doesn't exist in
>>> the
>>> book). Or, if you are smart enough, you can print out a link (i.e. page
>>> name
>>> with hyperlink to the entity or something similar) that people can look
>>> up for
>>> themselves.
>>>
>>> Instead, I agree that a nice syntax for this intra-wiki reference could
>>> be
>>> something like:
>>> <content-ref page=PageName/EntityName />
>>>
>>> I still don't have any preference for this syntax or what Russell
>>> proposed,
>>> which are very similar.
>>>
>>> The only problem that I can foresee for now (and needs a little thought)
>>> is:
>>>  * what happens if a page gets moved?
>>>  * what happens if the ref gets updated? how do we proceed to do updates
>>> database-wise?
>>>
>>> I don't really have a solution for that, but it is also due to my lack of
>>> knowledge of how MediaWiki does things internally...
>>>
>>> Be also careful with hovering and accessibility, or usage from a
>>> touch-based
>>> device. These interactions are always tricky. :-)
>>>
>>> ...just my two cents!
>>>
>>> For the rest, kudos for your work, this is something we really really
>>> need!
>>>
>>> Bye,
>>> -Riccardo
>>>
>>> _______________________________________________
>>> WikiToLearn-Tech mailing list
>>> WikiToLearn-Tech at kde.org
>>> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>>>
>>
>> _______________________________________________
>> WikiToLearn-Tech mailing list
>> WikiToLearn-Tech at kde.org
>> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/wikitolearn-tech/attachments/20160203/c4ca3934/attachment.html>