Get rid of pandoc-include

jindrichmynarz · Sep 18, 2017 · 0af0f48 · 0af0f48
1 parent a6d145f
commit 0af0f48
Show file tree

Hide file tree

Showing 55 changed files with 40 additions and 142 deletions.
diff --git a/Makefile b/Makefile
@@ -2,13 +2,14 @@ define COMMON_PARAMS
 -f markdown+implicit_figures+backtick_code_blocks \
 --number-sections \
 --toc \
--s \
--S \
---filter pandoc-include \
+--smart \
+--standalone \
+--normalize \
 --filter pandoc-crossref \
 --filter pandoc-citeproc \
 --bibliography references.bib \
---csl style/iso690-author-date-cs.csl
+--csl style/iso690-author-date-cs.csl \
+parts/metadata.yaml
 endef
 
 html:
@@ -20,7 +21,7 @@ html:
 		--css http://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic \
 		--css media/css/bootstrap.css \
 		$(COMMON_PARAMS) \
-		text.md
+		parts/*.md
 
 pdf:
 	pandoc --latex-engine=xelatex \
@@ -35,7 +36,7 @@ pdf:
 		-V papersize=a4paper \
 		-V documentclass:report \
 		$(COMMON_PARAMS) \
-		text.md
+		staging/*.md parts/*.md
 
 excerpt:
 	pandoc --latex-engine=xelatex \
@@ -49,7 +50,7 @@ excerpt:
 		-V papersize=a4paper \
 		-V documentclass:report \
 		$(COMMON_PARAMS) \
-		excerpt.md
+		parts/*.md
 
 clean:
 	rm -f text.html text.pdf excerpt.pdf
diff --git a/excerpt.md b/excerpt.md
diff --git a/parts/analyses.md → out-takes/analyses.md b/parts/analyses.md → out-takes/analyses.md
diff --git a/out-takes/definitions.md b/out-takes/definitions.md
@@ -0,0 +1,9 @@
+## Definitions
+
+<!--
+TODO: Distribute this section to the parts that reference the notation.
+-->
+
+We can start with a definition of the key entities involved in the matchmaking task.
+Let $C$ be the set of public contracts, $B$ the set of bidders, $Auth$ the set of contracting authorities, and $Con_{CPV}$ be the set of CPV concepts.
+We use numeric subscripts to access elements of n-tuples, so that $coll_{i}$ denotes the $i$-th element of n-tuple $coll$.
diff --git a/parts/factors.md → out-takes/factors.md b/parts/factors.md → out-takes/factors.md
diff --git a/parts/full_text_search.md → out-takes/full_text_search.md b/parts/full_text_search.md → out-takes/full_text_search.md
diff --git a/parts/further_problems.md → out-takes/further_problems.md b/parts/further_problems.md → out-takes/further_problems.md
diff --git a/parts/loading_elasticsearch.md → out-takes/loading_elasticsearch.md b/parts/loading_elasticsearch.md → out-takes/loading_elasticsearch.md
diff --git a/parts/online_evaluation.md → out-takes/online_evaluation.md b/parts/online_evaluation.md → out-takes/online_evaluation.md
diff --git a/parts/qualitative_evaluation.md → out-takes/qualitative_evaluation.md b/parts/qualitative_evaluation.md → out-takes/qualitative_evaluation.md
diff --git a/parts/introduction.md → parts/1.00_introduction.md b/parts/introduction.md → parts/1.00_introduction.md
diff --git a/parts/linked_open_data.md → parts/1.01_linked_open_data.md b/parts/linked_open_data.md → parts/1.01_linked_open_data.md
diff --git a/parts/open_data.md → parts/1.02_open_data.md b/parts/open_data.md → parts/1.02_open_data.md
diff --git a/parts/linked_data.md → parts/1.03_linked_data.md b/parts/linked_data.md → parts/1.03_linked_data.md
diff --git a/parts/public_procurement_domain.md → parts/1.04_public_procurement_domain.md b/parts/public_procurement_domain.md → parts/1.04_public_procurement_domain.md
@@ -24,10 +24,10 @@ Matchmaking in public procurement can be framed in its legal and economic contex
 
 Public procurement is a domain governed by law.
 We are focused on the Czech public procurement, for which there are two primary sources of relevant law, including the national law and the EU law.
-Public procurement in the Czech Republic is governed by the law no. 2016/134 [@CzechRepublic2016].
+Public procurement in the Czech Republic is governed by the act no. 2016/134 [@CzechRepublic2016].
 Czech Republic, as a member state of the European Union, harmonises its law with EU directives, in particular the directives 2014/24/EU [@EU2014a] and 2014/25/EU [@EU2014b] in case of public procurement.
 The first directive regulates public procurement of works, supplies, or services, while the latter one regulates public procurement of utilities, including water, energy, transport, and postal services.
-The law no. 2016/134 transposes these directives into the Czech legislation.
+The act no. 2016/134 transposes these directives into the Czech legislation.
 Besides legal terms and conditions to harmonize public procurement in the EU member states, these directives also define standard forms for EU public procurement notices,^[<http://simap.ted.europa.eu/web/simap/standard-forms-for-public-procurement>] which constitute a common schema of public notices.
 The directives design Tenders Electronic Daily ("Supplement to the Official Journal")^[<http://ted.europa.eu>] to serve as the central repository of public notices conforming to the standard forms.
 
@@ -152,16 +152,16 @@ As in open procedures, contracting authorities announce contracts publicly, but
 Contracting authorities then screen the interested bidders and send invitations to tender to the selected bidders.
 
 The chosen procedure type determines for which users is matchmaking relevant.
-Bidders can use matchmaking both in case of open and restricted procedures to be alerted about the current business opportunities in public procurement that are relevant for them.
+Bidders can use matchmaking both in case of open and restricted procedures to be alerted about the current business opportunities in public procurement that are relevant to them.
 Contracting authorities can use matchmaking in restricted procedures to get recommendations of suitable bidders.
 <!-- A potential issue: A restricted procedure is probably chosen when the contracting authority already knows which bidders to invite. -->
 Moreover, in case of the simplified under limit procedure, which is allowed in the Czech Republic for public contracts below a specified financial threshold, contracting authority can approach bidders directly.
-In such case, at least five bidders must be approached according to the law no. 2016/134 [@CzechRepublic2016]. <!-- <https://www.zakonyprolidi.cz/cs/2016-134#p53> -->
+In such case, at least five bidders must be approached according to the act no. 2016/134 [@CzechRepublic2016]. <!-- <https://www.zakonyprolidi.cz/cs/2016-134#p53> -->
 In that scenario, matchmaking can help recommend appropriate bidders to interest in the public contract.
 There are also other procedure types, such as innovation partnership, in which matchmaking is applicable to a lesser extent.
 
 An additional use case for similarity-based retrieval employed by matchmaking may occur during contract specification.
-The Czech law no. 2016/134 [@CzechRepublic2016] suggests contracting authorities to estimate contract price based on similar contracts. <!-- <https://www.zakonyprolidi.cz/cs/2016-134#f5805154> -->
+The Czech act no. 2016/134 [@CzechRepublic2016] suggests contracting authorities to estimate contract price based on similar contracts. <!-- <https://www.zakonyprolidi.cz/cs/2016-134#f5805154> -->
 In order to address this use case, based on incomplete descriptions of contracts matchmaking can recommend similar contracts, the actual prices of which can help estimate the price of the formulated contract.
 
 <!--

diff --git a/parts/matchmaking.md → parts/1.05_matchmaking.md b/parts/matchmaking.md → parts/1.05_matchmaking.md
diff --git a/parts/case_based_reasoning.md → parts/1.06_case_based_reasoning.md b/parts/case_based_reasoning.md → parts/1.06_case_based_reasoning.md
diff --git a/parts/statistical_relational_learning.md → ...s/1.07_statistical_relational_learning.md b/parts/statistical_relational_learning.md → ...s/1.07_statistical_relational_learning.md
diff --git a/parts/related_work.md → parts/1.08_related_work.md b/parts/related_work.md → parts/1.08_related_work.md
diff --git a/parts/data_preparation.md → parts/2.00_data_preparation.md b/parts/data_preparation.md → parts/2.00_data_preparation.md
diff --git a/parts/modelling.md → parts/2.01_modelling.md b/parts/modelling.md → parts/2.01_modelling.md
diff --git a/parts/public_contracts_ontology.md → parts/2.02_public_contracts_ontology.md b/parts/public_contracts_ontology.md → parts/2.02_public_contracts_ontology.md
diff --git a/parts/concrete_data_model.md → parts/2.03_concrete_data_model.md b/parts/concrete_data_model.md → parts/2.03_concrete_data_model.md
diff --git a/parts/extraction.md → parts/2.04_extraction.md b/parts/extraction.md → parts/2.04_extraction.md
diff --git a/parts/transformation.md → parts/2.05_transformation.md b/parts/transformation.md → parts/2.05_transformation.md
diff --git a/parts/linking.md → parts/2.06_linking.md b/parts/linking.md → parts/2.06_linking.md
diff --git a/parts/geocoding.md → parts/2.07_geocoding.md b/parts/geocoding.md → parts/2.07_geocoding.md
diff --git a/parts/linked_datasets.md → parts/2.08_linked_datasets.md b/parts/linked_datasets.md → parts/2.08_linked_datasets.md
diff --git a/parts/cpv.md → parts/2.09_cpv.md b/parts/cpv.md → parts/2.09_cpv.md
diff --git a/parts/ares.md → parts/2.10_ares.md b/parts/ares.md → parts/2.10_ares.md
diff --git a/parts/czech_addresses.md → parts/2.11_czech_addresses.md b/parts/czech_addresses.md → parts/2.11_czech_addresses.md
diff --git a/parts/zindex.md → parts/2.12_zindex.md b/parts/zindex.md → parts/2.12_zindex.md
diff --git a/parts/fusion.md → parts/2.13_fusion.md b/parts/fusion.md → parts/2.13_fusion.md
diff --git a/parts/loading.md → parts/2.14_loading.md b/parts/loading.md → parts/2.14_loading.md
diff --git a/parts/loading_sparql.md → parts/2.15_loading_sparql.md b/parts/loading_sparql.md → parts/2.15_loading_sparql.md
diff --git a/parts/loading_rescal.md → parts/2.16_loading_rescal.md b/parts/loading_rescal.md → parts/2.16_loading_rescal.md
diff --git a/parts/data_summary.md → parts/2.17_data_summary.md b/parts/data_summary.md → parts/2.17_data_summary.md
diff --git a/parts/methods.md → parts/3.00_methods.md b/parts/methods.md → parts/3.00_methods.md
diff --git a/parts/ground_truth.md → parts/3.01_ground_truth.md b/parts/ground_truth.md → parts/3.01_ground_truth.md
diff --git a/parts/sparql.md → parts/3.02_sparql.md b/parts/sparql.md → parts/3.02_sparql.md
@@ -117,7 +117,7 @@ Note that it is possible to infer a concept already included in the explicitly a
 In such case, the concept appears twice in the contract object, distinguished by its concept assignment.
 Similarly, the same inferred concept can be reached more times by expanding different concepts.
 Such concept is present once in the results of query expansion since the results form a set.
-Figures [@fig:expand-to-narrower] and [@fig:expand-to-broader] illustrate the query expansion, showing expansions to two-hop neighbourhoods. 
+The figures [-@fig:expand-to-broader] and [-@fig:expand-to-narrower] illustrate the query expansion, showing expansions to two-hop neighbourhoods. 
 
 ![Expansion to broader concepts](img/query_expansion_broader.png){#fig:expand-to-broader width=50%}
 

diff --git a/parts/tensor_factorization.md → parts/3.03_tensor_factorization.md b/parts/tensor_factorization.md → parts/3.03_tensor_factorization.md
diff --git a/parts/evaluation.md → parts/4.00_evaluation.md b/parts/evaluation.md → parts/4.00_evaluation.md
diff --git a/parts/offline_evaluation.md → parts/4.01_offline_evaluation.md b/parts/offline_evaluation.md → parts/4.01_offline_evaluation.md
diff --git a/parts/results_sparql.md → parts/4.02_results_sparql.md b/parts/results_sparql.md → parts/4.02_results_sparql.md
diff --git a/parts/results_rescal.md → parts/4.03_results_rescal.md b/parts/results_rescal.md → parts/4.03_results_rescal.md
diff --git a/parts/results_comparison.md → parts/4.04_results_comparison.md b/parts/results_comparison.md → parts/4.04_results_comparison.md
diff --git a/parts/conclusions.md → parts/5.00_conclusions.md b/parts/conclusions.md → parts/5.00_conclusions.md
diff --git a/parts/references.md → parts/A_references.md b/parts/references.md → parts/A_references.md
@@ -1,3 +1,6 @@
 \footnotesize
 
 # References {.unnumbered}
+
+<div id="refs"></div>
+
diff --git a/parts/software.md → parts/B_software.md b/parts/software.md → parts/B_software.md
diff --git a/parts/abbreviations.md → parts/C_abbreviations.md b/parts/abbreviations.md → parts/C_abbreviations.md
diff --git a/parts/metadata.yaml b/parts/metadata.yaml
@@ -0,0 +1,14 @@
+---
+title: Matchmaking of bidders and public contracts using linked open data
+author: Jindřich Mynarz
+institute: Department of Information and Knowledge Engineering, University of Economics
+date: 2017
+keywords:
+- matchmaking
+- recommender systems
+- case-based reasoning
+- linked data
+- open data
+- public procurement
+link-citations: true
+---
diff --git a/parts/acknowledgements.md → staging/0.00_acknowledgements.md b/parts/acknowledgements.md → staging/0.00_acknowledgements.md
diff --git a/parts/abstract_english.md → staging/0.01_abstract_english.md b/parts/abstract_english.md → staging/0.01_abstract_english.md
diff --git a/parts/abstract_czech.md → staging/0.02_abstract_czech.md b/parts/abstract_czech.md → staging/0.02_abstract_czech.md
diff --git a/text.md b/text.md