The mable data engine, which provides advertisers high quality data for ad platforms and data warehouses

Mable

THE DETERMINATION OF HEATING VALUES OF FUELS

The Count of Monte Cristo, Illustrated: Chapter 5 - The Marriage Feast

Can you name them by just looking at their faces? You should be able to given their accomplishments. The twentieth century is not so long ago, but time is weird and history weirder. When you are living history in the way we are today it is difficult to find perspective. Everything seems so very new, but the human condition...it doesn't change as much. If you read about the Roaring Twenties, there was so much excitement during the time period. There are huge technological leaps, but also some of the greatest social change of the 20th century. There is so much optimism and forward-looking energy at the beginning of the 20th century. Every single American in the Roaring Twenties is looking to a future of great promise. The nineteenth century was in everyone’s rearview mirror. The horse and buggy era was long gone. There was nothing to be learned from that time when we were driving cars and flying in airplanes. I detect a similar zeitgeist today. There is this belief in technology. A strong belief it can solve ALL our problems if it is just properly applied. It was similar in the 20th century though. Technology did NOT prevent the Great Depression or World War II. We learned about our human flaws again...as we often do. In these times of strife, I am a little surprised that these three women get so little attention. However, like of the nineteenth century perhaps they are just seen as dinosaurs. Trapped in their times with nothing to offer the future. I fear we are about to learn about the extent of our human flaws again... Harriet Tubman Despite that fear, there remains hope for a country which produces people like the three who follow. Three Americans from the 20th century who ought to be celebrated in the 21st century. They are trailblazers. They broke ground for all of us. A consideration of their lives may help us reduce some of our human flaws. 1. Bessie Coleman I will hazard a guess that few readers have heard of this woman. She died tragically young, but she was a real trailblazer. Chauvinists of the era might believe women could not operate mechanical things. Similarly, racists thought the indigenous peoples of North America AND Africa were similarly handicapped, if not more so. Yet Bessie Coleman was the first African-American woman and first Native-American to hold a pilot license. She earned her pilot license from the Fédération Aéronautique Internationale. These are strong words. They are insightful words. Her tragic early death seems unfair. You see she was killed while her mechanic/agent/publicist was flying the damn plane. She was getting ready for a parachute jump and the dumbbell crashed the plane killing her and himself. She died in 1926 at quite a young age. It is probably one of the reasons why she is not remembered. Still, to have died because a white male Texan had failed to secure his tools in the cockpit... Subsequently, his wrench got lodged in the controls during flight causing the fatal crash. It seems a really stupid way to check out and a terrible irony for chauvinists and racists alike. Killed by dumb white male arrogance was certainly a legitimate interpretation of how she passed. It is tragic and sad. 2. Moms Mabley When I was a child, Occasionally, I would see her when the adults would let me stay up late while they drank coffee and gossiped or whatever adults do while they ignore children. Goodness, she was quite funny. She also had a non-threatening grandmotherly air about her. Late in her life though, the fight for civil rights really heated up. Though Moms Mabley was near the end of her career, she was able to get traction with young people. this woman was making the late-night comedy circuit. She even made jokes about being a lesbian during , which had to be some kind of first somewhere/somehow in the LBGTQ community. I did not get the jokes at first, I was young. Eventually, I understood, but I wonder about the adults who were in the same room with me at the same time. her stand-up As I grew older, she appeared in more serious venues too. I saw her sing some songs. I saw her give some interviews. I learned who Moms Mabley really was. She had had quite a hard life. She had been raped twice in her childhood, once by a family member and then by a white sheriff. Both these incidents led to pregnancies which she brought to term and then gave the baby up for adoption. It was then at the urging of her grandmother that she ran off at the age of 14 to join the vaudeville circuit. As tough as that must have been be on the road at 14, it could not have been as tough as what she was fleeing. To learn of these things made me very sad. I cried a tear for Moms Mabley. This woman’s life is so trailblazing in SOOO many ways, I am shocked she does not get more attention. I provided you with a link to some of her stand-up above, but she was so much more than that. You have to see her in a more relaxed setting to really appreciate what she was bringing to the table. In fact, even if you don't read the rest of this you really must watch this video of her rendition of Abraham, Martin and John. Here she is with Sammy Davis, Jr. 3. Shirley Chisholm I really had to save this woman for last. America needs someone like Shirley Chisholm right now. During the sixties and seventies, she was right there in my face of Establishment politics. She could articulate her political opinions with great flourish. When I hear Tyler Perry's Madea character enunciate certain words, I think of Shirley Chisholm. She had a similar way of speaking sometimes. She ran for president in 1972. There is no way to call it a symbolic campaign either. She put up numbers at the convention, which I watched as a child. Her largest support overall came from Ohio, with 23 delegates with a total of 152 first ballot votes at the Democratic convention. Her total gave her fourth place in the roll call tally, behind McGovern’s winning total of 1,728 delegates. Chisholm said she ran for the office . BADASS! “in spite of hopeless odds … to demonstrate the sheer will and refusal to accept the status quo” Goodness, we need women like this today. I cannot believe I do not see this woman’s old speeches all over social media. It is shocking to me given today’s social climate that the name Shirley Chisholm is not on every activist’s lips. If somehow and someway Shirley Chisholm could be resurrected, I feel she would be a shoe-in for the Presidency of the United States this time around. Read this again - " . I don't think a person like Shirley Chisholm would not face hopeless odds today. in spite of hopeless odds … to demonstrate the sheer will and refusal to accept the status quo” Unbought and unbossed, yeah!

