Re: Getting into Annotator

[Randall Leeds]

On Fri, Mar 30, 2018 at 3:31 AM Vincent den Boer  wrote:

> As far as I've understood from the overview, Annotator's main job for now
> is to convert selectors into anchors, and vice-versa, right?


Correct.


> Are there any more docs?


Not yet. Sorry! The API is still stabilizing.


> And since I see no "index" keyin the package.json, is it already meant to
> be used as a package?


It is many packages.

The package.json sets up yarn workspaces and installs common development
tooling used for all the packages. The top level is not, itself, a package
and will never be published to npm. The packages are all in the "packages"
directory.


> If so, what can we expect in terms of API stability?
>

You can expect semantic versioning. We'll break API as often as we need to,
but not carelessly. If we ship a release and you are are actively depending
on an older version, we will welcome your help!

I don't think it's reasonable to expect every volunteer to help maintain
multiple versions, but if there is a demand for back-porting and lingering
support for old versions we will welcome help in doing so.

Re: Getting into Annotator

[Gerben]

On 30.03.2018 12:31, Vincent den Boer wrote:
> Hi everyone,
>
> We're implementing a feature requiring annotations in WorldBrain.io, so I've 
> begun looking into Apache Annotator. Scrounging the wiki and the website, 
> I've 
> come across links to AnnotatorJS and other projects, but have no idea how far 
> Annotator has diverged from AnnotatorJS. Looking at the incubator-annotator I 
> see some packages for anchoring annotations (docs anywhere?), but could 
> anyone 
> give me an idea how everything connects? As far as I've understood from the 
> overview, Annotator's main job for now is to convert selectors into anchors, 
> and vice-versa, right? Are there any more docs? And since I see no "index" 
> key 
> in the package.json, is it already meant to be used as a package? If so, what 
> can we expect in terms of API stability?
>
> Thanks for your time!
>
> Best,
> Vince

Hi Vincent; cool you are looking at Annotator, sorry for the state it is
currently in. ;)

As for the relation with AnnotatorJS: there is overlap in people and
purpose, but it does not share any code. The approach this time is to
make a library of smaller modules, rather than a framework for a whole
annotation workflow. At least, that is my understanding so far.

As you already noticed, we started making packages for creating and
re-anchoring Web Annotation selectors
.
There is a simple demo in the source to show the idea; it can also be
played with here  (while it is
not on the Annotator website yet).

Regarding the readiness: it is not fit for using right away since only
the very basic cases have been implemented, but the setup is all there
to implement missing functionality. It mainly needs some more love to
help get it going!

Let know if you have more questions, want to share your use case, or
have ideas to contribute.

Cheers,

Gerben

Getting into Annotator

[Vincent den Boer]

Hi everyone,

We're implementing a feature requiring annotations in WorldBrain.io, so I've 
begun looking into Apache Annotator. Scrounging the wiki and the website, I've 
come across links to AnnotatorJS and other projects, but have no idea how far 
Annotator has diverged from AnnotatorJS. Looking at the incubator-annotator I 
see some packages for anchoring annotations (docs anywhere?), but could anyone 
give me an idea how everything connects? As far as I've understood from the 
overview, Annotator's main job for now is to convert selectors into anchors, 
and vice-versa, right? Are there any more docs? And since I see no "index" key 
in the package.json, is it already meant to be used as a package? If so, what 
can we expect in terms of API stability?

Thanks for your time!

Best,
Vince

Podling Report Reminder - April 2018

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, April 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/April2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC