43 Matching Annotations
  1. Jun 2021
  2. stoa.anagora.org stoa.anagora.org
    1. Some conventions may be emerging in a new batch of personal knowledge management tools, or amenable to them; for the duration of this document, we'll refer to these tools as [[personal knowledge management]] tools, [[roam like]] or (preferred as of the time of writing) [[wiki like]].

      It would be incredibly useful to have a list of these [[Roam Research like]] tools so that they can be documented as to what level of input they can/could take and remain compatible from text, to text+[[wiki links]], to the various flavors of markdown up to full HTML perhaps.

      I know a handful are documented at indieweb.org/commonplace_book

  3. May 2021
    1. Whether or not digital gardens should follow any standards is an interesting question.

      What features/functionality should a digital garden have? Is there a canonical list yet?

      I wish more supported Webmention to enable the Memex dream...

    1. why do we have an <img> element? Why not an <icon> element? Or an <include> element? Why not a hyperlink with an include attribute, or some combination of rel values? Why an <img> element? Quite simply, because Marc Andreessen shipped one, and shipping code wins.That’s not to say that all shipping code wins; after all, Andrew and Intermedia and HyTime shipped code too. Code is necessary but not sufficient for success. And I certainly don’t mean to say that shipping code before a standard will produce the best solution.

      Shipping code is necessary, but not sufficient for success.

  4. Apr 2021
  5. Mar 2021
    1. In terms of defining the “open” in open web annotation, I tend to take a standards approach: the Hypothes.is tool is built upon, and our organization advocates for, open standards in web annotation.

      This explanation also highlights an additional idea of open itself. I have heard many in the W3C space criticize the open standard of web annotation arrived at because of the ultimate monoculture of the space. Most of the participants of the process were all related to Hypothes.is in some way and the result was a single product that implemented the standard. To my knowledge no other companies, groups, or individual programmers have separately implemented the standard.

      In this sense, while the "standard" is openly defined, it isn't as open as other standards which were mote slowly evolved and implemented gradually and more broadly by various programming languages and disparate groups.

  6. Feb 2021
  7. Nov 2020
    1. Capacitor's origins lie in Ionic's mission to provide a holistic framework for developing hybrid apps—apps that run on mobile devices, on desktops, and in the browser. It does not only replace Apache Cordova as a “bridge” to native platform access in new Ionic projects but also “provides a consistent, web-focused set of APIs”.
  8. Sep 2020
  9. Jul 2020
    1. A growing number of platforms, vendors, and partners support the AMP Project by providing custom components or offering integration with AMP pages within their platforms.

      I guess AMP is actually open-source software, but it still feels like it's something non-standard. I guess it's just an alternative open standard to the "main" web open standards.

  10. May 2020
  11. Apr 2020
    1. And if the closed platforms prohibited DRM in apps, then the large content providers would simply distribute their own set-top boxes and game consoles as the only way to watch their stuff.

      This sounds a bit naive to me. Who would buy those set-top boxes and game consoles? And do not only consider the United States' and European markets. Wouldn't the large content providers have to adapt to how the web works if they want to reach a broader audience?

    2. embed Netflix content in their own web pages,

      Now that the w3c has recommended eme, Is this possible?

    1. Extensions are built using web technology and can use the same APIs the browser provides to the open web.

      Wonder what they mean by "open web". Web standards, presumably.

  12. Feb 2020
  13. Dec 2019
    1. And other recent developments suggest that doing so could overcome many of the earlier pitfalls of protocol-based systems, potentially creating the best of all words: useful internet services, with competition driving innovation, not controlled solely by giant corporations, but financially sustainable, providing end users with more control over their own data and privacy—and providing mis- and disinformation far fewer opportunities to wreak havoc.

      Some of the issue with this then becomes: "Who exactly creates these standards?" We already have issues with mega-corporations like Google wielding out sized influence in the ability to create new standards like Schema.org or AMP.

      Who is to say they don't tacitly design their standards to directly (and only) benefit themselves?

  14. Nov 2019
  15. Sep 2019
  16. Aug 2019
  17. Mar 2019
  18. webstandards.hhs.gov webstandards.hhs.gov
    1. Usability guidelines This site seems a bit dated in its appearance but still provides the user the opportunity to review usability standards in general, together with a rating of the weight of evidence that supports each assertion. It would take some time to go through all the information available on this site. It is also usable enough that a designer can check up on guidelines while in the middle of designing a specific project. Rating 3/5

  19. Mar 2018
    1. We worked with the industry to launch the open-source Accelerated Mobile Pages Project to improve the mobile web

      There was some collaborative outreach, but AMP is really a Google-driven spec without significant outside input.

      See also: http://ampletter.org/

    2. With AMP Stories, which is now in beta, publishers can combine the speed of AMP with the rich, immersive storytelling of the open web.

      "With AMP Stories, which is now in beta, publishers can combine the speed of AMP with the rich, immersive storytelling of the open web."

      Is this sentence's structure explicitly saying that AMP is not "open web"?!

  20. Apr 2017
    1. Google is adding a Fact Check feature to Google Search and Google News. When fact checks are available from one or more approved publishers, they will appear in the search results.

      One requirement for publishers to be cited is to use the schema.org ClaimReview markup, or the Share the Facts widget.

    1. Dave Winer points out that interoperability of software is important. Don't shun an existing standard just because you think your way is better. If you hate using some standard technology, find or write a module to convert between the standard and your preferred format.

  21. Mar 2017
    1. All views use standards-based HTML templates

      Aurelia's standards focus means our code stays relevant down the road.

    2. One of the strengths of Aurelia is that you can write so much of your application in vanilla JS.

      By sticking close to standards, such as upcoming EcmaScript features, Aurelia code prepares for us for the future. It encourages writing code that will be relevant 2-5 years from now, or perhaps beyond.

  22. Oct 2016
  23. Sep 2016
    1. I’ve found Canvas to be less draconian than I’d been led to expect. More broadly, the LMS ecosystem that’s emerged — based on a standard called Learning Tools Interoperability (LTI), now supported by all the LMS systems — led me to an insight about how the same approach could help unify the emerging ecosystem of annotation systems. Even more broadly, all this has prompted me to reflect on how the modern web platform is both more standardized and more balkanized than ever before.

      ...

      The app I’ve written is a thin layer of glue between two components: Canvas and Hypothes.is. LTI defines how they interact, and I’d be lying if I said it was easy to figure out to get our app to launch inside Canvas and respond back to it. But I didn’t need to be an HTTP, HTML, CSS, JavaScript, or Python wizard to get the job done.

  24. Jan 2016
    1. The prohibition on reporting bugs in systems with DRM makes those bugs last longer, and get exploited harder before they're patched. Last summer, the US Copyright Office collected evidence about DRM interfering with reporting bugs in tractors, cars, medical implants, and critical national infrastructure.
    2. DRM exists to stop users from doing things they want to do and to stop innovative companies from helping users do things they want to do -- or would want to do, if they had the option. Your cable box, for example, will be designed to stop you from recording your favorite shows for long-term storage and viewing on the go.
    3. The World Wide Web Consortium (W3C), the nonprofit body that maintains the Web's core standards, made a terrible mistake in 2013: they decided to add DRM
  25. Dec 2015
  26. Nov 2015
  27. Jan 2014
    1. The process of tying two items together is the important thing.

      Annotations are at the Web’s core.