@azaroth42 We could nail everything down to very specific profiles - but in general it would be better to profile the content - what it contains - and negotiate the most convenient representation - encoding, language, CRS, version, precision etc - otherwise there is a combinatorial explosion of things that are implementation specific choices, and perhaps transformable, whereas the profile should really be about the community of practice's intent to interoperate - and hence not necessarily transformable. This fits best with existing practice where we already have negotiation over some aspects - what we are doing is adding either another aspect, or an extension point. (This Use Case is intended to register the requirement that other aspects are considered - we might still end up choosing a very specific non-extensible mechanism, but best not to do it out of ignorance of such use cases :-) -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/311#issuecomment-411004441 using your GitHub accountReceived on Tuesday, 7 August 2018 10:13:36 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:24 UTC