3 Black Women of the 20th Century Who Deserve More Recognition

2018: A Review of the the First Year of the DApps: the Anecdotes You Know and Don’t Know (Part I)

Many have written about classification and categorization of crypto assets. Security tokens, utility tokens, cryptocurrencies, exchanges, appcoins, and altcoins are all labels in an effort to organize a collection of similar crypto assets. Some people, like Tom Lee (whom I respect very much) of , break the collections into cohorts based on how they trade — more like sectors. For example, Lee breaks the sectors into commodities, platforms, privacy, exchanges and stablecoins. He does this because these cohorts trade similarly, and he can based on their collective attributes. Sector definition is important, but I think there’s one higher level of abstraction needed. That’s crypto asset classes. Commodities, platforms and stablecoins are of a different classification type than privacy coins and exchanges, and I would separate them as such. That way, we’ll have both asset classes and sectors like we do with traditional financial markets. Fundstrat Global Advisors model trading action Others, like the general partners at , break the collections into 3 major cohorts: currencies (stores of value); security tokens (tokens backed by real-world assets); and utility tokens (work tokens). They’ve settled on this configuration because they think each has a separate and distinct valuation model. They outline a for currencies and work tokens. You’ll notice that they don’t distinguish platform coins from cryptocurrencies as they believe platform coins will be held for their own specific store of value. Multicoin Capital valuation model Some labels have just come to us through nomenclature “inheritance” which I don’t think is very helpful. An example of this is the moniker “altcoins”. It can be confusing as to exactly what an altcoin is and whether it can mean every other coin that is not bitcoin or ether. That’s a large subset that really doesn’t do anyone much good. I think of the crypto asset class superset a little differently. I would classify the mutually-exclusive subsets based on logical groupings. I see and eight distinct crypto asset classes — reserve, currencies, platforms, utility tokens, security tokens, commodities, appcoins stablecoins. I use these crypto asset classes because members of the set have similar properties. They have similar functional goals and react to the market in a similar fashion. They have similar valuation models, compete with one another in some form or operate similarly within their set, have similar regulatory risk and generally define the highest subset under the umbrella crypto asset superset. Fundamentally, I’m coming at this as an investor. I want to have an asset allocation strategy, and then have multiple positions of the best coins I think will produce a return for that crypto asset class. I want to be able to manage target asset class percentages. I don’t want to commingle currencies, utility tokens, platforms and appcoins in the same asset class because it does not provide me with a satisfactory level of precision to allocate across the total market. The asset classes may have similar valuation models, but their stated goal and their functions are different. From an investor’s perspective, it makes sense to create 6–12 classes that are mutually exclusive while also being exhaustively comprehensive to classify members in the entire crypto asset superset. Reserve Assets The reserve crypto asset class contains just two coins — bitcoin and ether. I’m pulling Ethereum out of the platforms crypto asset class for now because it has special properties. Ultimately, investors need to convert their fiat currency into either bitcoin or ether to buy any other coin or token. These act as reserve crypto assets in the market. While bitcoin and ether are different in many ways, they both have a market quality similar to one another and not shared by any other crypto assets. They are both mined and have set monetary policies. Cogent arguments have been made that bitcoin is its own distinct crypto asset class because its deflationary cryptocurrency with limited supply. The Ethereum network is a platform with different supply/demand mechanics than Bitcoin. However, as long as these two crypto assets hold this special dynamic within the market, I’m going to consider them both reserve assets. Let’s take a page from the financial analog. The entire current global asset structure starts with gold. Gold is the first form of money because it is not issued or controlled by a central authority. Moreover, it does not have counter-party risk. We have agreed on its price, based on its scarcity, which has held for millennia. From gold, countries manage their fiat money supplies through their central banks. In the past, the amount of gold a country owned affected how much of its currency supply could be printed. From the formation of currency, a government creates bonds which include an interest rate. Moreover, commodities are priced and other fixed income (bonds) are created to produce a return on capital in the financial market. Equity can be created as a security, after pricing resources (commodities) and calculating interest rates and risk. While gold is classified as a commodity (for legal and other reasons), it’s treated as both a commodity and a currency. It has special properties which convince asset allocators and investors that gold is an asset class of its own. I agree. The same is true for the reserve crypto assets. decentralized Cryptocurrencies Cryptocurrencies’ core benefit to the market is to be a digital form of payment. The fundamental question to test whether or not a coin is a currency asks “Is the primary use as a medium of exchange and/or a store of value?” That is, does it digitally fulfill on a currency’s ability to be: a medium of exchange; a store of value; and, ultimately, a unit of account. While each cryptocurrency is at various stages of delivering on these, that is the primary goal or function. Cryptocurrencies collectively would have similar regulatory risk as a collection compared against other crypto asset classes, i.e., utility tokens, depending on how they came to market. Cryptocurrency has a similar valuation function as standard currency. As such, the Equation of Exchange, M x V= P x Q, is applicable here. The valuation model of cryptocurrency is fundamentally based on unit expenditure and, more importantly, on the velocity of money. As money is used faster throughout the system, the value of that monetary system increases. Cryptocurrencies are all trying to address the same issues with payment. Cryptocurrencies are grouped logically, and there is no superset between this asset class and the crypto asset umbrella superset. Therefore cryptocurrency is its own crypto asset class. Examples of cryptocurrencies are: Bitcoin, Bitcoin Cash, Monero and Dash. Platforms Platforms are going to be one of the most interesting cryptos because this is where smart contracts and programmatic money are going to exist. If a blockchain wants to implement smart contracts in some form, then it’s probably in the platform asset class. Programmatic enforcement of legal and financial contracts will transform the shape and velocity of what’s possible globally. We’re already seeing a fundamental change in what’s possible with the accumulation, transference and store of value. To understand what’s possible, let’s paint a picture of the future in 20 years. All corporations will effectively be smart contracts. Governance, voting, supply chain and contract enforcement will fundamentally change because we are going to be able to programmatically store and transfer value based on some previously agreed-upon logic. We will be able to see exactly where our food comes from and how its handled along the way. We will be able to trust digital voting has not been tampered with because of the immutability of a blockchain. Land title disputes will no longer exist. Value will be created globally just from the transparency and predictability of contract execution. Platforms will work to provide some of the fundamental building blocks of blockchain, like smart contracts, immutability and decentralization. However, they are distinct from cryptocurrency in their stated goal and function. They have different regulatory risk than other crypto asset classes, depending on how they were created (e.g. based on regulatory region and whether a public ICO or private pre-sale governed sale, etc.) Platforms are closer to legal contracts than money in the analog paradigm. Their valuation model is primarily based on , which is described by — the value of the network is proportional to n² users of the network. Whereas, cryptocurrencies are valued on the velocity of money and the equation of exchange. Platforms are distinct from all other crypto asset classes, and thus they are an asset class of their own. network effects Metcalfe’s Law Examples of Platforms are: EOS, NEO, Cardano & IOTA. Utility Tokens Utility tokens focus on a providing a service layer. They provide a function or a resource to address a specific need. They have partners and contributors who create applications on top of the protocol or create applications that use the utility token. Utility tokens valuation model is primarily based on network effects and are influenced by supply/demand. Utility tokens run on a platform blockchain they do not directly manage or control. Most utility tokens to date run on the Ethereum platform. Utility tokens are distinct from platforms in that they aren’t providing a lower level or horizontal functionality built on top of a blockchain like a protocol and they are distinct from appcoins because their stated functional goal is not limited to one application or service. Utility tokens may work on one blockchain for now, but in the future the utility tokens may operate on multiple networks to serve multiple appcoins. Examples of Utility Tokens are: BAT, Civic, OmiseGO and 0x. Photo by on Igor Ovsyannykov Unsplash Security Tokens Security tokens are different from utility tokens and platforms by their functional nature and goal as well as by their regulatory risk profile. They derive their value from being linked to an external asset and are likely subject to federal securities regulations here in the U.S. The valuation model of a security token directly relates to valuing the underlying asset linked to the token. These tokens will have a much bigger play and their growth stage in 2018 and beyond. I predict within the next 12 months there will be companies that want to have their equity trade as security tokens on a crypto exchange. We’ll also see real estate secured on a blockchain with a security token. Security tokens are distinct from all other crypto asset classes because of their link to an external, real-world asset. An example of a Security Tokens is: BCAP. Crypto Commodities Commodities aim to provide a direct consumable resource. This is distinct from the platform asset class in that it’s vertical/industry specific and it seeks to exchange based on a specific subset of resources. Those resources could include disk space, computing power or other consumable services. Commodities are distinct from utility tokens in that their valuation model is mostly influenced by the supply and demand of a given resource. Crypto-commodities run their own blockchain which is different than how utility tokens operate. This is one of the main mechanics to how supply and demand affect price. Price surges and other scarcity risks could occur more frequently with commodities than may affect other asset classes like utility tokens or appcoins. Though, they will have less regulatory risk because of the work or resource exchanged, assuming appropriate measures were followed in their pre-sale. Their valuation model is influenced by network effects but the valuation model is different than currencies which are mostly valued by the velocity of money and platforms which are valued mostly by network effects. Examples of crypto-commodities are: STORJ, FileCoin and Golem. Appcoins / dApps Appcoins work on one specific network to provide a specific vertical application service. They are distinct from commodities in that their supply is not constrained like a commodity or resource that is consumed. They are different from platforms because they are vertical and application-specific. They aren’t providing a platform or protocol for others to build upon. Their goal and utility is distinct in focusing on their own narrow ecosystem. They have a many-to-one relationship in their network model whereas utility tokens have a many-to-many relationship. Appcoins are the most narrow applications and therefore levered to a specific use case as being a “pure play” to a particular application or service. As a result, their valuation model will be distinct from commodities, currencies or platforms. Examples of Appcoins are: Steem, Binance and SALT. Stablecoins Stablecoins are present to provide a stable store of value. Currently, there is one major player within this crypto asset class. That is Tether. However, that will change in the future. Currently there are several projects pursuing various methods on how they will achieve a stable coin. I recommend this to learn more about stablecoins. This is a new and burgeoning asset class, and we will distinguish it on its own due to its stated goal and functional nature. article from Multicoin Capital Examples of Stablecoins: Tether, Maker, Basecoin & Digix Conclusion Hopefully, this makes a case for a good classification model of crypto asset classes. This could change as we’re in the very early stages of this new asset class. It’s possible appcoins could merge into utility tokens or crypto-commodities merge into platforms. My goal is to help investors build a portfolio with appropriate asset allocation to improve your risk-adjusted returns. To achieve that, we need a good framework for how to think about crypto asset classes. If Modern Portfolio Theory (MPT) suggests a return can be made only 3 ways — portfolio construction, asset selection and market timing — then we want a structure to help guide and enforce how we think about asset allocation. A comprehensive crypto asset class model will help in this effort. I’ll leave selection and market timing to other upcoming articles. Happy Hunting! Jake Disclaimer: The above references an opinion and is for information purposes only. It is not intended to be investment advice. Please do your own homework. Jake Ryan is the founder of Wealth Rituals and Tradecraft Capital, a startup advisor, an angel investor & writer on investing. If you enjoyed this article “clap” to help others find it! For more, join us on Facebook , Twitter . #crypto #cryptocurrency #bitcoin #investing #howto #blockchain

