technology:xml

VerbNet — A Computational Lexical Resource for Verbs

« VerbNet is a hierarchical domain-independent, broad-coverage verb lexicon with mappings to other lexical resources such as WordNet (Miller, 1990; Fellbaum, 1998), Xtag (XTAG Research Group, 2001), and FrameNet (Baker et al., 1998). VerbNet is organized into verb classes extending Levin (1993) classes through refinement and addition of subclasses to achieve syntactic and semantic coherence among members of a class. Each verb class in VN is completely described by thematic roles, selectional restrictions on the arguments, and frames consisting of a syntactic description and semantic predicates with a temporal function, in a manner similar to the event decomposition of Moens and Steedman (1988). »

▻https://verbs.colorado.edu/verbnet #knowledge #graph #thesaurus #text #xml

doctest—The Fastest C++ Testing Framework—version 2.3 released!—Viktor Kirilov
▻http://isocpp.org/feeder/?FeederAction=clicked&feed=All+Posts&seed=http%3A%2F%2Fisocpp.org%2Fblog%2F2

doctest brings the ability of compiled languages such as D, Rust and Nim to write tests right next to the production code to C++.

doctest - “The Fastest C++ Testing Framework” - version 2.3 released by Viktor Kirilov

From the article:

Version 2.3 brings an extensible reporter system and a few already implemented reporters with the framework - most importantly one for XML - vital for Continuous Integration (CI) workflows. Huge thanks to the Catch2 project for paving the way for single header testing libraries.

#News,_Product_News,

The Rise and Demise of RSS
▻https://motherboard.vice.com/en_us/article/a3mm4z/the-rise-and-demise-of-rss

https://video-images.vice.com/articles/5c2fc754ae60f200077f016f/lede/1546966494759-rss.jpeg?crop=1xw:0.9995xh;center,center&resize=1200:*

Before the internet was consolidated into centralized information silos, RSS imagined a better way to let users control their online personas.

The story of how this happened is really two stories. The first is a story about a broad vision for the web’s future that never quite came to fruition. The second is a story about how a collaborative effort to improve a popular standard devolved into one of the most contentious forks in the history of open-source software development.

RSS was one of the standards that promised to deliver this syndicated future. To Werbach, RSS was “the leading example of a lightweight syndication protocol.” Another contemporaneous article called RSS the first protocol to realize the potential of Extensible Markup Language (XML), a general-purpose markup language similar to HTML that had recently been developed. It was going to be a way for both users and content aggregators to create their own customized channels out of everything the web had to offer. And yet, two decades later, after the rise of social media and Google’s decision to shut down Google Reader, RSS appears to be a slowly dying technology, now used chiefly by podcasters, programmers with tech blogs, and the occasional journalist. Though of course some people really do still rely on RSS readers, stubbornly adding an RSS feed to your blog, even in 2019, is a political statement. That little tangerine bubble has become a wistful symbol of defiance against a centralized web increasingly controlled by a handful of corporations, a web that hardly resembles the syndicated web of Werbach’s imagining.

RSS would fork again in 2003, when several developers frustrated with the bickering in the RSS community sought to create an entirely new format. These developers created Atom, a format that did away with RDF but embraced XML namespaces. Atom would eventually be specified by a standard submitted to the Internet Engineering Task Force, the organization responsible for establishing and promoting the internet’s rules of the road. After the introduction of Atom, there were three competing versions of RSS: Winer’s RSS 0.92 (updated to RSS 2.0 in 2002 and renamed “Really Simple Syndication”), the RSS-DEV Working Group’s RSS 1.0, and Atom. Today we mostly use RSS 2.0 and Atom.

For a while, before a third of the planet had signed up for Facebook, RSS was simply how many people stayed abreast of news on the internet.

Today, RSS is not dead. But neither is it anywhere near as popular as it once was. Lots of people have offered explanations for why RSS lost its broad appeal. Perhaps the most persuasive explanation is exactly the one offered by Gillmor in 2009. Social networks, just like RSS, provide a feed featuring all the latest news on the internet. Social networks took over from RSS because they were simply better feeds. They also provide more benefits to the companies that own them. Some people have accused Google, for example, of shutting down Google Reader in order to encourage people to use Google+.

