- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Apr 2020 21:15:26 +0000
- To: public-hydra-logs@w3.org
>>5.1.1. Base URI Embedded in Content I agree. At first I thought about custom predicate for denoting a _local_ base but the RFC mentions media types and their syntax. >>5.1.2. Base URI from the Encapsulating Entity This seems it doesn't fit to the intermediate parent (as you named it in your commit to your client). The RFC mentions a situation when a document is enclosed within another being, (i.e. attachment to the email, IFrame within the HTML page). I think this is not the case of a resource being in relation with another one within the same document. >>5.1.3. URI used to retrieve the entity >>5.1.4. Default Base URI (application-dependent) These are already in use. No questions about it. It clearly looks like whatever we may want to add to make it happen will be outside of the mentioned RFC which may result in unexpected behavior. I feel like we may need something _extra_ added to the vocabulary/spec that servers will need to use explicitly in order to amend client's behavior in that matter. BTW. It is somehow unfortunate to have implementation of the feature in discussion without resolving it. Whatever reason you may want to use it will look like you want to support what you've already implemented. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/208#issuecomment-617418091 using your GitHub account
Received on Tuesday, 21 April 2020 21:15:27 UTC