Crypto Asset Classes

seems to have a effect on people – either they love it or hate it. It’s true that rebasing opens up a whole range of new and exciting ways to screw yourself over. Even better than that it offers up a range of wonderful opportunities to screw over your team mates as well. Yet despite that I am most definitely in the pro-rebase camp. After all, all the most powerful tools will burn you if you don’t use them properly. Having developed a fairly extensive set of rebase scars over the years here are my handy tips for dodging the pitfalls and making the most of rebase. Git rebasing marmite This assume that you are already familiar with the basic operations of . If not the is probably a good place to start. git rebase git rebase documentation Always rebase interactively Git has two main forms of rebase – interactive and non-interactive. Essentially they do the same thing – take your branch and reapply the code changes on top of another branch. Interactive rebasing offers a bunch more options such as re-ordering and re-wording commits but for the safety-conscious rebaser, the main thing it offers is that it shows you a list of commits that will be re-applied before the rebase starts. In my experience, the vast majority of rebase disasters can be averted by simply reviewing this list and aborting the rebase before it even starts. If the list is not what you expect then run away, figure out why and then try again. Example interactive rebase commit list Be conscious of how you bring in upstream changes A corollary of always rebasing interactively is that you should never use . I would go a step further and say that the only version of git pull you should use is . This is because both the rebase and the default case may result in the code you are working on changing without you realising it. They will both attempt to transparently incorporate any changes made upstream without advising you what they are or letting you review them. A classic case of where this is undesirable is when you and a colleague both add the same method to a class but in a different place in the file. Git will quite happily combine these changes resulting in a duplicate method definition. Maybe you or your colleague will catch it in code review but it is better to avoid it in the first place by being mindful of when the code you are basing your changes on may have changed. git pull --rebase git pull --ff-only Go slow and keep it simple It’s very easy to get excited when you start an interactive rebase. But instead of just diving in and throwing commits here, there and everywhere, taking it easy and spreading the rebase over a few steps will save you a lot of pain and misery in the long run. The first thing I do is an interactive rebase without changing anything. This way you can review the commits and deal with any upstream conflicts up front without having to try and figure out whether the conflicts are a result of something that has changed in the branch you are rebasing onto or whether it is a problem you have created with all your commit juggling. Then as you proceed keep moving, squashing and editing commits in small chunks. That way if you do get any unexpected conflicts you can abort the rebase and figure out the problem without losing any other changes you may have made. Nothing’s worse than going through a marathon rebase to get within sight of the end and having to abort the whole thing because you’ve swapped the wrong two commits around and now one of them won’t apply. Don’t be afraid to run away Rebasing shouldn’t be hard. If it is there is probably an underlying problem with what you are trying to do. Perhaps something has changed upstream that you weren’t aware of. Perhaps you have files in a commit that you weren’t expecting to be there. Don’t be afraid to abort the rebase so that you can stop and rethink what you are trying to do without the pressure of being in rebase limbo. The best way to resolve conflicts is not to have any It is inevitable that you will sometimes run into conflicts caused by changes your colleagues have made. One way or another you will have to deal with them, whether it is via rebasing, when you merge or by shouting at your colleagues until they revert their changes so that you can merge first and thereby force them to deal with the conflicts. Conflicts caused by moving commits around within your own branch are more avoidable however. Keep your commits small and focused. The fewer files and changes in a commit, the less likely it is to conflict and so the easier it is to reorder. If you are TDDing then a good place to start is committing each time you add a test and get the associated code passing. That way you are only ever committing two files at a time and each file will contain a small change. Sometimes more is less The more here being the number of commits and the less being the amount of pain involved in rebasing. If you have ignored the previous suggestion of committing often then that doesn’t mean all is lost. Interactive rebasing allows you to edit a commit. If you have added too many files to a commit and so now can’t move it around, you can edit the commit, remove some of the changes from the commit and create a new commit for them. This sounds complicated but in fact is as simple as marking the commit for editing in the interactive rebase commit list. Then when the rebase pauses run git reset HEAD~ some/file/for/another/commitgit commit --amendgit add .git commit -m '- message for the separate commit'git rebase --continue This will leave all the changes to that file in a separate commit. Another variation on this is for when you have multiple changes to the same file that have accidentally ended up in the same commit. In this case is your friend. This will allow you to choose which of the changes to the file are merged back into your original commit and which stay unstaged ready to add to another commit. git add -p . Know how to fix it when it all goes wrong One of the beauties of git is that it is actually quite hard to completely lose anything once it has been committed. If you do get to the end of your rebase and realise you’ve made a pig’s ear of it, your previous commits still exist and you can easily revert back. First you need the SHA of the tip of your branch before the rebase. Assuming you don’t have this to hand, you can find it using . You will be able to see where your rebase started easily enough as the line will contain . You just need to find the SHA of the commit before this and reset to that commit with . git reflog rebase -i (start) git reset --hard SHA Force push if you have to, but make sure you really need to first One of the oft-cited reasons for avoiding rebasing is that in order to push your changes back upstream you will need to force push, with the potential to overwrite other user’s changes. This is of course completely possible and a great way to antagonise your colleagues. However just because you can screw things up by force pushing doesn’t mean you have to. First of all, you only use rebasing before you merge. Once you have merged something into one of your “main” branches (typically master but perhaps you have other special release branches) then it’s there for good. If you find a problem afterwards you have to live with it or add another commit. You can rebase other branches that you share with colleagues if you choose to. You simply need to communicate as to who is doing what. We do this on a daily basis without issue. It helps if people are responsive. So if one of my colleagues tells me that they have force pushed a branch we are sharing then I will update my local copy straight-away. It helps avoid conflicts and trying to figure out whether a force push should or shouldn’t be necessary. You should also know before you attempt to push whether you are expecting a force push to be necessary. If you get the classic force push error message (along the lines of ) when you weren’t expecting it then don’t just automatically force push. Stop and see what commits you have locally compared to the remote version and then it should become clear what you need to do to fix it. error: failed to push some refs... My personal rule of thumb around shared branches is that if a colleague and I are working on the same feature at the same time, I will create my own branch from the feature branch, work on that and then rebase and merge back into the shared feature branch. It is the safest option and since you both may be pushing frequently it saves constant back and forth. If we are working independently in more of a handover type scenario then we will probably both just work on the same branch as the chances of treading on each other’s toes is much smaller. The other approach, which is probably what we do most commonly, is save the rebase until the end. So we both just keep adding commits to the tip of the branch and then one or both of us will perform the rebase tidy up once we are happy that the feature is ready to go. Use the correct type of merge The aim of rebasing is not to avoid merge commits or maintain a linear history. Merge commits can be very helpful in identifying a set of commits that have some degree of cohesion. However at the other extreme where every single commit has a matching merge commit they are unhelpful and clutter up your log. The answer is simply to always merge with the correct flag set. If I am merging a single commit or if the branch contains multiple unrelated commits then I will do a . If not I will do a . Simple as that. git merge --ff-only git merge --no-ff You don’t have to wait til the end to rebase There are definite benefits to rebasing your code once you have completed all the tasks as discussed above and in . However sometimes you will add a commit just to fix a typo in an earlier commit or something equally trivial. It can be beneficial to just squash these changes straight into the correct commit immediately in order to reduce the number of commits you are working with in your final pre-PR rebase. The poetry of pull requests So there we have it, 10 handy tips for smooth and efficient rebasing. However knowing techniques for juggling commits is only part of the picture. You also need to know what kind of end result you are looking to achieve. For more on that, check out . The poetry of pull requests

