<commit_before>==========
ISP format
==========
------------------------------------------------
Schema specification & implementation guidelines
------------------------------------------------

:Editor:
    Gu1 <<EMAIL>>
:Authors:
    FFDN diyisp schema working group
:Revision:
    draft-1 (0.1)
:Date:
    October 2013


**Abstract:**
 The ISP format is a file format created and supported by the FDN Federation (FFDN) in order to help ISPs sharing its value to document and publish relevent informations regarding their status and progress in a common format.


.. contents:: **Table of Contents**



1. Introduction
===============

The ISP format is meant to allow an ISP to share relevant data and informations, such as its number of subscribers, the URL of its websites, chatrooms, etc... It was mostly created with small/diy/non-profit ISPs in mind, such as those in the FFDN.

1.1. Definitions
----------------
* The ISP format itself is based on the JSON data format. The JavaScript Object Notation (JSON) format and its basic types are defined in [RFC4627]_.
* The ISP format is mostly specified as a JSON Schema file, a JSON-based format for defining the structure of JSON data. JSON Schema is defined in the following IETF draft [json-schema-04]_.
* HTTP... [RFC2616]_.
* The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]_.


2. JSON Schema definition of the format
=======================================<commit_msg>Clarify the HTTP definition in the spec<commit_after>==========
ISP format
==========
------------------------------------------------
Schema specification & implementation guidelines
------------------------------------------------

:Editor:
    Gu1 <<EMAIL>>
:Authors:
    FFDN diyisp schema working group
:Revision:
    draft-1 (0.1)
:Date:
    October 2013


**Abstract:**
 The ISP format is a file format created and supported by the FDN Federation (FFDN) in order to help ISPs sharing its value to document and publish relevent informations regarding their status and progress in a common format.


.. contents:: **Table of Contents**



1. Introduction
===============

The ISP format is meant to allow an ISP to share relevant data and informations, such as its number of subscribers, the URL of its websites, chatrooms, etc... It was mostly created with small/diy/non-profit ISPs in mind, such as those in the FFDN.

1.1. Definitions
----------------
* The ISP format itself is based on the JSON data format. The JavaScript Object Notation (JSON) format and its basic types are defined in [RFC4627]_.
* The ISP format is mostly specified as a JSON Schema file, a JSON-based format for defining the structure of JSON data. JSON Schema is defined in the following IETF draft [json-schema-04]_.
* The ISP format relies on HTTP/1.1 for data transfer [RFC2616]_.
* The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]_.


2. JSON Schema definition of the format
=======================================
{'fraction_non_alphanumeric': 0.18218497827436375, 'fraction_numerical': 0.01675977653631285, 'mean_word_length': 3.110969387755102, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3855453', 'n_tokens_mistral': 880, 'n_tokens_neox': 805, 'n_words': 424}