Metalinks / Code Commit Log

Commit	Date
[r512] by antbryan add implementors bit	2010-01-02 18:50:45	Tree
[r511] by antbryan Remove Securing Metalinks section, work into Security Considerations	2009-12-31 22:45:03	Tree
[r510] by antbryan metalinkhttp-14 final	2009-12-31 21:33:02	Tree
[r509] by antbryan clarify priority attribute	2009-12-24 19:08:29	Tree
[r508] by antbryan secdir review from Radia Perlman	2009-12-24 07:39:33	Tree
[r507] by antbryan (metalinkUri)	2009-12-23 06:49:34	Tree
[r506] by antbryan Example fragments ...	2009-12-23 06:36:25	Tree
[r505] by t-tujikawa Made priority optional in 4.2.8. metaurl and 4.2.16. url according to the schema in Appendix B.	2009-12-23 05:18:10	Tree
[r504] by antbryan Matthias Fuchs: remove dynamic element, make it an attribute of origin element	2009-12-22 23:25:29	Tree
[r503] by antbryan Brian Carpenter gen-art review: This is a bit picky, but section 4.1.2 contains a series of rules like this one: o metalink:file elements MAY contain exactly one metalink:copyright element. Note that (if parsed rigorously according to RFC2119) this does not forbid an element that contains more than one metalink:copyright element. To be rigorous, you'd have to add "and MUST NOT contain more than one such element".	2009-12-21 05:48:49	Tree

[r512] by antbryan

add implementors bit

2010-01-02 18:50:45

Tree

[r511] by antbryan

Remove Securing Metalinks section, work into Security Considerations

2009-12-31 22:45:03

Tree

[r510] by antbryan

metalinkhttp-14 final

2009-12-31 21:33:02

Tree

[r509] by antbryan

clarify priority attribute

2009-12-24 19:08:29

Tree

[r508] by antbryan

secdir review from Radia Perlman

2009-12-24 07:39:33

Tree

[r507] by antbryan

(metalinkUri)

2009-12-23 06:49:34

Tree

[r506] by antbryan

Example fragments ...

2009-12-23 06:36:25

Tree

[r505] by t-tujikawa

Made priority optional in 4.2.8. metaurl and 4.2.16. url according to the schema in Appendix B.

2009-12-23 05:18:10

Tree

[r504] by antbryan

Matthias Fuchs: remove dynamic element, make it an attribute of origin element

2009-12-22 23:25:29

Tree

[r503] by antbryan

Brian Carpenter gen-art review:
This is a bit picky, but section 4.1.2 contains a series of rules like
this one:

o metalink:file elements MAY contain exactly one metalink:copyright
element.

Note that (if parsed rigorously according to RFC2119) this does not forbid an
element that contains more than one metalink:copyright element. To be rigorous,
you'd have to add "and MUST NOT contain more than one such element".

2009-12-21 05:48:49

Tree

Metalinks Code

Code Commit Log