human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "machine readable web apis with schema org action annotations"):
  Abstract: The schema.org initiative led by the four major search engines curates a vocabulary for describing web content. The number of semantic annotations on the web are increasing, mostly due to the industrial incentives provided by those search engines. The annotations are not only consumed by search engines, but also by other automated agents like intelligent personal assistants (IPAs). However, only annotating data is not enough for automated agents to reach their full potential. Web APIs should be also annotated for automating service consumption, so the IPAs can complete tasks like booking a hotel room or buying a ticket for an event on the fly. Although there has been a vast amount of effort in the semantic web services field, the approaches did not gain too much adoption outside of academia, mainly due to lack of concrete incentives and steep learning curves. In this paper, we suggest a lightweight, bottom-up approach based on schema.org actions to annotate Web APIs. We analyse schema.org vocabulary in the scope of lightweight semantic web services literature and propose extensions where necessary. We show that schema.org actions could be a suitable vocabulary for Web API description. We demonstrate our work by annotating existing Web APIs of accommodation service providers. Additionally, we briefly demonstrate how these APIs can be used dynamically, for example, by a dialogue system.

Includes members:
  Member "heuristics for publishing dynamic content as structured data with schema org":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "verification and validation of semantic annotations")
  Member "domain specific semantic validation of schema org annotations":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "a formal approach for customization of schema org based on shacl")
  Member "complete semantics to empower touristic service providers":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "verification and validation of semantic annotations")
  Member "semantify it a platform for creation publication and distribution of semantic annotations":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "rocketrml a nodejs implementation of a use case specific rml mapper")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.IR(Information Retrieval)