NL 6.2 Ed Broken references to requirements and Fix Updated recommendations UK 6.1.1 Note: Ed Change the system will if the Register The system will check the Register descriptor Text changed “If descriptor is available at the given URI through is available at the given URI through an HTTP an HTTP GET request to the URI with the GET request to the URI with the HTTP Accept HTTP Accept header set to header set to "application/x-ror-rdf+xml". Otherwise it will ask for the resource Otherwise it will ask for the resource using the using the standard HTTP GET request.” to standard HTTP GET request without an Accept header. 6.1.1 TG Req. 1 te http URI”. This may require specification. Updated to HTTp-URI “an The address of the document where to find it – is by it’s nature an URL. But it reasonable to – let the address of the document be identical to the HTTP-URI identifier of the document. 6.2 Para 1 te harvested”. So publishing the Please explain. Yes, the frequency of the harvesting it is the “automatically accrual period is all it takes to become only information required automatically harvestable? NL 6.1.1 Req 1 Ge By stating it must be an http URI, https is URI’ Accepted ‘http(s) prohibited. Consider allowing https. 6.1.1 Tg te What does that mean? Who Please consider to add clarification/definition. The examples are provided below in the text “well-defined”. defines? Where is it described? 2 6.1.1 Tg ed (example URI: ) is not dereferentiable at time The publication office is shortly going to make being it dereferenceable. 2 NL 6.1.1 Rec 2 Ge Not the URI of the foaf:Agent class, but the Remove Updated ‘class’. URI of the foaf:Agent individual should be provided UK 6.1.1 TG ge Not clear what "well-defined URI pattern" Accepted. Reworded to: means here. Same comment for 6.1.2 TG TG Recommendation 1 The URI of the 2 Recommendation 3 foaf:Agent should be taken from an organisation register or provided using a URI well-defined URI pattern. EXAMPLE Some examples are provided below:
NL 6.2 Ed Broken references to requirements and recommendations Fix Updated UK 6.1.1 Note: Ed Change “If the system will if the Register descriptor is available at the given URI through an HTTP GET request to the URI with the HTTP Accept header set to Otherwise it will ask for the resource using the standard HTTP GET request.” to The system will check the Register descriptor is available at the given URI through an HTTP GET request to the URI with the HTTP Accept header set to "application/x-ror-rdf+xml". Otherwise it will ask for the resource using the standard HTTP GET request without an Accept header. Text changed 6.1.1 TG Req. 1 te “an http URI”. This may require specification. The address of the document – where to find it – is by it’s nature an URL. But it reasonable to let the address of the document be identical to the HTTP-URI identifier of the document. Updated to HTTp-URI 6.2 Para 1 te “automatically harvested”. So publishing the accrual period is all it takes to become automatically harvestable? Please explain. Yes, the frequency of the harvesting it is the only information required NL 6.1.1 Req 1 Ge By stating it must be an http URI, https is prohibited. Consider allowing https. ‘http(s) URI’ Accepted 6.1.1 Tg 2 te “well-defined”. What does that mean? Who defines? Where is it described? Please consider to add clarification/definition. The examples are provided below in the text 6.1.1 Tg 2 ed (example URI: ) is not dereferentiable at time being The publication office is shortly going to make it dereferenceable. NL 6.1.1 Rec 2 Ge Not the URI of the foaf:Agent class, but the URI of the foaf:Agent individual should be provided Remove ‘class’. Updated UK 6.1.1 TG 2 ge Not clear what "well-defined URI pattern" means here. Same comment for 6.1.2 TG Recommendation 3 Accepted. Reworded to: TG Recommendation 1 The URI of the foaf:Agent should be taken from an organisation register or provided using a URI well-defined URI pattern. EXAMPLE Some examples are provided below:
inspire-tg-registers-and-register-federation-mig-t-comment-resolution.docx