DTD changes include :—
- Support for `<abbr>`, `<emph>`, `<gap reason="editorial">`, `<note>`,
and `<ellipsis>` with `<metamark>` and `<supplied>`. Note that
`<gap reason="editorial">` should be used for ellipses which are not
present in the original fortune source (while `<ellipsis>` should be
used for those which _are_.)
- Support for `<emph>` inside of `<seg>`.
- Support for `<date>` inside of `<analytic>`. This is useful for
articles whose copyright date differs from the publication date of
the journal issue they belong to.
This commit also improves the linting to ensure that fortunes contain
exactly one `<seg type="callout">`, and makes the make·file ignore lint
errors (so that it does not immediately exit on the first failure).
<!--
The following are “ordinary” phrase‐level elements usable inside of paragraphs.
-->
-<!ELEMENT seg (#PCDATA|soCalled|pc)*>
-<!ATTLIST seg
- type (callout) #IMPLIED
+<!ELEMENT abbr (#PCDATA)>
+<!ELEMENT emph (#PCDATA)>
+<!ELEMENT gap (#PCDATA)>
+<!ATTLIST gap
+ reason (editorial) #REQUIRED
+>
+<!ELEMENT note (p)>
+<!ATTLIST note
+ n CDATA #IMPLIED
>
-<!ELEMENT soCalled (#PCDATA)>
<!ELEMENT pc (#PCDATA)>
<!ATTLIST pc
unit (paragraph|phrase|sentence) #REQUIRED
>
+<!ELEMENT seg (#PCDATA|emph)*>
+<!ATTLIST seg
+ type (callout) #IMPLIED
+>
+<!ELEMENT soCalled (#PCDATA)>
<!--
The following encode links.
mimeType CDATA #IMPLIED
>
+<!--
+The following encode choices.
+-->
+<!ELEMENT metamark (#PCDATA)>
+<!ELEMENT supplied (#PCDATA)>
+<!ELEMENT ellipsis (metamark,supplied?)>
+
<!--
The following encode names and name components.
-->
<!--
The following are paragraph‐level elements.
-->
-<!ELEMENT p (#PCDATA|pc|ptr|seg)*>
+<!ELEMENT p (#PCDATA|abbr|ellipsis|emph|gap|note|pc|ptr|seg)*>
<!--
The following encapsulate paragraph information within bibliographies.
<!--
The following provide structured bibliographic information.
-->
-<!ELEMENT analytic (title,idno*,author*,editor*,availability?)>
+<!ELEMENT analytic (title,idno*,author*,editor*,availability?,date?)>
<!ELEMENT monogr (title,idno*,author*,editor*,availability?,imprint,biblScope*)>
<!ELEMENT series (title,idno*,editor*,availability?,biblScope*)>
$(foreach xml,$(xmls),lint][$(xml)) : lint][% :
@xmllint --valid --noout '$*'
+ @$(if $(findstring /fortunes/,$*),if ! xmllint --xpath '//*[local-name()="seg" and namespace-uri()="http://www.tei-c.org/ns/1.0" and @type="callout"]' '$*' >/dev/null 2>/dev/null; then printf '%s\n' 'No callout in file <$*>'; false; fi; if xmllint --xpath '//*[local-name()="seg" and namespace-uri()="http://www.tei-c.org/ns/1.0" and @type="callout"][2]' '$*' >/dev/null 2>/dev/null; then printf '%s\n' 'Multiple callouts in file <$*>'; false; fi,:)
-.PHONY : lint $(foreach xml,$(xmls),lint][$(xml))
+.IGNORE : $(foreach xml,$(xmls),lint][$(xml)) ;
+
+.PHONY : lint $(foreach xml,$(xmls),lint][$(xml)) ;
## Directory Structure
-Each fortune source (in `data/`) is provided in directory of the
- form `AUTHOR__YEAR__IDENTIFIER`, where :—
-
-- **`AUTHOR`** is the author of the work.
- For people, the family name is given first, in all capitals, followed
- by their personal name(s).
-
-- **`YEAR`** is the copyright year of the work.
+Each fortune source (in `data/`) is provided in directory whose name
+ has the form `CREATOR__YEAR__IDENTIFIER`, where :—
+
+- **`CREATOR`** is the creator of the work.
+ Typically, this is the author, translator, producer, or otherwise
+ entity who is most directly responsible for the work existing in a
+ given form.
+ For people with multiple names, family name(s) are given first, in
+ all capitals, followed by their personal name(s).
+ Names in other languages are not romanized, except when the romanized
+ form is considered a distinct, and applicable, alias.
+
+- **`YEAR`** is the (most recent) copyright year of the work.
+ This is, generally speaking, the year that the work was first
+ published.
- **`IDENTIFIER`** is a humanreadable identifier uniquely identifying
the work among all the sources.
+ Typically it is an abbreviated form of the work’s title.
-Within this directory, the following files can be found :—
+Within each source directory, the following files can be found :—
- **`bibl`:**
The bibliographic citation for the source.
--- /dev/null
+<?xml version="1.0"?>
+<!--
+SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
+SPDX-License-Identifier: CC0-1.0
+-->
+<!DOCTYPE biblStruct SYSTEM "../../DTD">
+<biblStruct xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
+ <analytic>
+ <title level="a">
+ <title type="main">
+ <soCalled>Patches don’t have gender</soCalled>
+ </title>
+ <title type="sub">
+ <seg>What is not open in open source software</seg>
+ </title>
+ </title>
+ <idno type="DOI">10.1177/1461444811422887</idno>
+ <author>
+ <persName>
+ <forename>Dawn</forename>
+ <surname>Nafus</surname>
+ </persName>
+ </author>
+ <date when="2011"/>
+ </analytic>
+ <monogr>
+ <title level="j">
+ <seg>new media & society</seg>
+ </title>
+ <imprint>
+ <date when="2012"/>
+ </imprint>
+ <biblScope unit="volume" from="14" to="14"/>
+ <biblScope unit="issue" from="4" to="4"/>
+ <biblScope unit="page" from="669" to="683"/>
+ </monogr>
+</biblStruct>
--- /dev/null
+<?xml version="1.0"?>
+<!DOCTYPE cit SYSTEM "../../../DTD">
+<cit xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
+ <p>
+ In the gift economies to which F/LOSS is often compared, gifts are given to create ties and obligations among people<pc unit="sentence">.</pc>
+ But in F/LOSS, code was just as readily given away as <seg type="callout">a way of cutting ties</seg><pc unit="sentence">.</pc>
+ <gap reason="editorial"/>
+ </p>
+ <p>
+ <gap reason="editorial"/>
+ Community members are decidedly <emph>not</emph> free to build ties that might oblige others to explain themselves, which is exactly what women’s groups do, and exactly why they are considered problematic<pc unit="sentence">.</pc>
+ If someone does not like being in one software project, the accepted course of action is to simply start another project elsewhere, not create an obligation for that community to include you<pc unit="sentence">.</pc>
+ This particular form of exchange means that others can push the technology along further only <emph>as</emph> individually willful agents who have taken it upon themselves to ‘read the f<ellipsis>
+ <metamark>***</metamark>
+ <supplied>uck</supplied>
+ </ellipsis>ing manual.’<pc unit="sentence"/>
+ </p>
+ <bibl>
+ <citedRange unit="page" from="680" to="680"/>
+ </bibl>
+</cit>
--- /dev/null
+<?xml version="1.0"?>
+<!DOCTYPE cit SYSTEM "../../../DTD">
+<cit xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
+ <p>
+ In <abbr>F/LOSS</abbr>, openness relies on a steadfastly closed epistemological frame that not only constitutes technology as apart from persons, but shapes this separability in such a way that code is more than just outside the realm of the social: it is <seg type="callout">downright <emph>freed</emph> from it</seg><pc unit="sentence">.</pc>
+ The social here is not exactly orthogonal to the technical as <abbr>F/LOSS</abbr> imagination has it; rather, social forms shape how ties are <emph>severed</emph>, as well as how they are built, between people<pc unit="sentence">.</pc>
+ Not needing to know with whom code is being exchanged, or having a stake in their concerns, is as central to <abbr>F/LOSS</abbr> as open scrutiny to improve code quality<pc unit="sentence">.</pc>
+ </p>
+ <bibl>
+ <citedRange unit="page" from="680" to="680"/>
+ </bibl>
+</cit>
--- /dev/null
+<?xml version="1.0"?>
+<!DOCTYPE cit SYSTEM "../../../DTD">
+<cit xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
+ <p>
+ Other researchers have likened software production to craft production<note n="2">
+ <p>
+ Here <abbr>F/LOSS</abbr>ers are drawing on the masculinity of the eighteenth century blacksmith or woodworker, an image that evokes a self‐sufficient individualist without posing a threat to male dominance.
+ </p>
+ </note> (Coleman, 2001) or pleasurable play (Klief and Faulkner, 2002)<pc unit="sentence">.</pc>
+ In our study this is indeed part of coders’ imagination<pc unit="sentence">.</pc>
+ Members often describe their work as ‘scratching an itch’ by producing something tangible and craft‐like<pc unit="sentence">.</pc>
+ Scratching an itch is a common reason why people become involved with communities and why they stay<pc unit="sentence">.</pc>
+ Yet tradition and repetition, key elements of other forms of craft production, have no place other than as building blocks upon which to take one’s own work further<pc unit="sentence">.</pc>
+ Re‐doing work similar to that of other coders does not scratch the itch satisfactorily, whereas it generally does among craftspeople<pc unit="sentence">.</pc>
+ In this way, the craft system looks suspiciously <seg type="callout">like a system of science</seg><pc unit="sentence">.</pc>
+ </p>
+ <bibl>
+ <citedRange unit="page" from="677" to="677"/>
+ </bibl>
+</cit>
--- /dev/null
+<?xml version="1.0"?>
+<!--
+SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+<!DOCTYPE div SYSTEM "../../DTD">
+<!--
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
+To view a copy of this license, visit <https://creativecommons.org/licenses/by-sa/4.0/>.
+-->
+<div xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
+ <p>
+ Altho it does serve as a fair analysis of the lack of gender diversity in free ∣ libre ∣ opensource software, the underlying critique in this piece could have been made stronger:
+ The individualistic liberal ideals of the free software move·ment actively work to disrupt socialist, and solidarity‐oriented, modes of producing software.
+ This naturally re·inforces (as it simultaneously obfuscates) existing hierarchies—which happen to be white and male—but I think it’s important to note that, even if the free software move·ment were to miraculously diversify in terms of gender and race, inequality would persist for as long as this liberal frame remained unchallenged.
+ </p>
+</div>
Lady’s Gitweb / Fortune / commitdiff