Which means these standards need to be written to be very clear, and must be small enough to be understood by individual contributors.
For example, I just searched for "open document format specification". The results are a pile of irrelevant sites that are happy to explain what ODF files are at an abstract level, but none provide the specifications. There is a single link to https://opendocumentformat.org towards the bottom of my search results.
I click it, and I get a wonderful brochure site that is happy to sell me the idea of adopting ODF for my document processing needs, but again, no specs.
I click on Developers, and I am once again presented with a literal pile of irrelevant bullshit. There is one statement in the first paragraph which tells me, "Sorry, Mario, but the princess is in another castle!" In this case, I have to go to some place named "OASIS".
I click on OASIS and I'm lead to a technical committee description page. Still no specs.
At this point, I'm giving up.
But, apparently, ODF is a proper ISO specification now, so I now try that route.
After some rummaging around on the web, I finally land on this: https://www.iso.org/standard/43485.html
By george, it's an actual spec. But holy fuck, it costs me almost $200.
Yeah, it is "open in name only, for it is neither."
Contrast this with RapidIO specifications, a major competitor to HyperTransport and QPI bus interconnects on high-performance microprocessor-based systems:
Go to https://rapidio.com
Hover over "Technology" and click on "RapidIO Specifications"
Click on any PDF link your heart desires. THOUSANDS of pages of specs, at your immediate beck and call. Have fun.
for fucks sake yes!!!!!!!!! articulating strategies at a supra project level and then aligning them, rinse and repeat!!!!!!!
Taking a strategic approach to software development projects. Have a vision, outline strategies, create a plan, act on it. Does it happen in FOSS world?
Searching on strategy gives pages full of biz this, commercial that, capitalistic BS.
Would FOSS benefit from being more strategic? There's this concept called #OpenStrategy and it could be adapted, populated with practices that are useful for teams, communities, and the commons.
A #poll to see what you think..
This. This. This. This. This. This.
I cannot emphasize this enough. This.
I am so sick and tired of the FLOSS community trying to emulate the commercial world of applications (web and otherwise).
What we need to do is agree upon common data formats and build tools that work with those formats. Not everything needs to be a full-fledged application.
I am reminded of the Commodore-Amiga platform, which had an ecosystem of tools which largely worked together thanks in part to the common usage of IFF-based file formats and ARexx ports.
The notion of "import and export" (or, as PC/GEOS called it, "impex") was generally only a concern when working with software on other platforms, like Macintosh or PCs.
Glossy apps backed by Yet Another Techbro Company based in San Francisco or NYC is great and all; but, without standardized means of controlling these apps or for sharing data, they always, always, always become walled gardens sooner, rather than later.
There is this conference "Semantic Web in Libraries"(SWIB) which I am involved in organizing. Each year, there's a great bunch of people meeting.
You have something interesting to share about #LinkedData in libraries or related institutions? Or have some ideas on how libraries could contribute more to the growth and maintenance of the Fediverse?
"I was able to operationalize the cooperative values and principles into a cooperative platform design. 'Cooperation among Cooperatives' and having 'Concern for Community' have implications for transitioning FarmCoin via an 'Exit to Community.' "
-- Draft text from today's cooperative speculative fiction writing group, as spoken by our AI character, whose name is Jude.
PyPI: Python packets steal AWS keys from users - https://blog.sonatype.com/python-packages-upload-your-aws-keys-env-vars-secrets-to-web
thank you!!!!! that is exactly the kind of paper I was looking for. looking forward to reading it Monday. many people working over long periods has been the story of everything I've learned in this domain, good reminder to be humble :).
seeing the different beliefs about different ontology projects is also one of the most interesting things here to me. like an explicitly realist ontology vs. a provisional or tool-oriented one, and how that comes across in its structure
I have liked the few times Dan and I have crossed paths, and was planning on reaching out, but I get the feeling he is busy, and have gotten the vibe generally (not necessarily from him) that maybe some dust has not settled that might be touchy to bring up, so try to be delicate when pinging directly, but yes!!! also hi Ed :) I saw your name earlier and was also gonna come knocking after I read some more. hope I didn't uh wildly mischaracterize your work, I'm just learnin :)
@jonny I must admit that I don't know much about the early history of SKOS but I always assumed one reason for its development was to enable all the people and orgs that already do knowledge organisation to easily jump onto the semantic web wagon. Thesauri, classifications and other controlled vocabularies have a long history in libraries, and also journalism, corporations and other domains. SKOS was an invitation to publish them.on the web and participate in the Giant Global Graph.
Internet architecture social history is something where I feel particularly new, especially because, maybe by feature of the people, everything is so meticulously documented that I feel like there's infinitely more to read. I would love to submit something, but maybe more as an invitation to history for people who were involved to speak about what things look like in retrospect, tell stories, reflect, reorient, etc.
thank you!!!!! I had just started taking a look at the practice of thesauri when I closed writing for the night. schema translation, however it is usually called, in general is something I'm _extremely_ interested in as it feels like one of those fundamental challenges in knowledge organization and I can't get enough perspectives and histories on it. I have wondered a lot about the overlap in communities of practice that was happening then-- appealing to librarians makes perfect sense
yeah definitely. I've been thinking of resting as planning time, which it is, both in the sense of literal planning but also being useful for plans. idk it's not magic but it's all I got
systems/neuro & digital infrastructure, rawdog meatspace cooperator eating digital vegetal
crossposting to/from @firstname.lastname@example.org , except for toots containing !/
A Fediverse instance for people interested in cooperative and collective projects.