25 Matching Annotations
  1. Nov 2020
    1. In such cases it is important to capture the connections radially, as it were, but at the same time also by right away recording back links in the slips that are being linked to. In this working procedure, the content that we take note of is usually also enriched

      By adding a backlink for every link we make, we are also enriching the content we are linking to.

  2. Oct 2020
  3. Sep 2020
  4. May 2020
  5. Feb 2019
    1. It’s simply better to link directly to your related content in a meaningful context, than to use a generic related posts box somewhere else on your page.
  6. Jul 2018
    1. The “connected” in connected learning is about human connection as well as tapping the power of connected technologies. Rather than see technology as a means toward more efficient and automated forms of education, connected learning puts progressive, experiential, and learner-centered approaches at the center of technology-enhanced learning.

      Students pursue their interests in the classroom with the support of friends and caring adults while linking this learning and interests to academic achievement.

  7. Jun 2018
    1. 1- 13 A13 --- Planet Planet 15- 15 I1 --- robust Robust flag (1) 17- 23 F7.3 d Per Orbital period 25- 28 F4.1 Rgeo Rad Planet radius 30- 33 F4.2 Rgeo E_Rad 1{sigma} upper error bound on Rad 35- 38 F4.2 Rgeo e_Rad 1{sigma} lower error bound on Rad 40- 40 A1 --- r_Rad Source of planet-star radius ratio (2) 42- 44 F3.1 solMass Mstar Mass of host star 46- 49 F4.2 solMass E_Mstar 1{sigma} upper error bound on Mstar 51- 54 F4.2 solMass e_Mstar 1{sigma} lower error bound on Mstar 56- 56 I1 --- l_Md Md upper limit flag (3) 58- 63 F6.2 Mgeo Md Planet mass from default prior 65- 69 F5.2 Mgeo E_Md ?="" 1{sigma} upper error bound on Md 71- 74 F4.2 Mgeo e_Md ?="" 1{sigma} lower error bound on Md 76- 81 F6.2 g/cm3 rhod Planet density from default prior 83- 87 F5.2 g/cm3 E_rhod ?="" 1{sigma} upper error bound on rhod 89- 92 F4.2 g/cm3 e_rhod ?="" 1{sigma} lower error bound on rhod 94- 94 I1 --- l_Mh Mh upper limit flag (3) 96-100 F5.1 Mgeo Mh Planet mass from high mass prior 102-107 F6.2 Mgeo E_Mh ?="" 1{sigma} upper error bound on Md 109-112 F4.2 Mgeo e_Mh ?="" 1{sigma} lower error bound on Md 114-119 F6.2 g/cm3 rhoh Planet density from high mass prior 121-126 F6.2 g/cm3 E_rhoh ?="" 1{sigma} upper error bound on rhod 128-131 F4.2 g/cm3 e_rhoh ?="" 1{sigma} lower error bound on rhod 133-155 A23 --- Ref References (4)

      This is the main header block of the AAS Journal's "Machine Readable Format" for structured tables. It is based on the CDS table format, and follows their structuring rules. There are columns for the numerical format, units, labels, and explanations for each column.

    1. Our posterior samples are available online (10.5281/zenodo.162965).

      This is an example of our current data linking markup. Data links are inline to the text through a parenthetical anchored link to the DOI resource.

      There is a bug in the current version of the article. Our formal practice is to include this in the "Article Data" tab, which didn't happen this time. We will have to do some more work standardizing our production practices. We are also still thinking about how best to markup the anchored text.

      We have not yet adopted a formal XML schema for including data links. We are working on this, which may be made easier when we adopt the most recent JATS schema.

  8. Aug 2017
  9. Jun 2017
  10. May 2016
  11. Feb 2016
  12. Dec 2015
    1. let you share a URL that navigates directly to the selection you shared.

      An important form of deep linking.

  13. Feb 2014
    1. "We should have some ways of connecting programs like garden hose--screw in another segment when it becomes necessary to massage data in another way. This is the way of IO also."

      And here we are with a web of hoses (nee tubes) and we still only have simplistic linking mechanisms with no way to link directly to the content we are referring to: https://hypothes.is/a/G3usyxJQRFyvOS-bzyXaVQ

    1. Point 3 is almost certainly the one that still bugs Doug. All sorts of mechanisms and utilities are around and used (source code control, registries, WWW search engines, and on and on), but the problem of indexing and finding relevant information is tougher today than ever before, even on one's own hard disk, let alone the WWW.

      I would agree that "the problem of indexing and finding relevant information is tougher today than ever before" ... and especially "on one's own hard disk".

      Vannevar Bush recognized the problem of artificial systems of indexing long before McIlroy pulled this page from his typewriter in 1964, and here we are 50 years later using the same kind of filesystem indexing systems and wondering why it's harder than ever to find information on our own hard drives.

    2. 3. Our library filing scheme should allow for rather general indexing, responsibility, generations, data path switching.