Re: [dxwg] New namespace dcat2 for DCAT2 ?

I'd say (I imagine uncontroversially), that defining a new namespace for DCAT2 should be an absolute last resort. Doing so would set the clock back in terms of establishing DCAT's acceptance - and it already has a lot of competition. Even if you were to define a new namespace, you'd then have the problem of people using, say, dcat:Distribution when in fact, oh silly developer, you meant dcat2:Distribution; don't you know the difference? 

No - unless there are strong reasons backed by real world evidence, stick with the existing namespace.

But... don't fret too much. Removing a domain restriction or other such relaxing of the rules isn't cause to consider a new namespace. Even tightening semantics would only entail a new namespace if you had clear evidence of people using the existing looser semantics - which as Simon says, I think would be surprising.

I remember many years ago, Chaals McN saying that people add domain and range constraints to try and push people to use their vocabulary they way they want it used. Actually, all it does is to restrict your audience. If you need to specify domains and ranges for the thing to work, OK. If you can live without them, don't do it. People are much more likely to use your terms if they can use them the way they want to. Hence schema.org's 'domainIncludes' notion - which may be useful here?

The alternative is to go down the route followed by SSN/SOSA where a simple lightweight vocabulary, SOSA, is extended and the semantics are more tightly defined by the more sophisticated SSN. If the WG really feels that a separate namespace is needed for DCAT2
1. Strip out as many semantic restrictions as possible from DCAT (and goodness knows, there aren't many)
2. Define DCAT2 as an extension - or, given the DXWG context - I guess the world is profile ;-)

But again, this should be a last resort. At the end of the day, DCAT is doing a pretty straightforward job - it probably doesn't need a lot of semantics for everyday, widespread use. 

-- 
GitHub Notification of comment by philarcher
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/131#issuecomment-366165887 using your GitHub account

Received on Friday, 16 February 2018 07:50:16 UTC