1,020 Matching Annotations
- Oct 2021
-
dev.to dev.to
-
make our components larger
Overhead of FRP engines baked into WCs may indeed add up to a substantial size by Web standards.
-
convolute the code
How so?
-
-
webcomponents.dev webcomponents.dev
-
Notes
I'm curious to see how an example case of 30 ReactJS components with different ReactJS versions are going to look like. Having dependency on a different version of a library is the most likely scenario in practice. How will dependencies be managed in this case?
-
All components will share the library code
How does it work?
-
-
www.force11.org www.force11.org
-
Automatic linking of other resources and discussions
What problem is it meant to solve?
-
Portability across hosting services
What is meant to be hosted?
-
Rich connections to other online resources
-
Discovery and linking of annotations across different content instances (html vs. pdf)
<anchor> -
Rich
What is meant by "rich"?
-
Many different clients that support basic functionality
Are there any implementations?
-
Tags that help filter, sort, identify annotations by date, relevance, topic…factual annotations vs. comments (pragmatic vs. true semantic interoperability)
Perhaps RDF is a good fit for it.
-
People identifiers within groups and globally (SSO including with ORCID), w/ Twitter, other SM groups
Can this problem of identifying people be solved by WebID?
-
repositories
What is it?
-
versions of content
What is meant by it?
-
Selection
What is it?
-
ability to evolve permissions on selected annotations
How to control who's allowed to evolve?
-
branded
What is it?
-
authoritative
What is it?
-
private group
What is it?
-
but
Why "but"?
-