Skip to content

Commit

Permalink
Merge pull request #715 from handrews/format
Browse files Browse the repository at this point in the history
Add "uuid" format
  • Loading branch information
handrews committed Mar 18, 2019
2 parents eb25539 + 6cae0d0 commit ff48a42
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions jsonschema-validation.xml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@
<!ENTITY RFC3339 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3339.xml">
<!ENTITY RFC3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC3987 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3987.xml">
<!ENTITY RFC4122 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4122.xml">
<!ENTITY RFC4291 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4291.xml">
<!ENTITY RFC4329 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4329.xml">
<!ENTITY RFC4648 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4648.xml">
Expand Down Expand Up @@ -686,10 +687,22 @@
Reference (either an IRI or a relative-reference),
according to <xref target="RFC3987"/>.
</t>
<t hangText="uuid:">
A string instance is valid against this attribute if it is a valid
string representation of a UUID, according to <xref target="RFC4122"/>.
</t>
</list>
</t>
<t>
Note that all valid URIs are valid IRIs, and all valid URI References are
also valid IRI References.
</t>
<t>
Note also that the "uuid" format is for plain UUIDs, not UUIDs in URNs. An example
is "f81d4fae-7dec-11d0-a765-00a0c91e6bf6". For UUIDs as URNs, use the "uri" format,
with a "pattern" regular expression of "^urn:uuid:" to indicate the URI scheme and
URN namespace.
</t>
</section>

<section title="uri-template">
Expand Down Expand Up @@ -1073,6 +1086,7 @@
&RFC3339;
&RFC3986;
&RFC3987;
&RFC4122;
&RFC4291;
&RFC4648;
&RFC5322;
Expand Down

0 comments on commit ff48a42

Please sign in to comment.