Re: URL fragment text directives

[Gerben]

Hi Dinesh! It’s called “URL Fragment Text Directives” these days (for a 
while it was called “Text Fragments”, originally 
“scroll-to-text-fragment”). The Chromium/Chrome team started this a few 
years ago. Other browsers started to follow up, as that happens more 
often.. (in this case, I think it is a helpful development for the web)

Draft Specification: https://wicg.github.io/scroll-to-text-fragment/
Browser support: https://caniuse.com/url-scroll-to-text-fragment
By the way, I made a line-by-line implementation of the spec, but it’s 
somewhat outdated now: <https://code.treora.com/gerben/text-fragments-ts>.

Cheers,
— Gerben

On 02/05/2023 06:35, TB Dinesh wrote:
I found this URL that works on my browser! This is an essential progress of
sorts for this project.
https://thelanguagenerds.com/2019/piraha-language-the-linguistic-anomaly/#:~:text=two%20experiments%20on-,four,-Pirah%C3%A3%20speakers%20that

Dont know how this URL was generated.
If this is a standard we can use (any links?)

thanks for any pointers.

-dinesh


On Sun, Apr 30, 2023 at 7:39 PM Gerben <ger...@treora.com.invalid> wrote:

Hi Udit, glad to hear you are interested in Web Annotation and
Annotator. Sounds like you did some serious research!

Development of Apache Annotator has indeed slowed, mainly due to lack of
time from the initial developers, to an activity level that could well
be called hybernation.. However, it may merely need a motivated person
to wake it up again. Contributions are certainly welcome.

We can jump on a call some day if you are interested. I see you already
joined the chatroom (#annotator on libera.chat), so let’s coordinate
over there.

Answers to your questions below, inline.

Kind regards,
— Gerben

On 18/04/2023 01:40, Udit Desai wrote:
Hello,

I recently stumbled upon the Apache Annotator project while researching
on W3C
Web Annotation spec<https://www.w3.org/annotation/>  and its
implementations.

I tried to gather all the information I could on this project (Mail list,
Github, IRC etc.). But all those channels seemed silent and did not give
clear indication on whether this project is under active development or
not. Is it?

If so, I have further questions:

     - Does this project have any real world examples where it is being
used
     in any large scale system in a production environment?
Not that I know of, but (parts of) it might be. Note that the project
provides a library of quite simple functions — it’s not an all-in-one
framework like its predecessor AnnotatorJS <https://annotatorjs.org/>
is/was. People could just use e.g. its text highlighter function and
ignore any of the other functionality.

     - The latest published version on npm is 0.2.0, which makes me
believe
     that the APIs have not reached a stable milestone. Is that a fair
     assumption?
We’ve indeed been open to the idea of tweaking the API still. I think it
is needlessly complicated now for simple uses cases. A good first step
would be making synchronous API and non-curried functions. (see e.g.
issue #81 <https://github.com/apache/incubator-annotator/issues/81>,
#115 <https://github.com/apache/incubator-annotator/issues/115>)
     - What would it take to bring the project to version 1.0?
A version bump, I guess. ;)

It’s largely a matter of taste when to call something ‘1.0’. Given the
low activity and limited functionality it provides, I would still keep
it at a version <1 to convey this immaturity. (Also, being an incubating
Apache project, perhaps an eventual graduation would be a nice moment to
call it 1.0).

     - Are you open to receive contributions on this, of course with some
     guidance from your team?
Yes, as said above. People may however not have a lot of time for
guidance..
     - The last dev call was probably last year in April 2022. Are they
     happening anymore anywhere else or just haven't happened since then?
That could have been the last dev call indeed..
Regards,
Udit Desai
Mobile: +61-459-343-918