RSS might have been able to overcome some of these limitations if it had been further developed. Maybe RSS could have been extended somehow so that friends subscribed to the same channel could syndicate their thoughts about an article to each other. Maybe browser support could have been improved. But whereas a company like Facebook was able to “move fast and break things,” the RSS developer community was stuck trying to achieve consensus. When they failed to agree on a single standard, effort that could have gone into improving RSS was instead squandered on duplicating work that had already been done. Davis told me, for example, that Atom would not have been necessary if the members of the Syndication mailing list had been able to compromise and collaborate, and “all that cleanup work could have been put into RSS to strengthen it.” So if we are asking ourselves why RSS is no longer popular, a good first-order explanation is that social networks supplanted it. If we ask ourselves why social networks were able to supplant it, then the answer may be that the people trying to make RSS succeed faced a problem much harder than, say, building Facebook. As Dornfest wrote to the Syndication mailing list at one point, “currently it’s the politics far more than the serialization that’s far from simple.”

#RSS #Histoire_informatique #Politique_algorithme #Normalisation

How to send the #json data from a #drupal 8 site?
▻https://hackernoon.com/how-to-send-the-json-data-from-a-drupal-8-site-306145e5f5a1?source=rss--

https://cdn-images-1.medium.com/max/1024/0*FNhV1MgZNLvYk50v.png

By ADCI SolutionsImagine a situation: your mobile application needs to get some information from your site on Drupal 8 using JSON. Why JSON? Why not XML? My client needed the data in the JSON format, but still, why choose JSON in our case? On the client application side, JSON data processing is very simple. On the other hand, the data sent in JSON format can have security problems. So it’s better to use XML on the server and JSON for the client-side.How to do it without much effort and installing additional modules, how to change the JSON array programmatically, and send the JSON data with and without using Views — all of these you will learn from this article.Several ways to create and send data in the JSON format in Drupal 8Good news! You do not need to write code or download additional (...)

#api #send-json-data #drupal-8

Designing a Messaging System Using Enterprise Integration Patterns
▻https://hackernoon.com/designing-a-messaging-system-using-enterprise-integration-patterns-86a99

https://cdn-images-1.medium.com/max/1024/1*YzCyBpwJx4G655fC_twyJg.jpeg

