Sometimes as a parent one has to encourage their child to do something their child doesn't want to do. That time can today. I had to pull teeth to get Katja to come to the pool with me today. I told her she only needed to swim 3 laps. After much cajoling we got to the car. By the time she got to the pool, she had a kick board and was off. I got a few laps in and she met me at the far wall of the 25 yard lane. She says to me: " I want to swim 12 laps". And so she did. So.. from poolside observer 4 years ago so swim partner today.
This might be a way forward to an OAI-PMH repo: https://github.com/discourse/discourse-sitemap another option is to use a query mechanism in the JSON api to get all threads and treat these threads as resources for description. https://meta.discourse.org/t/discourse-rest-api-documentation/22706
I wonder how many layers a tag-group can have... https://docs.discourse.org/#tag/Tags/operation/updateTagGroup
Subject analysis is very interesting. In a recent investigation into a theory of subject analysis, I was introduced to the concepts of: "about-ness", "is-ness", "of-ness".
Sometimes I wonder if linguists defy standard practices in subject representation, of if they define what a general population holds as a challenge with subject analysis in cataloging.
I harken to the OLAC application profile, which is based on Dublin Core. Dublin Core does not scope the subject element to "about-ness" analysis. UNT curriculum, informed and based (in structure) on Steven J. Miller', Metadata for Digital Collections: A How-To-Do-It Manual. The issue at hand is that for linguists, about-ness is only relevant for Information resources representing analysis. For other kinds of resources such as primary oral texts, or narratives captured via video which are often the object analyzed and discussed in information resources representing analysis, the primary view on subjecthood is through of-ness. As far as I know no-one has discussed audio and of-ness descriptions of audio.
It also makes me wonder if genre is mostly about utility and not about a binding style. To this end then a scholar looking for a phonology corpus, is looking for what—a combination of things—a MIMEType, with a relationship to another MIMEType, with an of-ness of a kind and a subject of "phonology".
By splitting up the concepts of: "about-ness", "is-ness", and "of-ness" it provides analytical space for more articulate descriptions in the dc:description field. But when it comes to language materials, the question is: is language a subject by virtue of "of-ness" or by virtue of "about-ness"? There are several implications here:
The description field ought to be re-thought.
The subject field ought to be re-thought.
Some searches by linguists are likely the concatenation of two or three factors: A relationship between two records, and a subject of a kind and a subject of a different kind.
Variation in accuracy, completeness, or consistency can contribute to lower quality metadata records. Hughes (2006), when looking at OLAC records, rightly points out that coverage (quantity of elements per record) is one way to estimate record quality. However, all three impact end-user perceptions about records and their associated resources.
For OLAC the question is how can it reward data contributors for high quality metadata and also detect low quality metadata while correcting or enhancing low quality?
I wonder if there's a way to limit patent or copyright protection for products that are not made from green materials, where the product could be made from a green material. For example, chopsticks￼.
The chopsticks in the photo are plastic and silicone. These could be made from wood and maybe a metal clip. It would serve the same function and likely have a similar functional product life. I wonder if there were an intellectual property rights protections carve-out if it would discourage the use of materials in product types which do not degrade gracefully. In this way does the law facilitate and reward inventions which complement environmental life-cycles, or does the law facilitate the consumerism which leads to the great pacific garbage patch?
This morning while changing Hugh V’s diaper, I said:” now we have to wipe that pee off so the skin doesn’t hurt later”. Hugh V says: “do we need ahh cream (diaper rash paste)?” To which I replied:”no, we need a little boy who puts his pee in the potty.” To which he replied:” well, I’m definitely a little boy.”
OK I did update on may 29th... it took 10 hours. Now I'm sorting out all the visual theme stuff I lost in the process something about unity vs gnome. Chromium updated fine, brave installs. I had to uninstall vivaldi, and signal Tom get the upgrade to work. Obsidian and slack now work. There is the question on if i should just move up the ladder to 22.04.
One of the frequent things I hear about OLAC is a critique of its Resource Type vocabulary. The OLAC application profile adds linguistics resource types in addition to DCMITypes and an unqualified DC type value. What I don't hear from these same cries for additional descriptive power is for a structured way to use any of the existing resource type vocabularies. Let me list a few:
It has been argued that the Dublin Core Type field is an example of a genre field. This may be true in some sense, but I have a tendency to think of it in terms of an interactivity type field; more of a modality field.
We newly acquired a Chevy Bolt EUV. It seems to present a very nice driving experience. One minor thing that I think the designers overlooked. When using Apple play, the fonts in the iPhone support a wide range of Unicode (as demonstrated by my phone's name in the first image). Apple play in the car's display unit also supports a similar range Unicode (second image). However, the screen of the drivers dash does not support the same set of characters (third image). It is quite common for fonts to replace the characters they don't contain with boxes. I encountered this issue with US based automobile manufacturers' media console displays in Nigeria when people were playing songs with titles in arabic script.
Two other user experience issues:
My wife raises the seat and it didn't automatically lower when I get in. Every time I get in with her seat height I knock my head and it kills my neck out.
When I am in the front passenger seat and the car is off, and the driver is out of the car, I can not turn on the air conditioning.