Re: Alternatives to containers/collections (was Re: Requirements for a possible "RDF 2.0")

2010/1/15 Jeremy Carroll <>:

> I think optional features are, in general, a bad idea.
> They are technically flawed solutions to political problems.
> If there is not consensus that a feature should be in, then it is
> non-standard, and should not be included.
> See
> "The greatest way to undo the utility of a specification is with too many
> optional features."

I don't disagree, certainly valid if starting from scratch - but given
the current status of RDF, with baggage that people could maybe do
without, I suspect "optional" might be appropriate. If e.g. RDF
reification was dropped from the spec tomorrow, hard line, it's fairly
likely that it would break someone's setup.

The quiet deprecation thing again, I guess.


Received on Friday, 15 January 2010 17:32:47 UTC