46 Matching Annotations
  1. Last 7 days
    1. Perhaps if everyone reads and writes from their own home on the web, they’re less likely to desecrate their neighbor’s blog because it sticks to their own identity? There’s lots of work to be done certainly, but perhaps we’ll get there by expanding things, opening them up, and giving ourselves some more space to communicate?

      Chris, I like your point about companies opening up, it reminds me Cory Doctorow's discussion of interoperability as a means of fixing the internet.

  2. Apr 2021
    1. Ideally, GitHub would understand rich formats

      I've advocated for a different approach.

      Most of these "rich formats" are, let's just be honest, Microsoft Office file formats that people aren't willing to give up. But these aren't binary formats through-and-through; the OOXML formats are ZIP archives (following Microsoft's "Open Packaging Conventions") that when extracted are still almost entirely simple "files containing lines of text".

      So rather than committing your "final-draft.docx", "for-print.oxps" and what-have-you to the repo, run them through a ZIP extractor then commit that to the repo. Then, just like any other source code repo, include a "build script" for these—which just zips them back up and gives them the appropriate file extension.

      (I have found through experimentation that some of these packages do include some binary files (which I can't recall offhand), but they tend to be small, and you can always come up with a text-based serialization for them, and then rework your build script so it's able to go from that serialization format to the correct binary before zipping everything up.)

  3. Mar 2021
    1. The idea is that many smaller tech companies would allow for more choice between services. This solution is flawed. For one, services like search or social media benefit from network effects. Having large datasets to train on, means search recommendations get better. Having all your friends in one place, means you don’t need five apps to contact them all. I would argue those are all things we like and might lose when Big Tech is broken up. What we want is to be able to leave Facebook and still talk to our friends, instead of having many Facebooks.

      I'd be interested to better understand this concern or critique. I think the goal of smaller, interoperable services is exactly the idea of being able to communicate with our Facebook friends even if we leave Facebook. Perhaps that is an argument for combining deconsolidation with interoperability.

  4. Feb 2021
    1. Do not use *= require in Sass or your other stylesheets will not be able to access the Bootstrap mixins or variables.
    1. Most important, though, is restoring an appreciation for the importance of interoperability in preventing monopolies and promoting technological self-determination for communities and individuals.
  5. Jan 2021
    1. That means enforcing interoperability, so that, for example, payments services on one e-commerce platform can be used seamlessly on a rival one.

      interoperability: (of computer systems or software) able to exchange and make use of information.

  6. Nov 2020
    1. Others have already said how Flutter renders inside a canvas and how it's difficult/impossible for it to interact with other JS libraries (and why would you want to... the whole thing is so different that even the issues are solved by completely different libraries).
    1. It's really helpful that Svelte stores are easy to use in plain JS. We can change a state store over completely to Svelte and make the Angular components subscribe to that store as well without needing to maintain and sync 2 copies of the state.
    1. 1.Austausch von Wissen und Erfahrungen, gegenseitige Unterstützung. 2.Aufbau einer Interessengemscheinaft. Gemeinsame Entwicklung, soweit das mit den unterschiedlichen Programmen möglich ist.3.Einen Software-Standard für Verwaltungssoftware entwickeln (also die Programme zueinander kompatibel zu machen, soweit das möglich ist), damit·man diese Komponenten gemeinsam entwickeln kann·diese später vielleicht sogar untereinander austauschbar oder miteinander kombinierbar sind·neue Programmierer mitmachen können, statt allein von vorne anzufangenBetrifft z.B.:·Datenbankstrukturen·Dateiformate·interne und externe APIs4.Entscheidung für eine Software, die wir zukünftig unterstützen, finanziell und entwicklungstechnisch. Die Software soll durch möglichst viele Solawis und Solawi-Typen nutzen können und soll gleichzeitig modular und selbständig durch die Solawis erweitert werden können.

      Die Beispiele können erweitert werden durch die Vorarbeiten die @yova im internationalen Kontext mit Solidbase und in seiner wissenschaftlichen Abschlussarbeit untersucht hat.

  7. Oct 2020
    1. The Gopher story is a perfect case history for Adversarial Interoperability. The pre-Gopher information landscape was dominated by companies, departments, and individuals who were disinterested in giving users control over their own computing experience and who viewed computing as something that took place in a shared lab space, not in your home or dorm room. Rather than pursuing an argument with these self-appointed Lords of Computing, the Gopher team simply went around them, interconnecting to their services without asking for permission. They didn't take data they weren't supposed to have—but they did make it much easier for the services' nominal users to actually access them.
    2. Today's Web giants want us to believe that they and they alone are suited to take us to wherever we end up next. Having used Adversarial Interoperability as a ladder to attain their rarefied heights, they now use laws to kick the ladder away and prevent the next Microcomputer Center or Tim Berners-Lee from doing to them what the Web did to Gopher, and what Gopher did to mainframes.
  8. Sep 2020
    1. This treatment of thenables allows promise implementations to interoperate, as long as they expose a Promises/A+-compliant then method. It also allows Promises/A+ implementations to “assimilate” nonconformant implementations with reasonable then methods.
    2. the promise specification explicitly does not make a distinction
    1. As you've probably already figured out it's the last output definition that should be by legacy apps. With the above output configuration we allow consuming the component both from a modern app with a Node.js-based environment and from legacy apps.
    2. But what if we want to use it in a legacy app built with for example Bootstrap 3 and lots of jQuery where there's no sign of Node.js? No problem! We'll just use the IIFE build and instantiate the component class through its global constructor:
    1. Rollup is a tool that lets you write your application using ES6 modules, even though you can't publish those modules directly to your users, because native support is only just starting to land in browsers. Rollup compiles your modules into a format that all browsers _do_ understand—a single script file—by, essentially, concatenating files together (while reordering and renaming declarations to preserve scope).
    1. For interoperability with RxJS Observables, the .subscribe method is also allowed to return an object with an .unsubscribe method, rather than return the unsubscription function directly.
  9. Jun 2020
    1. Add fast and low-overhead interoperability with languages like Java, JavaScript, Python and R
  10. May 2020
    1. A standard-setting organization is an industry group that sets common standards for its particular industry to ensure compatibility and interoperability of devices manufactured by different companies.
  11. Mar 2020
  12. Jan 2020
    1. The Web Annotation Data Model specification describes a structured model and format to enable annotations to be shared and reused across different hardware and software platforms.

      The publication of this web standard changed everything. I look forward to true testing of interoperable open annotation. The publication of the standard nearly three years ago was a game changer, but the game is still in progress. The future potential is unlimited!

  13. May 2019
  14. Mar 2019
    1. In a perfect world, the author would sell you a license to the book and you'd just read it on whatever platform suited you. For now, the leading ebook providers are not making this easy so I end up with some titles (and associated annotations) on one platform and other titles on another, which is far more complicated than it needs to be.

  15. May 2018
    1. It should be noted that the number of female founders (and employees) is also significantly higher in social enterprises. According to the State of Social Enterprise Survey (2013), 38% of social ventures are led by women.

      So interesting! Annotating on Alex's annotation here.

  16. Nov 2017
    1. xAPI is a json based data structure that's for expressing the actions taken by a user. It's popular for tracking activity across websites because of it having a standard base schema with flexibility for providing contextual information based on use-case.
    1. H5P elements naturally emit xAPI statements

      Some of them, at least. There are content types which do not emit xAPI statements, sadly enough.

    1. Often our solutions must co-exist with existing systems. That’s why we also invest time and money in emerging standards, like xAPI or Open Badges, to help connect our platforms together into a single ecosystem for personal, social and data-driven learning.
    1. David Smetters (in the G+ locked-in comments):

      A similar article could have been written 10 years ago about QTI 2.x. The vendors had coalesced around QTI 1.x, tweaking it as needed. Then QTI 2.x was created, but not with involvement by the vendors who implemented QTI 1.x. Somewhere along the way, QTI 2.x was pulled from the IMS website, only to reappear many months later, unchanged. There has been little adoption of QTI 2.x in the market and it still causes confusion for newcomers who think it's the "standard" they should be following.

  17. Sep 2017
    1. Over the course of many years, every school has refined and perfected the connections LMSs have into a wide variety of other campus systems including authentication systems, identity management systems, student information systems, assessment-related learning tools, library systems, digital textbook systems, and other content repositories. APIs and standards have decreased the complexity of supporting these connections, and over time it has become easier and more common to connect LMSs to – in some cases – several dozen or more other systems. This level of integration gives LMSs much more utility than they have out of the box – and also more “stickiness” that causes them to become harder to move away from. For LMS alternatives, achieving this same level of connectedness, particularly considering how brittle these connections can sometimes become over time, is a very difficult thing to achieve.
  18. Jul 2017
  19. Mar 2017
    1. Indeed, cannibalizing a federated application-layer protocol into a centralized service is almost a sure recipe for a successful consumer product today. It's what Slack did with IRC, what Facebook did with email, and what WhatsApp has done with XMPP. In each case, the federated service is stuck in time, while the centralized service is able to iterate into the modern world and beyond.

      What Slack, Facebook, WhastApp and others have done to not allow users to use their favorite app to communicate with someone who another app. Sad and bad!

      What would you do if had to use the same email client/provider as the people you want the communicate with?

  20. Feb 2016
    1. We don’t know if content will be interoperable – that is, usable beyond the Amazon (Kindle) ecosystem – or if there’ll be integration with other software systems.

      If not then it really wouldn't be truly "open."

  21. Jan 2016
    1. As NSFdirector Ardent L. Bement, Jr., observes, “with today's electrical grid. . . my neighbor and I can use differentappliances to meet our individual needs; as long as the appliances conform to certain electrical standards,they will work reliably,” and a sufficiently advanced cyberinfrastructure will work similarly: researchers willhave “easy access to the computing, communication, and information resources they need, while pursuingdifferent avenues of interest using different tools.”92

      Helpful analogy for thinking about importance of open standards/interoperability.

  22. Dec 2015
  23. Aug 2015
  24. Jul 2015
    1. Users need digital collections that contain interoperable content or functionality that facilitates comparative analyses of digital materials.

      Enter IIIF for images

  25. Mar 2014
    1. There is no technical or functional reason not to use and establish EPUB 3 as an/the interoperable (open) e-book format standard. One short term obstacle is the non-availability of reader applications able to display all EPUB 3 features. However, this problem should be fixed soon by the IDPF Readium initiative which is developing an open source reference system and rendering engine for EPUB 3