W3C home > Mailing lists > Public > public-hydra@w3.org > December 2014

variable representations edited for spec

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Mon, 22 Dec 2014 20:46:33 +0100
Message-Id: <EE80A8D0-48A4-4796-B424-6E6C8EEC6CD9@ugent.be>
To: Hydra <public-hydra@w3.org>
Dear all,

I have turned the IriTemplate variabel discussion [1][2] into a spec proposal [3].
Your comments are welcome!

While writing this down, I came across 3 potential issues:

1. Should hydra:BasicRepresentation and hydra:ExplicitRepresentation
    have a superclass hydra:VariableRepresentation?
    This would allow to set a specific range
    on the hydra:variableRepresentation property.

2. Currently, hydra:variableRepresentation's domain is hydra:IriTemplate.
    Just to ensure that this is not an oversight, do we want to:
    - Have this only on hydra:IriTemplate?
      Then all variables of the template have the same representation type.
    - Have this only on hydra:IriTemplateMapping?
      Then variables of the template can have different representation types.
    - Allow both of the above.
      Then variables of the template can have different representation types,
      but we can also easily make them all the same.

3. Section 5.2 of the document (“Templated Links”) has now become large.
    I was tempted to subsection this, but that would not be in line
    with the rest of the document's structure.
    Given a rewrite for the entire document is pending, I did not act yet.



[1] https://github.com/HydraCG/Specifications/issues/30
[2] http://lists.w3.org/Archives/Public/public-hydra/2014Oct/0119.html
[3] https://github.com/HydraCG/Specifications/pull/79
Received on Monday, 22 December 2014 19:47:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:44 UTC