- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Fri, 8 Aug 2014 14:31:00 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-hydra@w3.org
Hi Markus, > 1) Do we want the new property to be called > a) expansionMechanism, > b) variableExpansion, or > c) variableRepresentation? c) sounds most easy and captures the thing best for me. > 2) What do we call the expanded value representation (mechanism described in [2])? > a) ExpandedRepresentation > b) CompleteRepresentation > c) something else? > > I'm leaning towards b) but am open for better names. The main characteristic about this option is that it explicitly differentiates between URIs and literals, and between literals of specific types and languages. How about ExplicitRepresentation? That seems a bit more precise than "Complete". Otherwise, a) ExpandedRepresentation is fine with me, too. > 3) Do we really want to use two hats (^^) in the expanded representation > knowing that we might introduce a Turtle representation in the future which > will make it difficult to distinguish them by just looking at the resulting > URL? Also unlike "$", the character "^" isn't allowed in a URL and needs to > be escaped [3] to %5E. > a) use one hat (^) > b) use two hats as Turtle does (^^) > c) use another character such as $ which doesn't need to be escaped > > I strongly favor c) What about the @ then for languages? I'd say b) because the function of the symbol is identical. Ruben
Received on Friday, 8 August 2014 12:31:35 UTC