W3C home > Mailing lists > Public > public-ddwg@w3.org > October 2007

RE: [VOC] Do we really need a property in the vocabulary for each markup or variety of them

From: Rhys Lewis <rhys@volantis.com>
Date: Tue, 2 Oct 2007 02:10:30 -0600 (MDT)
To: 'Josť Manuel Cantera Fonseca' <jmcf@tid.es>, <public-ddwg@w3.org>
Message-ID: <006301c804cc$19833d90$981e140a@volantisuk>

I think that now you are proposing path-based access to properties. I have
no problem with that. Indeed the Ontology already supports and uses this
approach [1].

However, the general feeling in DD up until now has been to have a flat
space of name/value pairs for the vocabulary and API. That contradicts any
hierarchy of properties.

If the group changes its mind and embraces hierarchies, then the hierarchy
SHOULD be the same as that in the ontology.

Best wishes


> -----Original Message-----
> From: public-ddwg-request@w3.org
> [mailto:public-ddwg-request@w3.org] On Behalf Of Josť Manuel
> Cantera Fonseca
> Sent: 01 October 2007 14:51
> To: public-ddwg@w3.org
> Subject: [VOC] Do we really need a property in the vocabulary
> for each markup or variety of them
> Hi,
> I was thinking about the issue of having a property for each
> variety of things that can depend on versions of the same
> technology, like CSS, markup, DOM, Javascript, etc. For
> example, CSS can be CSS Mobile Profile 1.0, W-CSS, CSS Level
> 1, CSS Level 2, CSS Level 2 revision 1, CSS 3, etc.
> One option for avoiding such a nigthmare would be to have
> some standard subproperties that allow the retrieval of
> particularities around an specific property. In the case of
> the CSS example, we would have
> ddr.getProperty("CSS_Support").getProperty("Version") and we
> could obtain some value that indicates the specific version supported
> Also the same could apply to HTML
> ddr.getProperty("HTML_Support").getProperty("Profile")
> ddr.getProperty("HTML_Support").getProperty("Version")
> What do you think?
> Best Regards
Received on Tuesday, 2 October 2007 08:10:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:00:15 UTC