I was recently sent a coding challenge where I was required to design a messaging system, diagram that design, and attach a writeup explaining my design choices.I based the structure of this system design off of the principles of Enterprise Integration Patterns (enterpriseintegrationpatterns.com).The ConstraintsEnsure no message are lost.Ensure corrupted or malformed messages cause an alert of some sort to be triggered.Permit priority-based messaging.Process messages by certain type.Collect and log information on each message such as processing time, the number of messages processed, and other related information.The SolutionThe system design document I createdThe first action the messaging system takes is to prepare the message for transit by extending and modifying its header (XML (...)

#interview #software-design-patterns #systems-integration #systems-engineering #design-thinking

Editoria — Building a Book in a Browser
▻https://www.pagedmedia.org/editoria-building-a-book-in-a-browser

Paginated outputs remain important to scholarly communications, and are still critical for books like monographs. Even in today’s increasingly digital discovery landscape, many readers of long-form content continue to prefer print, and the ability to cite page numbers continues to be critical to creating good old-fashioned tools like a book index. But producing paginated books from HTML source files that could also be used for generating other types of digital files has always been a challenge, as Nellie McKesson notes in her recent blog post on Hederis.

So, a couple of years ago, the University of California Press and the California Digital Library partnered with Coko to begin an ambitious project to develop a workflow application that would allow books to be built in a browser using entirely open source technologies. Editoria is not the first open source, browser-based book production system that has ever been attempted, but it’s (at least to our knowledge) the first that has attempted to replicate the rigorous production editing process and workflow, which includes styling, copyediting, author review, and proofreading, in a browser-based application.

We borrowed the idea of single-source publishing using HTML source from predecessor applications like Adam Hyde’s Booktype, O’Reilly’s Atlas, and Hugh McGuire’s Pressbooks, all of which use some form of PDF rendering engine (often proprietary) to output beautiful, paginated books in addition to EPUBs and other HTML or XML-based files. Then, we’ve tried to stand on the shoulders of those applications by building in a greater degree of workflow support. It’s an ambitious project, and supporting paginated outputs from a single HTML-based source file, has been a non-trivial aspect of the system’s development.

https://www.pagedmedia.org/wp-content/uploads/2018/02/2018-02-18_13-32-13.png

▻https://editoria.pub
►https://coko.foundation

#publications_hybrides #prepostprint #web2print #digital-first_publishing

RSS: there’s nothing better
▻https://davidyat.es/2017/05/18/rss-nothing-better

“But, but, XML is gross ! RSS is dead ! 2007 !”

#rss ?

How SAML Authentication Works
▻https://auth0.com/blog/how-saml-authentication-works

“SAML is a standard single sign-on (SSO) format. Authentication information is exchanged through digitally signed XML documents. It’s a complex single sign-on (SSO) implementation that enables seamless authentication, mostly between businesses and enterprises.”

#SAML_authentification

JSON Feed : Home
►https://jsonfeed.org

We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs.

So we developed JSON Feed, a format similar to RSS and Atom but in JSON. It reflects the lessons learned from our years of work reading and publishing feeds.

#web #json #syndication

Sharing Jekyll posts on social media using front matter and IFTTT
▻https://eduardoboucas.com/blog/2015/04/28/sharing-jekyll-posts-on-social-media-using-front-matter-and-ifttt.htm

“Instead of using the normal RSS feed as the trigger for our IFTTT, we can have one feed for each social platform. For example, feed-facebook.xml would contain all the posts we want to share on Facebook. If we want to share a post on Twitter and LinkedIn, then it would appear in both feed-twitter.xml and feed-linkedin.xml. Then we can use those feeds as the source for the individual IFTTT recipes.”

#IFTTT_Twitter_Facebook_Atom_RSS_feed_Jekyll

Logiciel libre à la conquête du grand public - Libération
►http://www.liberation.fr/futurs/2017/02/06/logiciel-libre-a-la-conquete-du-grand-public_1546749

« Linux est de plus en plus populaire, de plus en plus utilisé, mais ça ne s’accompagne pas d’une plus grande liberté pour l’utilisateur », regrette-t-il. C’est tout le paradoxe d’un mouvement qui n’a cessé de gagner du terrain à tous les niveaux sauf en bout de chaîne, dans nos interactions quotidiennes avec nos ordinateurs et nos smartphones.

[…]

« Le logiciel libre est toujours une amélioration, sauf quand le logiciel propriétaire est meilleur que les alternatives ouvertes, parce qu’il y a une perte d’ergonomie. C’est pour cela que le libre et l’ open source se sont développés dans tous les secteurs sauf la bureautique. Nous n’avons pas convaincu les utilisateurs et pour le moment, le problème de la perte de vie privée ne compense pas cette question de la facilité d’usage. »

#opensource #libre #ergonomie

PHP 7.0 (and 5.6) on Ubuntu | LornaJane
▻http://lornajane.net/posts/2016/php-7-0-and-5-6-on-ubuntu
(merci @marcimat !)
#php #version #migration #apache #serveur

Why the Footer Is the New Site Map
▻http://feedproxy.google.com/~r/uxmovement/~3/XVp-xpByV20

http://uxmovement.com/wp-content/uploads/2016/09/mini-sitemap-footer.png

Years ago it was common practice to place a link to your sitemap in the footer navigation. Those days are over because the footer itself has become the new site map.A sitemap is where users can go to find a directory of all site links on one page. But this is no longer necessary for most sites if you design your footer right (although XML sitemaps are still necessary for SEO).Traditional FootersBack then, the footer was rarely considered an important usability element. One study shows that most sites would use a traditional footer. It would contain a short line of administrative links and copyright info. The belief was that most users don’t use the footer because it’s at the bottom of the page.The traditional footer has now evolved into the mini sitemap. Mini sitemap footers are not (...)

LinkChecker - Check websites for broken links
▻https://wummel.github.io/linkchecker

LinkChecker is a free, GPL licensed website validator. LinkChecker checks links in web documents or full websites. It runs on Python 2 systems, requiring Python 2.7.2 or later. Python 3 is not yet supported.
Features:
– recursive and multithreaded checking and site crawling
– output in colored or normal text, HTML, SQL, CSV, XML or a sitemap graph in different formats
– HTTP/1.1, HTTPS, FTP, mailto:, news:, nntp:, Telnet and local file links support
– restriction of link checking with regular expression filters for URLs
proxy support
– username/password authorization for HTTP and FTP and Telnet
– honors robots.txt exclusion protocol
– Cookie support
– HTML5 support

#lien #outil #LinkChecker

Merging Offline Edits with the POSM Replay Tool — Hi.Stamen

▻https://hi.stamen.com/merging-offline-edits-with-the-posm-replay-tool-2f39a4410d2a

https://cdn-images-1.medium.com/max/1200/1*2mSnsbekg3nFgHKkZq40ZA.gif

POSM subverts the centralized revision control system nature of #OSM and layers on distributed semantics in the same way that git-svn enables distributed workflows and #Git semantics over #Subversion.

Given all of the above, the POSM Replay Tool’s solution is to create a local Git repository containing the current state (local edits), transform it so that it contains the new desired upstream state (what OSM should look like after merging), and apply the necessary transformations (in the form of API calls) to update the upstream state.

XML representations of OSM elements (nodes, ways, relations, and changesets) are converted into #YAML, a line-based, diff-friendly format, in order to take greater benefit of the change tracking mechanisms Git provides.

Huge number of sites imperiled by critical image-processing vulnerability
▻http://arstechnica.com/security/2016/05/easily-exploited-bug-exposes-huge-number-of-sites-to-code-execution-att

“According to developer and security researcher Ryan Huber, ImageMagick suffers from a vulnerability that allows malformed images to force a Web server to execute code of an attacker’s choosing. Websites that use ImageMagick and allow users to upload images are at risk of attacks that could completely compromise their security.”

#ImageMagick_image_sécurité_faille_clevermarks

FigDice, un Templating System efficace et original
▻http://connect.ed-diamond.com/GNU-Linux-Magazine/GLMF-158/FigDice-un-Templating-System-efficace-et-original

FigDice
▻http://figdice.org/en/intro.html

The fundamental principle of FigDice is to make the view itself responsible for calling the data it needs. This means FigDice places the view at the centre of the application and only the screens know the services invoked to produce them.

The controller no longer reassembles the data from the various services to inject them into a template - the template itself invokes the services, manipulates their data and decides which are to be presented and how.

Un moteur de #template pour #PHP qui inverse la responsabilité MVC habituelle, où le contrôleur passe les données à la vue (cf Smarty etc).
Ici, c’est la vue elle même qui va chercher les données dont elle a besoin.

Ça ressemble beaucoup à ce que fait #SPIP, mais avec un formalisme xml valide.

Exemple : une boucle sur des tweets

<fig:feed class="TwitterFeed" target="tweets" />
<ul>
<li fig:walk="tweets" fig:text="body" />
</ul>

PanamaData directory listing
▻https://archive.org/download/PanamaData

../ PanamaData_archive.torrent 13-Apr-2016 07:19 2.3K PanamaData_files.xml 13-Apr-2016 07:19 1.4K
PanamaData_meta.sqlite 13-Apr-2016 07:13 9.0K
PanamaData_meta.xml 13-Apr-2016 07:19 1.0K
Panama_data.zip 13-Apr-2016 07:13 18.6M

#anonymous #pp #panama-papers

ScholarlyMarkdown
▻http://scholarlymarkdown.com

ScholarlyMarkdown is a syntax/standard/best-practice of scholarly and academic communication that is web-first, semantic XML-second, and LaTeX/Word a close third. Its main goal is to produce a semantically model of a scholarly article based on Markdown input, and translate it to a variety of formats that is suitable for both online scholarly communication, archiving, and publication.

This is meant to be a replacement for LaTeX, using Markdown, implemented as a fork of pandoc. I’m not sure how hard I should be banging my head against the wall.

OOXML - Complete documentation and samples
▻http://www.datypic.com/sc/ooxml

Office Open XML (OOXML) (ECMA-376)

A very useful way of exploring the OOXML language, especially when you need to know what is what and goes where.

From #JOSM search & replace to processing #Openstreetmap with your favorite text edition tools
▻http://serendipity.ruwenzori.net/index.php/2015/08/25/from-josm-search-replace-to-processing-openstreetmap-with-you #OSM #XML #Perl

Firefox exploit found in the wild | Mozilla Security Blog
►https://blog.mozilla.org/security/2015/08/06/firefox-exploit-found-in-the-wild

Firefox exploit found in the wild

Yesterday morning, August 5, a Firefox user informed us that an advertisement on a news site in Russia was serving a Firefox exploit that searched for sensitive files and uploaded them to a server that appears to be in Ukraine. This morning Mozilla released security updates that fix the vulnerability. All Firefox users are urged to update to Firefox 39.0.3. The fix has also been shipped in Firefox ESR 38.1.1.

The vulnerability comes from the interaction of the mechanism that enforces JavaScript context separation (the “same origin policy”) and Firefox’s PDF Viewer. Mozilla products that don’t contain the PDF Viewer, such as Firefox for Android, are not vulnerable. The vulnerability does not enable the execution of arbitrary code but the exploit was able to inject a JavaScript payload into the local file context. This allowed it to search for and upload potentially sensitive local files.

The files it was looking for were surprisingly developer focused for an exploit launched on a general audience news site, though of course we don’t know where else the malicious ad might have been deployed. On Windows the exploit looked for subversion, s3browser, and Filezilla configurations files, .purple and Psi+ account information, and site configuration files from eight different popular FTP clients. On Linux the exploit goes after the usual global configuration files like /etc/passwd, and then in all the user directories it can access it looks for .bash_history, .mysql_history, .pgsql_history, .ssh configuration files and keys, configuration files for remina, Filezilla, and Psi+, text files with “pass” and “access” in the names, and any shell scripts. Mac users are not targeted by this particular exploit but would not be immune should someone create a different payload.

Update Firefox to the latest version | Firefox Help
▻https://support.mozilla.org/en-US/kb/update-firefox-latest-version

If you use your Linux distribution’s packaged version of Firefox, you will need to wait for an updated package to be released to its package repository. This article only applies if you installed Firefox manually (without using your distribution’s package manager).

Ne pas utiliser #firefox avant d’avoir la 39.0.3 . Je suis sous ubuntu et on est à la 39.0.0 ce matin .

Faille concernant windows et linux (pas mac visiblement)

#security #faille

JSONx is an IBM standard format to represent JSON as XML

http://media.tumblr.com/089bea5b2ce07985315eca2aba543544/tumblr_inline_njhe5grCR31raprkq.gif

#lol #wtf

via ▻http://devopsreactions.tumblr.com/post/112124376421/jsonx-is-an-ibm-standard-format-to-represent-json

Puli at a Glance — Puli 1.0.0-beta documentation
▻http://docs.puli.io/en/latest/at-a-glance.html

Puli (pronounced “poo-lee”) is a #PHP library that manages files, directories and other resources in a repository - much like a virtual #filesystem. Resources can be anything, but usually we use the term for machine-processed files that are not PHP, such as CSS, JavaScript, XLIFF, YAML, XML or HTML files.

Open source impeded by incompatibilities and inconsistencies in the Office Open XML document format

▻https://joinup.ec.europa.eu/elibrary/case/complex-singularity-versus-openness

When it comes to office documents, public administrations can choose from two ISO/IEC standards. Only one of these, ODF (ISO/IEC 26300), is vendor-neutral, open and reliable across a span of years and software versions, and supported by a variety of software products.

The later OOXML standard (ISO/IEC 29500), originally developed by a single proprietary software vendor, is implemented in three different versions (‘ECMA’, ‘Transitional’ and ‘Strict’) that are not compatible with each other. Although the ‘ECMA’ and ‘Transitional’ versions are outdated – ‘Transitional’ had only been accepted as a temporary solution to give the software vendor time to implement ‘Strict’ in its products – they both continue to be used in practice. This is because older versions of the vendor’s office suite (MS Office) cannot read or write OOXML Strict and are unlikely ever to gain such abilities.