I propose removal of section 3.3 "Client Implementation Requirements and Guidelines" as when I read it from the viewpoint of a potential player author, I do not really obtain any useful information from it in its current state.
I mean, if I come to DASH then I am already going to know what I will want to do seamless switching. There are some behavior-relevant clauses in 3.3.4 that might be useful for guiding an implementation but those points seem altogether dubious in value to me (why would I ignore something just because I cannot parse the Rating? I do not think this is realistic).
This is not to say that IOP could not benefit from client implementation guidelines (and indeed, it covers clients in various existing sections) but I think 3.3 is not what we need. Maybe if we restructure things we can assemble a new client implementation guidelines section of out clauses currently distributed across the document? It would be good to hear client developer comments here on what sort of guidelines actually matter for creating interoperable implementations.
sandersaares
commented
5 years ago
I propose removal of section 3.3 "Client Implementation Requirements and Guidelines" as when I read it from the viewpoint of a potential player author, I do not really obtain any useful information from it in its current state.
I mean, if I come to DASH then I am already going to know what I will want to do seamless switching. There are some behavior-relevant clauses in 3.3.4 that might be useful for guiding an implementation but those points seem altogether dubious in value to me (why would I ignore something just because I cannot parse the Rating? I do not think this is realistic).
This is not to say that IOP could not benefit from client implementation guidelines (and indeed, it covers clients in various existing sections) but I think 3.3 is not what we need. Maybe if we restructure things we can assemble a new client implementation guidelines section of out clauses currently distributed across the document? It would be good to hear client developer comments here on what sort of guidelines actually matter for creating interoperable implementations.