How to rebase safely for profit and pleasure

Loss of Amazon Rainforest Resilience: Author Contributions

This paper is under CC 4.0 license. available on arxiv Authors: (1) Jinrui Yang, School of Computing & Information Systems, The University of Melbourne (Email: jinruiy@student.unimelb.edu.au); (2) Timothy Baldwin, School of Computing & Information Systems, The University of Melbourne and Mohamed bin Zayed University of Artificial Intelligence, UAE (Email: (tbaldwin,trevor.cohn)@unimelb.edu.au); (3) Trevor Cohn, School of Computing & Information Systems, The University of Melbourne. Table of Links Abstract and Intro Background and Related Work Multi-EuP Experiments and Findings Language Bias Discussion Conclusion, Limitations, Ethics Statement, Acknowledgements, References, and Appendix 3 Multi-EuP In our approach, we consider the debate topics to be the queries, and the text of each individual speech delivered by an MEP to be a document. The topics are officially annotated by the EU, and professionally translated into 24 different languages.[5] During preprocessing, we filter out procedural debate topics such as , leaving 1.1K unique topics. They will serve as a valuable resource for assessing language bias in multilingual ranking methods, given that all the topics across different languages are semantically consistent. Topics agenda The 22K multilingual documents within the Multi-EuP dataset originate from MEP speeches during parliamentary debates. Each document annotated with additional metadata, including the date of the speech, the MEP ID, and a link to the video recording for potential multimodal research but not used here. Table 1 shows a detailed breakdown of the language distribution and descriptive statistics of the dataset. We include in our corpus documents only in the original language, as spoken by the MEP, but not their translations into other languages. Our only use of translations is the debate topics themselves. Documents To assess the relevance of documents to a given query, we use a binary relevance judgment, based on whether the speech was part of a debate on the given topic, resulting in one positive relevance judgment per document, meaning that the document collection is much less sparse than Mr. TYDI and MS MARCO, for example. Judgments Multi-EuP covers 24 EU languages from seven families (Germanic, Romance, Slavic, Uralic, Baltic, Semitic, Hellenic), each of which is the official language of one or more member states. Table 1 provides a breakdown of each language’s EU usage, member state distribution, and population, using ISO-639 codes. Languages Multi-EuP encompasses 705 members elected across the 27 member states of the EU. We constructed the MEP dictionary by collecting MEP attributes such as and . We further annotated MEPs with gender and their birthdate, based on Wikipedia profiles and Rabinovich et al. (2017), and manually checked if difference existing. Figure 1 illustrates the gender and age distribution across MEPs, with male MEPs being more than twice as numerous as female MEPs, and the majority falling within the 40– 70 age range. This corpus is rare, perhaps unique, due to its richly detailed speaker demographic information, which enables research on fairness and bias in information retrieval. MEP name, photo, id in EU, nationality, place of birth, party affiliation, spoken language For data splitting, we select two sets with 100 language-specific and distinct topics for development and test set in 24 languages, and keep the remaining topics to the training set. This design choice was made to maintain an ample supply of topics and judgment samples essential for the training of deep learning models, and also facilitate subsequent cross-lingual comparative research. Data Split Similarly to Mr.TYDI (Zhang et al., 2021), Multi-EuP can be used for monolingual retrieval in English as well as non-English languages (eg. Swedish queries against Swedish documents). However, unlike Mr.TYDI, Multi-EuP encompasses multilingual documents and identical multilingual topics, ensuring that queries in different languages can be compared. Consequently, Multi-EuP can support diverse information retrieval experimental tasks. These including scenarios with single one language queries against single one language documents, in other words, monolingual or cross-lingual IR, scenarios with single-language queries against multilingual documents, i.e., multilingual IR, and scenarios involving multilingual queries against multilingual documents, i.e, mixed multilingual IR). Supported Task one-vs-one one-vs-many many-vs-many [5] https://www.europarl.europa.eu/translation/ en/translation-at-the-european-parliament/

MABLE

mable.ai

-- employees

Since n.d.

COMPANY RANKING

MABLE

EVERGREEN INDEX #6640

Representing this company? Click here to claim and customize this page!

Mable WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

MABLE

mable.ai

-- employees

Since n.d.

COMPANY RANKING

MABLE

EVERGREEN INDEX #6640

RELATED COMPANIESRANK

STORIES ABOUT MABLE

Representing this company? Click here to claim and customize this page!

Mable WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!