Skip to content

Fix filename incompatibility with Windows systems #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cabaret-pro wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix filename incompatibility with Windows systems #208

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions OpenRTB v3.0 FINAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -420,7 +420,7 @@ For AdCOM v1.x, the objects allowed here all of which are optional are one of th

This object carries data about the source of the transaction including the unique ID of the transaction itself, source authentication information, and the chain of custody.

NOTE: Attributes `ds`, `dsmap`, `cert`, and `digest` support digitally signed bid requests as defined by the [Ads.cert: Signed Bid Requests specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert:%20Signed%20Bid%20Requests%201.0%20BETA.md). As the Ads.cert specification is still in its BETA state, these attributes should be considered to be in a similar state.
NOTE: Attributes `ds`, `dsmap`, `cert`, and `digest` support digitally signed bid requests as defined by the [Ads.cert: Signed Bid Requests specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert-Signed-Bid-Requests-1.0-BETA.md). As the Ads.cert specification is still in its BETA state, these attributes should be considered to be in a similar state.

<table>
<tr>
Expand Down Expand Up @@ -980,7 +980,7 @@ Any intermediary receiving a bid request with this attribute is obligated to inc

To put these concepts into practice, publishers or their trusted agents must know how to generate their public/private key pairs, how to sign transaction digest strings, and how to communicate this and related information to their immediate exchange partners. Both publishers and those vendors wishing to authenticate requests must know the precise method of creating a digest string from bid request attributes and how to validate a signature given a public key.

For these details, please refer to [ads.cert Beta Specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert:%20Signed%20Bid%20Requests%201.0%20BETA.md).
For these details, please refer to [ads.cert Beta Specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert-Signed-Bid-Requests-1.0-BETA.md).

## Enumerations <a name="enumerations"></a>

Expand Down Expand Up @@ -1340,7 +1340,7 @@ OpenRTB v3.0 Specification
[https://github.com/InteractiveAdvertisingBureau/openrtb](https://github.com/InteractiveAdvertisingBureau/openrtb)

ads.cert Specification
[ads.cert beta specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert:%20Signed%20Bid%20Requests%201.0%20BETA.md)
[ads.cert beta specification](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/ads.cert-Signed-Bid-Requests-1.0-BETA.md)

ads.text Specification
[iabtechlab.com/ads-txt](https://iabtechlab.com/ads-txt)
Expand Down
0 ads.cert: Signed Bid Requests 1.0 BETA.md → ads.cert-Signed-Bid-Requests-1.0-BETA.md
View file
Open in desktop
File renamed without changes.