D-AC004.2 discussion points

ATT: replace it with:

         Define and design web resources interfaces to ensure interoperability.

HP: What is a web resource?

MITRE: I'm not sure what "properly" means.

I envision an architecture diagram with boxes that represent "components" and lines between some of
them to represent "interfaces".  The architecture would describe the functions of the components and
the interfaces at an abstract level.  (I don't know if that means XML Infoset, since SOAP 1.2 uses
that and I'm not sure what would be more abstract than Infoset).  Other WG's would use these
abstract descriptions to design more concrete definitions of the functions and interfaces, while
still leaving room for different implementation.  "Properly" means at the right level of abstraction
to be useful to WGs that design protocols, but not too prescriptive (unless we really decide to
limit choices for some good reason, like interoperability; ah, a tradeoff!).

NOK: This is a nice goal, but has little to do with this AC004.

W3C: Any design we do should be done properly, so I think that the design
part of the goal is unnecessary.

Originally, D-AC004.2 was talking about Web components. I asked
whether components were resources, and the goal was updated. I now
wonder if the CSF didn't want to talk about Web services. If not, I
don't think that it is our job to define the interface to a Web
resource, and it is already done: get a representation of a resource,
get metadata about this resource, store specified entity, etc.

Received on Wednesday, 8 May 2002 09:18:25 UTC