142 Matching Annotations
  1. Sep 2018
    1. The epub:type attribute [ContentDocs32] is REQUIRED

      Discerning the available values of epub:type is a tangle... The referenced epub:type related section in the ContentDocs32 document references the Vocabulary Association paragraph which in turn references the Vocabulary Association Mechanisms section within this current document. From that section the default vocabulary can/may be found, but there is no reference there (or in any of these other sections) to the available epub:type values nor to their "meaning"/value to the author or implementer.

      However, just below this in the example (and above in relation to pagebreak there is a link directly to the defining defaults in the EPUB-SSV.

      It would be helpful for authors and implementers to know first about the SSV list, and then about the ability to extend the vocabulary.

    2. The page-list nav element SHOULD contain only a single ol descendant (i.e., no nested sublists).

      If this SHOULD is not heeded...what happens? How is the page list calculated if there is a hierarchy present?

    3. The toc nav element

      This makes it sound like there is an HTML element with a tag name of <toc nav> rather than <nav epub:type="toc"> (which seems to be what's intended).

      The landmarks example farther down is clearer--though the wording there of "the landmark nav element" is equally confusing.

      There remains only a nav element, but of varying types.

    4. In the context of this specification, the default display style of list items within nav elements MUST be equivalent to the list-style: none property [CSSSnapshot].

      This line is confusing because the actor (author or reading system) is unclear. The following two lines are much clearer on what actor is being restricted by this specification.

      This line feels specific to the Reading System requirements. Consequently, perhaps it's best to integrate it into the sentence just following.

    5. it MUST resolve

      Link resolve to any defined algorithms for resolving resources within an EPUB.

    6. If an a or span element contains instances of HTML embedded content that do not provide intrinsic text alternatives, the element MUST also include a title attribute with an alternate text rendering of the link label.

      This requirement is clearer than the one just previous and also seems to obviate the earlier one.

      However, this one is confusing limiting the textual expression to just the title attribute, and also being vague of which element is associated to the MUST--is it this surrounding a or span? or the contained "embedded content" element?

    7. after concatenation of all child content and application of white space normalization rules.

      Implied requirement? When is this necessary and what does the concatenation and normalization?

    8. visual display of components

      Where is this "visual display" taking place? Is this when the document is viewed as a spine element? or is this when the content is extracted and presented by the Reading System?

    9. while a span element

      Rephrase "while a child span element" and perhaps move to it's own sentence parallel to the "A child a element"

    10. Each list item

      Reference the li element here for consistency.

    11. current reading position

      Link to this, if defined.

    12. when rendered in a non-browser context.

      Is "non-browser context" defined? or its inverse?

      It's not clear if "browser" here is equivalent to "Reading System" or to a Web browser or something else.

    13. If such formatting and functionality is used

      Used by? It's not clear who the actor is here, the author/developer of the EPUB or the Reading System.

    14. a custom control, such as the table of contents

      Is the "table of contents" a specific type of custom control? If so, a link would help here.

    15. which has no effect outside of spine rendering

      But it does have effect on "spine rendering"? Perhaps add a link for spine rendering.

    16. represents a data island

      Is "data island" a specific, defined thing from a previous EPUB spec or another adjacent spec?

    17. custom control

      Link to a definition of "custom control" if one exists.

    18. Unlike typical XML data islands

      Not sure what a "typical XML data island" is either...so some links or even rewording (or removing?) might help others unfamiliar with the phrase.

  2. Dec 2017
    1. 6. It should be possible to further qualify a reference to a "sublocation" within an object (which would have meaning only to the server that houses it). This is needed, for example, for hypertext-type links. Such a sublocation might be the 25th paragraph of a text, for a hypertext-type pointer.
  3. Apr 2016
    1. When context gets smudged, whole constellations of meaning are lost.
    2. the hyperlink provided a diversity and decentralisation that the real world lacked
    3. We’re also losing the organic and open shape of the web. It’s becoming something much more rigid and more hierarchical.
    4. The hyperlink was a way to abandon centralization — all the links, lines and hierarchies — and replace them with something more distributed, a system of nodes and networks.
    5. “Go where the readers are” is what publications whistle to themselves as they slink by the graveyard of their inflexible or unlucky brethren.
    1. while e-mail dissolves barriers to the exchange of data, we need another solvent to dissolve the barriers to collaborative use of that data. Applied in the right ways, that solvent creates what I like to call the “universal canvas” – an environment in which data and applications flow freely on the Web.

      Highlight of original quote: https://hypothes.is/a/iKeap_T6TauWGfyf19VW_Q

    1. Interestingly, it uses multiple methods to locate the annotation within the cited page: absolute character count, text to search for, and XPath notation.

      That's done to accommodate sites who's DOM changes either over time or during user interaction (single page apps, etc).

      This blog post explains the current approach and thinking behind it in Hypothes.is: https://hypothes.is/blog/fuzzy-anchoring/

  4. Jan 2016
    1. ipfs cat /ipfs/QmW2WQi7j6c7UgJTarActp7tDNikE4B2qXtFCfLPdsgaTQ/cat.jpg >cat.jpg

      Same with this one. Dropping the /ipfs/ fixed it.

    2. hash=`echo "I <3 IPFS -$(whoami)" | ipfs add -q`

      Also, this gives me an error from ipfs add:

      $ hash=`echo "I <3 IPFS -$(whoami)" | ipfs add -q`
      Error: Argument 'path' is required
      Use 'ipfs add --help' for information about this command
    3. ipfs cat /ipfs/QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme

      This line didn't work for me (on Windows).

      However, after starting the daemon, I was able to do the following:

      ipfs cat QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme

      Not sure what's up.

  5. Dec 2015
  6. Nov 2015
    1. Companies that open source a project and then abandon it need to publicly acclaim the people taking over the project and make a clear change in ownership.
    2. Companies need to have realistic expectations of the work-life balance of open source maintainers.

      When you hire an open source developer, you hire someone who works all the time--not just 8-5, not just at a desk, not just on that one pet project that management's currently excited about. They work on that, they work on the related libraries, they work on projects that use those libraries, they work on the next great version of the libraries the company will need in two more years.

      Plan for your own future by letting your developers explore it for you. They already are...even before you've hired them.

    3. effectively contribute and participate in upstream projects

      If anything is missing with regards to open source within companies (of all sizes), it's this situation.

      Teaching "companies" (or rather the entire management stack/chain) how to "effectively contribute and participate in upstream projects" could change the game for those companies, the projects they interface with, and certainly for the developers (inside and outside of the companies).

    4. They should be treated like adults though and allowed to spend what they see as an appropriate amount of time working on the project versus other projects for the company. Trying to quanitfy/limit the amount of time leads to conflict and strife and unhappy management and employees. It doesn't work and it's not a long term, maintainable solution.

      In the end, it's a quest of trust. Hire people who work on the open source projects your company depends on. Then, let them keep doing it--for pay...at last!--and expect them to continue to balance the worlds of open source and business...as they likely already were, but now with the needle tilted slightly (or more, one would hope) in favor of working on open source code.

      It's like picking flowers. If you pick them and bring them inside, they die. Plant them in some fertile ground, however, and let them keep doing their thing. (OK, that was a bit strained...but hopefully you see my point ^_^).

    5. Some projects work to actively alienate corporations trying to contribute because of ideology. This is not the path that will lead us to sustainable open source software development and companies that can contribute responsibly.


      /me pats IBM on the back one more time. :)

      There are (a very few) companies that balance these worlds of community and commerce well.

      If you know of another, please reply!

    6. The company refuses to expand the core development team with non-employees

      From what I've seen these projects are often licensed under the AGPL and essentially amount to "loss leader source." Community === "add on builders" and "consumers" in the minds of the product team not future "land owners."

      Be sure the project is community lead (or in transition that way at least!) before you sign that CLA...or even bother with that patch.

    7. TwitterOSS team (hint: their funding as a department was cut)

      Sad news.

    8. sometimes you find a bounty like this one where a company has added a significant amount to a bug

      Unsurprisingly (to me) that company is IBM.

      Keep up the greatness!

    1. Definition SLE System of Linear Equations

      $$\begin{align*} a_{11}x_1+a_{12}x_2+a_{13}x_3+\dots+a_{1n}x_n&=b_1\\ a_{21}x_1+a_{22}x_2+a_{23}x_3+\dots+a_{2n}x_n&=b_2\\ a_{31}x_1+a_{32}x_2+a_{33}x_3+\dots+a_{3n}x_n&=b_3\\ &\vdots\\ a_{m1}x_1+a_{m2}x_2+a_{m3}x_3+\dots+a_{mn}x_n&=b_m \end{align*}$$

    1. まぶた)

      Testing a highlight on Ruby text.

      Highlight is meant to wrap this image: kanji

      Highlight is also meant to include the super-script hiragana characters: まぶた

      Actual highlight includes the hiragana characters "まぶた" as well as ")"

    1. The URI generic syntax for authority also includes a deprecated userinfo subcomponent ([RFC3986], Section 3.2.1) for including user authentication information in the URI. Some implementations make use of the userinfo component for internal configuration of authentication information, such as within command invocation options, configuration files, or bookmark lists, even though such usage might expose a user identifier or password. A sender MUST NOT generate the userinfo subcomponent (and its "@" delimiter) when an "http" URI reference is generated within a message as a request target or header field value. Before making use of an "http" URI reference received from an untrusted source, a recipient SHOULD parse for userinfo and treat its presence as an error; it is likely being used to obscure the authority for the sake of phishing attacks.

      You know...it didn't have to be this way...

      RFC3986 Section 3.2.1 states (emphasis added):

      The userinfo subcomponent may consist of a user name and, optionally, scheme-specific information about how to gain authorization to access the resource.

      Additionally, it clearly states that use of the : is deprecated.

      Use of the format "user:password" in the userinfo field is deprecated. Applications should not render as clear text any data after the first colon (":") character found within a userinfo subcomponent unless the data after the colon is the empty string (indicating no password).

      Further removal of the use of the userinfo section in HTTP URIs by this RFC was unnecessary...and now just complicates future use of this space.

      Were it not for this paragraph in RFC7230, userinfo.me could have been a simple thing...

      Quoting the sad bit one more time...

      A sender MUST NOT generate the userinfo subcomponent (and its "@" delimiter) when an "http" URI reference is generated within a message as a request target or header field value.

      Time for a new RFC which updates this one and fixes this error.

    1. If you have a copy of the ReSpec repository handy, you may see that there is also a respec2html.js tool under tools/. Feel free to try using it instead of the above process, but please note that it is not used much currently and may behave in a somewhat experimental manner (experiences with it vary — but it's worth a shot if you're looking for a way to generate ReSpec output from the command line).

      Respec (sadly) doesn't quite have a command line tool...at least not one comparable to a browser's output.

      Maybe PhantomJS (which Respec uses for tests) would do a better job?

    1. It is up to the domain model and server to determine the appropriate predicate to indicate the resource’s order within a page (or globally), and up to the client receiving this representation to use that order in whatever way is appropriate to meet its needs, for example to sort the data prior to presentation on a user interface.
  7. Oct 2015
    1. a web so conceptually consistent, socially relevant and technically expandable

      We've done relatively well with the first two. "Technically expandable" is the one in danger.

      If we continue to build "social networks" as singular dead end cul-de-sacs, we leave no exit available to those who follow.

      The Web we want is expandable beyond the reaches of what we currently know, the economies we operate within, and the future we can currently conceive.

    1. Apache Labs is a place for innovation where committers of the foundation can experiment with new ideas.

      Here's the door into making the ASF tooling better! Got an idea? Submit it! Got some code? Submit that too!!

  8. Sep 2015
    1. Schedule

      Let me know if I've missed anything! Feel free to link to photos, videos, send in editorial corrections, or link to blog posts you cite in your talk.

      The page will continue to change throughout the weekend, so you're input and help are very welcome!

  9. Aug 2015
    1. An external tool can ask for an xAPI callback URL, and then POST back an interaction activity to Canvas. This will update the activity time for the user in Canvas, and add a page view for that tool. Page views will show up in the course analytics section as activity.
    1. The TLA components align with 4 key concepts: experience tracking, learner profiles, content brokering and understanding, and competency networks.
    2. The Training and Learning Architecture (TLA) encompasses a set of standardized Web service specifications and Open Source Software (OSS) designed to create a rich environment for connected training and learning.
    1. A Learning Record Store (LRS) is a system that stores learning information (statements) communicated through the Experience API (xAPI).
    2. Traditionally, a learner's data stays within the LMS or the organization running the LMS. Unlike an LMS, the LRS and the xAPI enable the sharing of data between LRSs and other xAPI-enabled tools. This means a learner's data can follow them wherever they go, from school to school and job to job.
    1. In this scheme, if a sub-ject is related to multiple objects by the same prop-erty, then each distinct value is listed in a successiverow in the table for that property

      Sound like [Apache CouchDB]'s map/reduce output to anyone else?

    1. It was all envisioned by Sir Tim Berners-Lee 25 years ago

      It's amazing how hard the implementation bit is... :(

      Love the idea. Making it a reality is still ongoing, as I'm sure TimBL knows all too well...

    1. We know this because there are societies where a lot more of this money is taken from the most fortunate, and it results pretty straightforwardly in less cruelty for the least fortunate.

      Anyone know the scenario he's citing here?

      I'd love to read more.

    2. compensating for it by also doing good.

      "Good" isn't something you can buy like carbon credits. It's something that's done instead.

      Perhaps the debits and credits economics are at play even here in the terminology used to "understand" doing good.

    3. the winners of our disruptive age are arguably as concerned about the plight of the losers as any elite in human history.

      What is concern without action?

    4. The Aspen Consensus, in a nutshell, is this: the winners of our age must be challenged to do more good. But never, ever tell them to do less harm.

      Spot on.

    1. As soon as computer data entry moved from punch-cards to online files (in the mid/late 1960s) there were "commands" for accomplishing this operation.
  10. Jul 2015
    1. We strongly urge you to reconsider your business tactic here and again respect people’s right to choice and control of their online experience by making it easier, more obvious and intuitive for people to maintain the choices they have already made through the upgrade experience.

      Completely agree!

      Now...how do I change my Reader View settings to use something besides Pocket for social bookmarking?

      ...can't seem to find that setting...anywhere.

    1. Let me be very clear: I do not care what the “top highlight” is. In fact, I actively do not want to know what the top highlight is. That kind of information encourages the meme-ification of the web, a world where we care more about pushing one sentence over the “tipping point” into virality than in carrying on a global conversation. It’s American Idol for pull quotes.
    1. The world doesn’t throw a billion dollars at a person because the person wants it or works so hard they feel they deserve it. (The world does not care what you want or deserve.)  The world gives you money in exchange for something it perceives to be of equal or greater value: something that transforms an aspect of the culture, reworks a familiar story or introduces a new one, alters the way people think about the category and make use of it in daily life.
    1. “We need to be super careful with AI. Potentially more dangerous than nukes.”
    2. “Hope we're not just the biological boot loader for digital superintelligence. Unfortunately, that is increasingly probable.”
    3. “With artificial intelligence we are summoning the demon. In all those stories where there’s the guy with the pentagram and the holy water, it’s like – yeah, he’s sure he can control the demon. Doesn’t work out.”
    4. “The risk of something seriously dangerous happening is in the five year timeframe. 10 years at most.”
    1. Twitter is an "argument machine"

      Maybe annotation could put "tweet" sized things into context and thereby avoid the "argument machine."

      Rashly assuming anyone will actually take time to read the context and the comment...

    2. a chaotic way of managing a project as that project gets big

      Don't let it get big? Maybe.

    3. the nature of low-bandwidth communication on the internet probably just exposes you to misunderstandings and you end up stressing out over things vs being the friends you normally would.
  11. Jun 2015
    1. Apple’s superior position on privacy needs to be the icing on the cake, not their primary selling point.

      Yeah... 'cause apparently no one actually cares...

  12. May 2015
    1. Engineers who worked on a lot of open source projects had high levels of creativity
    2. Developers felt more ownership over their work, and pride in it
    3. Open source developers work well together because of their similar ways of thinking
    4. Peer pressure from GitHub—having their name on a project—was a big motivator for engineers to work harder and not let the community of users down.
    5. If they leave, they're likely to keep working on the project, so you're still getting value for free!
  13. Apr 2015
    1. Axiom: Opacity of URIs The only thing you can use an identifier for is to refer to an object. When you are not dereferencing, you should not look at the contents of the URI string to gain other information.
  14. Mar 2015
    1. Any contributor to our open source projects is already familiar with a bit of software that we use internally and would require less training if they joined the company.
    2. community development should be part of your open source project’s regular duties
    3. At Twitter, our open source program has a team of developer advocates focused on growing open source ecosystems which are important for us to ensure they thrive and evolve to our benefit.
    4. hosting events, speaking at conferences, reaching out to contributors, writing documentation to lower the barrier of entry to new contributors
    5. suffers from an over protective legal organization
    6. respecting open source licenses to making it easier for engineers to open source code and ensuring we’re giving back to the open source projects we depend on
    7. …empowerment of individuals is a key part of what makes open source work, since in the end, innovations tend to come from small groups, not from large, structured efforts.
    1. You can expect to pay 50 cents a day. Or try DIY. This is where you will own your content.

      Rent to own?

      There is no ownership while we rent.

      We either own or increase our freedom of movement in and out of rental environments...or both.

  15. Feb 2015
    1. A "non-transparent proxy" is a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering.

      Hey look!!1! "group annotation services"!

      Here's one: http://via.hypothes.is/

    1. Group name shows on cards

      Perhaps "{user} for {group} on {doc_title}" and "{user} for {group}" in the sidebar.

    2. leave a group

      Does "leaving" amount to "unsubscribing"? Such that, leaving a group simply means it won't:

      1. show up in your sidebar/stream content
      2. won't send you email for additions in that group
      3. won't be in your list of groups to publish into

      I.e. if I wanted back in, I could find that email with the invite link and re-join (or perhaps there's UI that let's me re-join past groups).

    3. (Again, this is in no way a proposal for how the URLs should be structured.)

      To avoid overvaluing group names by making them scarce, we should include a small uniqueness element like a (very short) UUID.

      Obviously more than one person will want to make a group named "research."

    4. email pops up a new email with the subject set

      Pretty simple with `mailto:{email}?subject="Annotate this"&body="http://..."

      Not all mail clients support body (iirc), but most/all support subject.

    5. Annotations show in stream

      Which stream? The public one? or a custom one?

    1. There was a point many years ago now when the web looked like it would be for documents. It would be structured and organized, and everything could be linkable.

      ...and I want this Web back...

    1. while e-mail dissolves barriers to the exchange of data, we need another solvent to dissolve the barriers to collaborative use of that data. Applied in the right ways, that solvent creates what I like to call the “universal canvas” -- an environment in which data and applications flow freely on the Web.
    2. Implementing a common collaboration system would require effort. Exploiting the e-mail common denominator requires none.
  16. Jan 2015
    1. Make no mistake, in today's digital age, we are most definitely "renters" with virtually no rights—including rights to our data.
    2. The Internet of Things promises to create mountains upon mountains of data, but none of it will be yours.
    1. To put it simply, the next great advance in human ability comes from being able to externalize the mental models we spend our entire lives creating.
    1. Teachers can save digital content to the built-in storage and up to 50 students at a time can connect to the Access Point to download or access documents, videos, or other files on their own devices even if there’s no internet signal.

      CouchDB replication anyone?

  17. Dec 2014
    1. ANNOTATION The information in B is additional to and subsidiary to that in A. Annotation is used by one person to write the equivalent of "margin notes" or other criticism on another's document, for example. Example: The relationship between a newsgroup and its articles. Acyclic.

      Annotation link relationship in HTML 1.0 circa 1993.

  18. Nov 2014
    1. There’s a certain amount of snobbery about PHP, but I’ve no truck for such snark. PHP is the Web’s BASIC. It’s everywhere, beginner-friendly, and I like it.
    1. Clients are browsers

      == or === ?

    2. Links must be stored in HTML files

      But what about links I want to add to documents that I don't own? "Layers for the Web"

      Doesn't Xanadu keep stuff separate somehow?

    3. URLs are filenames

      Is this why content negotiation died / never really happened?

    1. the interface currently works quite slowly, much slower than regular web content.

      This may be browser-side speed. Most of the heavy lifting of the application is done in the client.

    2. There is also no easy way of informing an author that someone has commented on his or her work, especially if he or she is not a Hypothes.is user.

      Yeah...tricky part is finding the author of a web page in the first place.


    3. Allowing users to submit more information about themselves will make communication easier.
    4. the possibility of exporting comments from an on-line Hypothes.is application to a desktop application (which could be an extension of the pdf viewer) and back, might be a crucial point for the further development of hypothes.is.
  19. Oct 2014
  20. Sep 2014
    1. Most systems av ailable today use a single database.

      Even after all these years...this is essentially still true.

    2. Hy per Card

      Anyone else think Hyper Card was amazing?!

    3. ENQUIRE

      As featured in "Weaving the Web" by Tim Berners-Lee

    1. While the Atom Protocol specifies the formats of the representations that are exchanged and the actions that can be performed on the IRIs embedded in those representations, it does not constrain the form of the URIs that are used. HTTP [RFC2616] specifies that the URI space of each server is controlled by that server, and this protocol imposes no further constraints on that control.
    1. An array of FDF annotation dictionaries (see “FDF Annotation Dictionaries” on page 681). The array can include annotations of any of the standard types listed in Table 8.16 on page 580 except Link , Movie , Widget , PrinterMark , Screen , and TrapNet .
    1. The cacophony of the crowd erases the past and affirms the present. It started with search and now its accelerated with the now web. I dont know where it leads but I almost want a remember button — like the like or favorite. Something that registers something as a memory — as an salient fact that I for one can draw out of the stream at a later time.
  21. Aug 2014
    1. This user's guide includes introductions to Scalar's features as well as more in-depth material to explore as your get to know the tools. If you're familiar with blogging platforms like WordPress you'll find yourself at home with many of Scalar's editing features, though you can also do things with Scalar that would be next to impossible in a typical blog.

      This is an annotation of a thing on a thing.

    2. free, open source


  22. Jun 2014
    1. Technology leadership is not defined by patents, which history has repeatedly shown to be small protection indeed against a determined competitor, but rather by the ability of a company to attract and motivate the world’s most talented engineers. We believe that applying the open source philosophy to our patents will strengthen rather than diminish Tesla’s position in this regard.

      "Technology leadership is....defined by...the ability of a company to attract and motivate the world's most talented engineers."

      The key components of this applied "open source philosophy" seem to be about increasing input, visibility, and collective motivation by taking fear out of the interaction equation.

    2. receiving a patent really just meant that you bought a lottery ticket to a lawsuit
    3. If we clear a path to the creation of compelling electric vehicles, but then lay intellectual property landmines behind us to inhibit others, we are acting in a manner contrary to that goal.
  23. May 2014
    1. MIT-licensed

      It's stored in a [COPYRIGHT](https://github.com/gittip/aspen-python/blob/master/COPYRIGHT) file rather than a LICENSE one, but it's well licensed, all the same. :)

    2. Negotiated

      Content Negotiation has finally come of age! More frameworks should make this as "native" as Aspen does.