page 2:
[..] All new entity registrationsperformed on or after that date [..]
[..] All new entity registrations performed on or after that date [..]
[..] SHALL be accurately reflectedin entity metadata [..]
[..] SHALL be accurately reflected in entity metadata [..]
page 3:
[..] make use of the Federation Operator’s registryto register entities [..]
[..] make use of the Federation Operator’s registry to register entities [..]
[..] becoming a member of the Federation as an Identity Provider isdocumented at: [..]
[..] becoming a member of the Federation as an Identity Provider is documented at: [..]
[..] the prospective member has legal capacity andrequires [..]
[..] the prospective member has legal capacity and requires [..]
[..] for example asa result of corporate name changes or merger [..]
[..] for example as a result of corporate name changes or merger [..]
page 4:
[..] indicate that the Federation Operatoris the registrar [..]
[..] indicate that the Federation Operator is the registrar [..]
Reformat the RegistrationInfo metadata extension example, from:
http://efis.ethernet.edu.et/docs/MRPS20121110
to:
http://efis.ethernet.edu.et/docs/MRPS20121110
page 5:
[..] the domain owner on a per-entity basis and scopecompliant [..]
[..] the domain owner on a per-entity basis and scope compliant [..]
[..] DNS domain names but there canbe left most extensions [..]
[..] DNS domain names but there can be left most extensions [..]
[..] MUST be an absolute URI using the http, httpsor urn schemes [..]
[..] MUST be an absolute URI using the http, https or urn schemes [..]
page 6:
[..] from Federation members needs to becommunicated from or confirmed [..]
[..] from Federation members needs to be communicated from or confirmed [..]
[..] modify the Federation metadata at any time inorder to [..]
[..] modify the Federation metadata at any time in order to [..]