You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering what it might take to get the clarifying comment under InteractiveResource to be edited to remove the word "service". See quote. It is confusing to have InteractiveResource say that it is a service... The presence of "service" in the comment seems to diminish the usability and distinct identity of InteractiveResource. I suggest moving chat service under service. In my paper I suggest that services are business services and they are content services which transform content. A chat service is a business communication service. In contrast to Service I suggest in the paper, that InteractiveResources are mutable, navigable resources which do not act on different sets of content. If I have two or three data sets in the same structure and I want to transform each of them, I would need to use a service not an InteractiveResource. See paper for discussion.
Examples include forms on Web pages, applets, multimedia learning objects, chat services, or virtual reality environments.
The text was updated successfully, but these errors were encountered:
Greetings,
At DC-2022 I presented a paper [Preprint] where I compared and contrasted DCMIType InteractiveResource and Service.
I am wondering what it might take to get the clarifying comment under InteractiveResource to be edited to remove the word "service". See quote. It is confusing to have InteractiveResource say that it is a service... The presence of "service" in the comment seems to diminish the usability and distinct identity of InteractiveResource. I suggest moving chat service under service. In my paper I suggest that services are business services and they are content services which transform content. A chat service is a business communication service. In contrast to Service I suggest in the paper, that InteractiveResources are mutable, navigable resources which do not act on different sets of content. If I have two or three data sets in the same structure and I want to transform each of them, I would need to use a service not an InteractiveResource. See paper for discussion.
The text was updated successfully, but these errors were encountered: