W3C home > Mailing lists > Public > public-hydra@w3.org > January 2015

Re: Introduce VariableRepresentation class (ISSUE-80)

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Tue, 6 Jan 2015 10:02:11 +0100
Cc: Hydra <public-hydra@w3.org>
Message-Id: <6DC64B4F-915A-4D9F-BE78-D6776D75A3B3@ugent.be>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
> Actually, we try to avoid having a property and a class which differ only in
> their capitalization. Should we follow Schema.org's convention and name this
>   hydra:VariableRepresentationType

I'd be fine with that.

> instead of just
>   hydra:VariableRepresentation

Now that we're talking about naming: when documenting the properties,
I've found “variable representation" to be confusing:

      "@id": "hydra:VariableRepresentation",
      "@type": "hydra:Class",
      "subClassOf": "hydra:Resource",
      "label": "representation of variable values",
      "comment": "A representation specifies how to serialize variable values into strings.",
      "vs:term_status": "testing"

So even though it is called *VariableRepresentation*
it actually defines how *values* are represented.

I can live with either name, and we have discussed this before,
but I just wanted to point out my experience actually adding it to the voc.


Received on Tuesday, 6 January 2015 09:02:45 UTC

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