Rob Sanderson

Representation was intentional. A resource cannot be prevented from having more than one class, but each representation can only expose one at a time.

@chiarcos I don't think anonymous classes are a good idea at all, and would propose in a profile of RDF that is intended to be simpler to implement and understand,...

@dbooth-boston I withdraw the issue, as this process is clearly never going to converge. We'll simply do our own thing, rather than trying to talk about it in an unfriendly...

How about -- when you retrieve a representation, then there is exactly one triple with rdf:type as the predicate per subject resource in the graph. Meaning that you can have...

I give up trying to have a meaningful discussion with @namedgraph present. @dbooth-boston, as the de-facto chair, I request that you enforce the code of ethics. "Just use complicated, not...

I also believe that a single class makes it easier to consume, as validation of the properties is easier and the use of traditionally understood techniques (including but not limited...

Suggest that this could be a tag in its own right for issues to discuss what should be in the easy profile and what not

Okay, I'll start ... Every resource should have exactly one class, given with `rdf:type`

@namedgraph It would make it easier for people who understand object-oriented programming and do not have a strong grasp of RDF (e.g. the target audience) to work with the data,...

@namedgraph I think you're missing the point of this exercise. Per @HughGlaser: > We should be very happy for people to get the "wrong" idea about RDF, if the gives...