Skip to content
This repository was archived by the owner on Mar 23, 2026. It is now read-only.

Commit 174e1c6

Browse files
committed
Updates to correct markdown errors
1 parent 3434b68 commit 174e1c6

2 files changed

Lines changed: 20 additions & 26 deletions

File tree

README.md

Lines changed: 18 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
## Welcome to the Blazegraph Database
2-
Blazegraph™ DB is a ultra high-performance graph database supporting Blueprints and RDF/SPARQL APIs. It supports up to 50 Billion edges on a single machine and has a enterprise features for High Availability, Scale-out architecture, and [GPU Acceleration](https://www.blazegraph.com/product/gpu-accelerated/). It is in production use for Fortune 500 customers such as EMC, Autodesk, and many others. It is supporting key [Precision Medicine](http://www.syapse.com) applications and has wide-spread usage for life science applications. It is used extensively to support Cyber anaytics in commercial and government applications. It powers the Wikimedia Foundation's [Wikidata Query Service](https://query.wikidata.org/). See the latest [Feature Matrix](http://www.blazegraph.com/product/).
1+
## Welcome to the Blazegraph Database ##
2+
Blazegraph™ DB is a ultra high-performance graph database supporting Blueprints and RDF/SPARQL APIs. It supports up to 50 Billion edges on a single machine. It is in production use for Fortune 500 customers such as EMC, Autodesk, and many others. It is supporting key [Precision Medicine](http://www.syapse.com) applications and has wide-spread usage for life science applications. It is used extensively to support Cyber anaytics in commercial and government applications. It powers the Wikimedia Foundation's [Wikidata Query Service](https://query.wikidata.org/).
33

44
![image](http://blog.blazegraph.com/wp-content/uploads/2015/07/blazegraph_by_systap_favicon.png)
55

@@ -9,11 +9,11 @@ Please see the release notes in [releases](bigdata/src/releases) for version cha
99

1010
Please also visit us at our: [website](https://www.blazegraph.com), [wiki](https://wiki.blazegraph.com), and [blog](https://blog.blazegraph.com/).
1111

12-
Find an issue? Need help? See [JIRA](https://jira.blazegraph.com) or purchase [Support](https://www.blazegraph.com/buy).
12+
Find an issue? Need help? See [JIRA](https://jira.blazegraph.com).
1313

1414
Reporting a security issue: [Security Reporting](Security.md).
1515

16-
###Quick Start with the Executable Jar
16+
### Quick Start with the Executable Jar ###
1717
Up and running with Blazegraph in under 30 seconds: [Quick Start](https://wiki.blazegraph.com/wiki/index.php/Quick_Start).
1818

1919
### Deploying in Production ###
@@ -34,20 +34,22 @@ There are three basic options:
3434
1. **Setup a reverse-proxy configuration with authentication**: You can setup an http or https reverse proxy configuration that has authentication and forward requests to the local Blazegraph instance (typically running on localhost:9999). This is a good option with [Nginx](https://community.openhab.org/t/using-nginx-reverse-proxy-authentication-and-https/14542) and [Apache](https://stackoverflow.com/questions/5011102/apache-reverse-proxy-with-basic-authentication).
3535

3636
##### Mitigating Cross-Site Request Forgery (CSRF) #####
37-
If you enable authentication and expose the Blazegraph workbench, you should also take steps to protect against CSRF. Tomcat8 provides a (CSRF filter)[https://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#CSRF_Prevention_Filter_for_REST_APIs] that can be configured. For Jetty, if you configure authentication the default value for `SecurityHandler.setSessionRenewedOnAuthentication(true)` can also be used. CSRF protection may require REST clients to implement HTTP headers to be used to interact with the service.
37+
If you enable authentication and expose the Blazegraph workbench, you should also take steps to protect against CSRF. Tomcat8 provides a [CSRF filter](https://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#CSRF_Prevention_Filter_for_REST_APIs) that can be configured. For Jetty, if you configure authentication the default value for `SecurityHandler.setSessionRenewedOnAuthentication(true)` can also be used. CSRF protection may require REST clients to implement HTTP headers to be used to interact with the service.
3838

39-
### Building the code
39+
### Building the code ###
4040
As a quick start, run `mvn install -DskipTests` or the utility script `./scripts/mavenInstall.sh `.
4141

4242
For more detailed maven information see the [wiki](https://wiki.blazegraph.com/wiki/index.php/MavenNotes).
4343

44-
###Samples and Examples
44+
If you build with Java 7, you need to add Maven options for TLS 1.2, i.e. `export MAVEN_OPTS="-Dhttps.protocols=TLSv1.2"`.
45+
46+
### Samples and Examples ###
4547
There are code samples and examples to get started with the Blazegraph Database [here] (https://github.com/blazegraph/blazegraph-samples). Tinkerpop3 examples are included directly within the Tinkerpop3 repository per below.
4648

47-
###Javadocs
49+
### Javadocs ###
4850
Click here to view the lastest [API Javadocs](https://blazegraph.github.io/database/apidocs/index.html).
4951

50-
###Maven Central
52+
### Maven Central ###
5153
Starting with the 2.0.0 release, the Blazegraph Database is available on Maven Central. To include the core platform and dependencies, include the artifact below in your dependencies. [Developing with Maven](https://wiki.blazegraph.com/wiki/index.php/MavenNotes) has notes on developing with Blazegraph Database source code and Maven.
5254

5355
```
@@ -74,13 +76,13 @@ If you'd just link the Blazegraph Database dependencies without any of the exter
7476
</dependency>
7577
```
7678

77-
###Deployers
79+
### Deployers ###
7880

7981
Starting with 2.0.0, the default context path for deployment is `http://localhost:9999/blazegraph/`. There are also Maven artifacts for WAR deployers (`blazegraph-war`), executable Jar files (`blazegraph-jar`), [Debian Package](blazegraph-deb/) (`blazegraph-deb`), [RPM](blazegraph-rpm/) (`blazegraph-rpm`), and a [Tarball](blazegraph-tgz/) (`blazegraph-tgz`).
8082

8183
The `bigdata-war` and `bigdata-jar` artifacts are included for legacy purposes and use the `/bigdata/` context path.
8284

83-
###Tinkerpop3
85+
### Tinkerpop3 ###
8486
Tinkerpop3 supports requires Java 1.8 and is now in a separate repository. See [Tinkerpop3](https://github.com/blazegraph/tinkerpop3). It is also available as Maven Central artifact.
8587

8688
```
@@ -92,19 +94,11 @@ Tinkerpop3 supports requires Java 1.8 and is now in a separate repository. See
9294
9395
```
9496

95-
###Triple Pattern Fragment (TPF) Server
96-
There is a [Blazegraph Triple Pattern Fragment TPF](https://github.com/blazegraph/BlazegraphBasedTPFServer) server that supports [Linked Data Fragments](http://linkeddatafragments.org/).
97-
98-
```
99-
<dependency>
100-
<groupId>com.blazegraph</groupId>
101-
<artifactId>BlazegraphBasedTPFServer</artifactId>
102-
<version>0.1.0</version>
103-
</dependency>
104-
```
97+
### Triple Pattern Fragment (TPF) Server ###
98+
There is a [Blazegraph Triple Pattern Fragment TPF](https://github.com/hartig/BlazegraphBasedTPFServer) server that supports [Linked Data Fragments](http://linkeddatafragments.org/).
10599

106-
###Blazegraph Python Client
107-
There is a Blazegraph Python Client [here] (https://github.com/blazegraph/blazegraph-python)
100+
### Blazegraph Python Client ###
101+
There is a Blazegraph Python Client [here](https://github.com/blazegraph/blazegraph-python)
108102

109-
###Blazegraph Dot Net RDF Client
103+
### Blazegraph Dot Net RDF Client ###
110104
There is a Blazegraph Dot Net RDF Client [here](https://github.com/blazegraph/blazegraph-dotnetrdf)

Security.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
##Reporting a Blazegraph Security Issue##
1+
## Reporting a Blazegraph Security Issue ##
22

33
For customers and Blazegraph users, please send an email to security [at] blazegraph.com to report a security issue. You may send an encrypted message using the public key below.
44

55
This alias is monitored on a daily basis. All security reports are acknowledged within 24 hours. Mitigations for reported security issues are made in a reasonable timeframe, which may be as quickly as 24 hours for high-severity issues.
66

7-
###Public Key###
7+
### Public Key ###
88
Please use the public key below for transmitting any sensitive information to the security alias.
99

1010
```

0 commit comments

Comments
 (0)