XML formats for publishing

  1. TEI based XML format at DHQ. Documentation.
  2. JATS based XML at de Gruyter and tons of other publishers.
  3. DocBook and Balisage-1.3 at Balisage. Example
  4. XLingPaper XML




JATS in multilingual books:



Interesting examples:

geoJSON tools and Data


Best Free Geospatial Tools


AnyChart seems to be an interesting option if I wanted to use it for keyboard layouts.


Administrative areas

Global Administrative Areas 2015 (v2.8) dataset. Hijmans, R. and University of California, Berkeley, Museum of Vertebrate Zoology. (2015). Second-level Administrative Divisions, United States, 2015. UC Berkeley, Museum of Vertebrate Zoology. Available at: http://purl.stanford.edu/gv775hx4053
- this resource has a dubious license.


Explination of admin layers


Simone Primarosa - simonepri. 2023. Geo-Maps. https://github.com/simonepri/geo-maps

Front runner: https://www.geoboundaries.org/



What I learned from fasting

My wife has been fasting off and on for a few years. It has been inspiring. I finally tried it. Friday night to Monday night nothing but salt and water. Here are some things I learned.

A pinch of salt when stomach cravings happen, make the feelings go away. I felt as if my stomach was full the whole time.

I didn’t really have any headaches and stomachaches like I did in Highschool. In Highschool I didn’t know about salt and I was biking 10 miles a day.

My stomach, back, and internals felt better with less in them. Granted I’m a bit over weight for my height and muscle composition at 200lbs.

My dad did fasting when I was in Highschool. It is probably what kept him alive. When he quit fasting he gained weight and then had a heart attack and died.

When reintroducing food to the GI track it can be painful. It makes me wonder if fasting is the normal state. If it is, then our culture is upside-down.

I’m keen to try this again for longer. But my todo list need larger margins. Where I don’t have to be all over the place.

OLAC Usage of DCMIType Collection

In the light of the following, usage guideline statements from OLAC, and my paper on Collections, I should write another note. http://www.language-archives.org/NOTE/usage.html#Type

The DCMI type Collection should be used in conjunction with one or more other applicable type terms to represent the nature of the resource as an aggregate of specific, but closely related resources, resources which could also stand on their own but were grouped together as a unit by their creator or a subsequent compiler. See Granularity of resources below for more discussion.


Determining the right level for units to be described as language resources in the OLAC context involves multiple factors. The level of unit appropriate for inclusion in an aggregated catalog like OLAC's may be different (typically higher) than the level desirable for the catalog of a specific institution's holdings, which in turn is typically higher than the level desirable for describing the detailed contents of a resource. Section 6 of the [OLAC-Repositories] standard establishes the following basic guideline regarding the granularity of the records in an OLAC repository:

  • A metadata repository should treat resources with a single provenance as constituting a single unit with respect to OLAC metadata and should, therefore, describe them within a single record.
  • The following discussion is aimed at assisting an OLAC participant to find the right level of description.

    For a resource that has been published in some form, the appropriate unit of description for the OLAC record is the unit of the publication itself. A collective work (e.g., a festschrift) may warrant separate records for the separate papers contained within it (which should be related to the record for the work as a whole through the isPartOf and hasPart relationships; see Relation). In general, the OLAC record parallels a citable source. Thus, for published works, granularity does not really pose a problem. However, many archival resources have not been formally published. Unpublished papers that present findings of research closely parallel typical publications and can be treated in a comparable way as units for archival description.

    Granularity poses the greatest problem with primary source materials (e.g., recordings, transcriptions, annotations, notes, data sets). The typical practice of archivists is to gather such materials into collections, which in turn become the primary units of archival description (i.e., the result is resources of DCMI type collection; see Type). The collection, for example, of a single field trip may contain a large number of distinct components—the separate pieces of documentation that comprise the records of a number of distinct linguistic events (each with recording, transcription, translation, annotation, etc.). However, these components are not the units for description at the OLAC level. It is the unit of the collection that forms the basic unit for OLAC description.

    The foremost factor in determining what materials belong together as a single collection is their Provenance. In the typical case, the collected resources have a common provenance, that is, they have a common origin and history. Common origin includes who was responsible for collecting the materials, as well as when and where they were collected. It could be a single researcher or a research team, either in the context of a single trip or a series of related trips. It could also be a project that draws together materials from disparate sources for a single new research purpose, thus creating a new collection based on a secondary use of the materials. Common history is also relevant; the fact that the set of resources has been moved or changed hands or processed as a whole since it was originally collected helps to establish its identity as a single unit for archival description.

    In other cases, materials may have been placed together at some point in time well after their creation, possibly by the archive itself. If this has occurred, there should be some coherent organizing principle or intermediate stage of development that is still relevant for the proper understanding and use of the resources. Materials without a common provenance generally should not be made to constitute a collection and should not be described collectively in an OLAC description.

    Situations of shared provenance that constitute a collection for arrangement and description purposes will be distinguished by the high degree of commonality of metadata elements, e.g., same researcher(s), author(s), subject language(s), content language(s), approximate dates, coverage, linguistic type. Other metadata elements that may also be important for resource discovery but that may differ for items in the collection (e.g., format or discourse type) can be repeated at the OLAC description level for as many values as are significantly present in the collection. Alternatively, the collection may be divided into sub-collections by discourse genre, speaker, or other significant feature. The sub-collections can then be treated in distinct OLAC records (and related to the whole through the isPartOf and hasPart relationships; see Relation).

    A collection is generally described in greater detail through the use of a "finding aid" that gives the details of organization and highlights features of interest. Further characteristics of individual items within a collection (such as topic, additional contributors, event specifics, extent, format) are documented at a finer level of granularity by creating such a collection description. This should also be included as a part of the collection, preferably as a structured document or metadata set. The Object Reuse and Exchange standard currently under development by the Open Archives Initiative [OAI-ORE] offers a means of handling such descriptions as a different kind of harvestable metadata in the OAI-PMH context. The session-level detail of [IMDI] description typically aligns with the finer level of description in OAI-ORE rather than the level of Dublin Core description in OAI-PMH.