DOCSLIB.ORG

Processing Xpath/Xquery to Be Aware of Xlink Hyperlinks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Processing Xpath/Xquery to Be Aware of Xlink Hyperlinks 2nd EUROPEAN COMPUTING CONFERENCE (ECC’08) Malta, September 11-13, 2008 Processing XPath/XQuery to be Aware of XLink Hyperlinks LULE AHMEDI MENTOR ARIFAJ University of Prishtina, Computer Engineering Kodra e diellit p.n. 10000 Prishtinë, Kosova {lule.ahmedi | mentor.arifaj}@fiek.uni-pr.edu Abstract: - XML Linking Language (XLink) as a W3C recommendation represents the standard way how to use links within XML documents. With these links, it is possible to select arbitrarily narrow content, and not restricted to selecting the whole document as it is the case with HTML hyperlinks. There are few implementations for XLink despite the fact that it is a recommendation since 2001. Most of these implementations are focused on how to handle XLink links while browsing rather then query them. There is an implementation using LDAP that uses other data model than XML and another one that is an extension of eXist a XML database system to support XLinks. We extended another well-known and widely used XPath/XQuery open source system named Saxon-B. The Saxon-B is an in-memory system and is capable to be used with programming languages to support the XML features implemented on it. We describe our extension in several steps and illustrate it with algorithms and samples. We complement the discussion by comparing our system with existing systems (eXist and LDAP), and confirm that our system is a complement and not a duplication of these systems. Keywords: - XML, Querying XML, XLink hyperlinks, XML Applications, LDAP. 1 Introduction 2 XLink Hyperlinks and Current Linking is an important feature of the Web, and with it Bottlenecks the web becomes the single and complex system [14]. Hyperlinks or links are very important part of the web XML Linking Language (XLink) is an XML based [6] and today they are very popular and widely used on language which specifies the standard way how to the Web. XLink presents the standard way of incorporate and use hyperlinks within XML documents. incorporating hyperlinks into XML documents. XLink These XML documents could be located into intranets links are incorporated at XML elements within XML and into the Internet. XLink is a World Wide Web documents. An XML element could be an XLink links Consortium (W3C) recommendation since year 2001 if it consists of the type attribute of the namespace xlink. [1]. Based on our investigation, there are few XLink presents two types of links, simple links with implementations of this recommendation when attribute xlink:type = “simple” and extended links with comparing with other W3C recommendations, attribute value xlink:type=”extended”[1]. especially XPath/XQuery [2][3]. For XLink these XLink simple links are similar with the Hypertext implementations could be partially dedicated only one Markup Language (HTML) hyperlinks. But at simple part of XLink or dedicated for browsers and from the links every element could be a link not only a querying point of view there are very few predefined “a” element as it is for HTML hyperlinks. implementations such as using eXist [5] and With XLink extended links is possible to create more Lightweight Directory Access Protocol (LDAP) [4]. complicated linking structure [1]. At extended links the On the section 2 we describe more details about XLinks XML element containing the attribute xlink:type = and the need for query XML documents that have “extended” serves as a container for other nested XLink links. Also we describe the similarities and elements which should have set the xlink:type attribute differences between our implementation and eXist and to one of these values “locator”, “resource”, “arc” or LDAP implementations. On the section 3 we describe “title”[1]. our steps towards the implementation. And at the end There are numerous systems implementating section 4, we discuss about related work and conclusion XPath/XQuery technology, whereas for XLink, there of our implementation that it is not a duplication of the are only few implementations [3, 2]. For XPath/XQuery existing implementations but a complementary there exists wide range of tools in different platforms implementation for query interlinking XML documents. and build with different programming languages. Based on [2] more of these implementations for XLink are for browsers and few regarding querying of the links. During our investigations we have found that there exist ISSN:1790-5109 217 ISBN: 978-960-474-002-4 2nd EUROPEAN COMPUTING CONFERENCE (ECC’08) Malta, September 11-13, 2008 two implementations for query XML documents in XPath defines 13 axis [17] and the mostly used axis are presence of XLink links. Extension of LDAP [4] to child, attribute, ancestor and descendent [8]. support XPath query at the XLink links is one of them. We base our implementation on the following logical This system is based on another data model than XML model: The XML model is not a tree, but rather a graph data model and it maps XPath query to that data model. with the major part of nodes inter-connected via And the other is extension of eXist system which is a child/attribute arcs, and an additional type of arc native XML database system [5]. The eXist extension is allowed referring into local or remote portions of graph based on a logical model proposed from Wolfgang May nodes. in [7]. From the query (or database) point of view there An XML element declared as XLink link can contain an are not any official drafts [7] or recommendation how to href attribute. This attribute in case of simple links handle interlinked XML documents and these could be specifies the location where the XML element points to, seen as an open issue from the XLink recommendations. and in general it has the form as in Expression 1. So based on facts that XPath/XQuery is widely used and Expression 1: href = uri-reference [4] the need to handle links into XML documents, on the The uri-reference could be expressed as in expression 2. other hand very few existences of the implementations Expression 2: uri-reference = uri#fragment [4] regarding querying these documents, we have Where uri represents the Internet resource and could be implemented an extension of “open-source”[10] system expressed with expression 3 and the fragment is express named Saxon-B. Saxon-B is an XPath 2.0, XQuery 1.0 with XPointer (a W3C recommendation [11]) pointers. and XSLT 2.0 [8], system developed in Java platform Expression 3: uri = sheme://host:port/path [4] and is a main memory XQuery processor or in-memory As our aim is to extend an existing XPath/XQuery processor [9]. For Saxon-B we can say that it is a native system this lead us to a condition that fragment is an XML processor together with eXist processor whereas XPath expression and we based this on the already LDAP is not native XML. The difference between LDAP extension [4]. LDAP and Saxon-B is more explicit as LDAP is based Condition 1: fragment = xpathexpression on another data model than XML based model. The Example 1: xpathexpression = //country/cities/city difference between Saxon-B and eXist could be seen as We have taken the saxon-resources9-0-0-1[10] and “how to use these tools”. Saxon-B can be use as an explore it using NetBeans 6.0.1[12]. extension to the application build with different Example 2: part of the adopted distributed mondial programming tools (Java, C#, etc.) whereas eXist is an database[13] from countries.xml file. XML database system. <country car_code="AL" area="28750"> First, we are aware of possibilities to use Saxon-B in <name>Albania</name> top of another application and then via the application … to execute XPath expressions. <capital xlink:type="simple" Second, simulate executions of XPath expressions and dbxlink:transparent="make-attribute insert-nodes" XPath functions as XQuery expressions [7] from the xlink:href="http://localhost/Mondial- new application. Distributed/Cities/cities- But, this approach could lead us to a more simulation of AL.xml#//cities/city[name='Tirane']"/> an implementation rather than a new extension of an <cities xlink:type="simple" existing XPath/XQuery system. dbxlink:transparent="drop-element insert-nodes" xlink:href="http://localhost/Mondial- Distributed/Cities/cities-AL.xml#//cities/city"/> 3 Extending XPath/XQuery to Model <encompassed xlink:type="simple" XLink Hyperlinks dbxlink:transparent="group-in-element insert-nodes" xlink:href="http://localhost/Mondial- 3.1 The XML Data Model with XLink Distributed/continents.xml#//continents/continent[name Our framework of extending XPath/XQuery bases on ='Europe']" modeling XML documents in presence of XLink links. percentage="100"/> XPath models the XML document [15] as a tree of <neighbor xlink:type="simple" nodes. In presence of links between XML documents, dbxlink:transparent="duplicate-element insert-bodies" the tree model expands to a graph model. In the graph xlink:href="http://localhost/Mondial- model, XPath expressions can still be used for Distributed//countries.xml#//countries/country[@car_co navigation [16], as also stated in the logical model de='GR']" introduced in [5]. borderlength="282"/> <neighbor xlink:type="simple" dbxlink:transparent="duplicate-element insert-bodies" ISSN:1790-5109 218 ISBN: 978-960-474-002-4 2nd EUROPEAN COMPUTING CONFERENCE (ECC’08) Malta, September 11-13, 2008 xlink:href="http://localhost/Mondial- B = False Distributed//countries.xml#//countries/country[@car_co de='MK']" If ( S contains (@xlink:href) ) borderlength="151"/> Let S1 = S (part before @xlink:href with <neighbor xlink:type="simple" added “/string(@xlink:href)” ) dbxlink:transparent="duplicate-element insert-bodies" Let S2 = S (part after @xlink:href) xlink:href="http://localhost/Mondial- Let B = True Distributed//countries.xml#//countries/country[@car_co Else de='YU']" // everything remains as in Saxon-B borderlength="287"/> End If-Else </country> If ( B == True ) First, in order to be handled elements’ attributes derived Let A be the array of results from processing of S1, from XLink recommendation the processors should which could have 0, 1 or more members with values recognize the xlink namespace which most of the time of @xlink:href attribute, in the XML documents it is declared at the beginning of /* the document with expression 4.
Load more

Recommended publications
  • Xincluding Plain-Text Fragments for Symmetry and Profit Piotr Bański, University of Warsaw, [email protected]
    XIncluding plain-text fragments for symmetry and profit Piotr Bański, University of Warsaw, [email protected] <xi:include href=”resource.xml” parse=”text|xml” Summary xpointer=”fragment_identifier” /> XML for the annotation of images, audio or video is by necessity of the stand-off kind: the annotations are virtually anchored to the parse=“xml” parse=“text” binary stream (typically by x,y coordinates or time offsets). Work on language resource annotation has extended this approach to plain text, where annotations are anchored by character offsets. This is referred to as extreme stand-off markup. No generic XML tools or standards support it, but... they could, fairly easily. inclusion of inclusion of inclusion of inclusion of Rationale the entire the entire a fragment a fragment ISO Language Annotation Framework (e.g. Ide & Romary, 2007) re- XML text of an XML of a text commends that data be kept as read-only plain text, with one or mo- resource resource resource resource re layers of XML annotation identifying individual spans of charac- ters and adding metadata to them (identifying e.g. segments of va- rious levels of granularity, parts of speech, syntactic or discourse @xpointer present functions, etc.) no @xpointer However, the only way to handle this (as evidenced by the American National Corpus), is to use in-house tools working on correspon- dence semantics for hyperlinks (see Bański, 2010, for terminology What makes it impossible right now? and more remarks). 1. XInclude Ban: XInclude Rec, 3.1: “The xpointer attribute must not be present when parse="text".” But character streams can do better! Because text is what XML is built out of and what it contains, instead of correspondence 2.
    [Show full text]
  • W3C Working Draft: Scalable Vector
    next contents properties index Scalable Vector Graphics (SVG) 1.0 Specification W3C Working Draft 03 March 2000 This version: http://www.w3.org/TR/2000/03/WD-SVG-20000303 (Available as: PDF, zip archive of HTML) Previous public version: http://www.w3.org/TR/1999/WD-SVG-19991203/ Latest public version: http://www.w3.org/TR/SVG/ Editor: Jon Ferraiolo <[email protected]> Authors: See author list Copyright ©1998, 1999, 2000 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This specification defines the features and syntax for Scalable Vector Graphics (SVG), a language for describing two-dimensional vector and mixed vector/raster graphics in XML. Status of this document This document is a public review draft version of the SVG specification. This working draft attempts to address review comments that were received during the initial Last Call period, which started 12 August 1999, and also incorporates other modifications resulting from continuing collaboration with other working groups and continuing work within the SVG working group. With the publication of this draft, the SVG specification enters a second "Last Call". The second Last Call period will end on 31 March, 2000. The SVG specification is going through a second Last Call review process to provide the public and other working groups an opportunity to review the changes to the specification since the initial Last Call period. A complete list of all changes since the initial Last Call version of the specification is available in Appendix L: Change History. Last call comments should be sent to [email protected].
    [Show full text]
  • Introduction to Scalable Vector Graphics
    Introduction to Scalable Vector Graphics Presented by developerWorks, your source for great tutorials ibm.com/developerWorks Table of Contents If you're viewing this document online, you can click any of the topics below to link directly to that section. 1. Introduction.............................................................. 2 2. What is SVG?........................................................... 4 3. Basic shapes............................................................ 10 4. Definitions and groups................................................. 16 5. Painting .................................................................. 21 6. Coordinates and transformations.................................... 32 7. Paths ..................................................................... 38 8. Text ....................................................................... 46 9. Animation and interactivity............................................ 51 10. Summary............................................................... 55 Introduction to Scalable Vector Graphics Page 1 of 56 ibm.com/developerWorks Presented by developerWorks, your source for great tutorials Section 1. Introduction Should I take this tutorial? This tutorial assists developers who want to understand the concepts behind Scalable Vector Graphics (SVG) in order to build them, either as static documents, or as dynamically generated content. XML experience is not required, but a familiarity with at least one tagging language (such as HTML) will be useful. For basic XML
    [Show full text]
  • Understanding JSON Schema Release 2020-12
    Understanding JSON Schema Release 2020-12 Michael Droettboom, et al Space Telescope Science Institute Sep 14, 2021 Contents 1 Conventions used in this book3 1.1 Language-specific notes.........................................3 1.2 Draft-specific notes............................................4 1.3 Examples.................................................4 2 What is a schema? 7 3 The basics 11 3.1 Hello, World!............................................... 11 3.2 The type keyword............................................ 12 3.3 Declaring a JSON Schema........................................ 13 3.4 Declaring a unique identifier....................................... 13 4 JSON Schema Reference 15 4.1 Type-specific keywords......................................... 15 4.2 string................................................... 17 4.2.1 Length.............................................. 19 4.2.2 Regular Expressions...................................... 19 4.2.3 Format.............................................. 20 4.3 Regular Expressions........................................... 22 4.3.1 Example............................................. 23 4.4 Numeric types.............................................. 23 4.4.1 integer.............................................. 24 4.4.2 number............................................. 25 4.4.3 Multiples............................................ 26 4.4.4 Range.............................................. 26 4.5 object................................................... 29 4.5.1 Properties...........................................
    [Show full text]
  • Progressive Imagery with Scalable Vector Graphics -..:: VCG Rostock
    Progressive imagery with scalable vector graphics Georg Fuchsa, Heidrun Schumanna, and Ren´eRosenbaumb aUniversity of Rostock, Institute for Computer Science, 18051 Rostock, Germany; bUC Davis, Institute of Data Analysis & Visualization, Davis, CA 95616 U.S.A. ABSTRACT Vector graphics can be scaled without loss of quality, making them suitable for mobile image communication where a given graphics must be typically represented in high quality for a wide range of screen resolutions. One problem is that file size increases rapidly as content becomes more detailed, which can reduce response times and efficiency in mobile settings. Analog issues for large raster imagery have been overcome using progressive refinement schemes. Similar ideas have already been applied to vector graphics, but an implementation that is compliant to a major and widely adopted standard is still missing. In this publication we show how to provide progressive refinement schemes based on the extendable Scalable Vector Graphics (SVG) standard. We propose two strategies: decomposition of the original SVG and incremental transmission using (1) several linked files and (2) element-wise streaming of a single file. The publication discusses how both strategies are employed in mobile image communication scenarios where the user can interactively define RoIs for prioritized image communication, and reports initial results we obtained from a prototypically implemented client/server setup. Keywords: Progression, Progressive refinement, Scalable Vector Graphics, SVG, Mobile image communication 1. INTRODUCTION Vector graphics use graphic primitives such as points, lines, curves, and polygons to represent image contents. As those primitives are defined by means of geometric coordinates that are independent of actual pixel resolutions, vector graphics can be scaled without loss of quality.
    [Show full text]
  • SVG Exploiting Browsers Without Image Parsing Bugs
    SVG Exploiting Browsers without Image Parsing Bugs Rennie deGraaf iSEC Partners 07 August 2014 Rennie deGraaf (iSEC Partners) SVG Security BH USA 2014 1 / 55 Outline 1 A brief introduction to SVG What is SVG? Using SVG with HTML SVG features 2 Attacking SVG Attack surface Security model Security model violations 3 Content Security Policy A brief introduction CSP Violations 4 Conclusion Rennie deGraaf (iSEC Partners) SVG Security BH USA 2014 2 / 55 A brief introduction to SVG What is SVG? What is SVG? Scalable Vector Graphics XML-based W3C (http://www.w3.org/TR/SVG/) Development started in 1999 Current version is 1.1, published in 2011 Version 2.0 is in development First browser with native support was Konqueror in 2004; IE was the last major browser to add native SVG support (in 2011) Rennie deGraaf (iSEC Partners) SVG Security BH USA 2014 3 / 55 A brief introduction to SVG What is SVG? A simple example Source code <? xml v e r s i o n = ” 1 . 0 ” encoding = ”UTF-8” standalone = ” no ” ? > <svg xmlns = ” h t t p : // www. w3 . org / 2 0 0 0 / svg ” width = ” 68 ” h e i g h t = ” 68 ” viewBox = ”-34 -34 68 68 ” v e r s i o n = ” 1 . 1 ” > < c i r c l e cx = ” 0 ” cy = ” 0 ” r = ” 24 ” f i l l = ”#c8c8c8 ” / > < / svg > Rennie deGraaf (iSEC Partners) SVG Security BH USA 2014 4 / 55 A brief introduction to SVG What is SVG? A simple example As rendered Rennie deGraaf (iSEC Partners) SVG Security BH USA 2014 5 / 55 A brief introduction to SVG What is SVG? A simple example I am not an artist.
    [Show full text]
  • XBRL and the Semantic
    How can we exploit XBRL and Semantic Web technologies to realize the opportunities? Track 3: Case Studies in XBRL Solutions 19th XBRL International Conference, Paris, 23rd June 2009 Dave Raggett <[email protected]> W3C Fellow – Financial data & Semantic Web Member – XBRL INT Technical Standards Board With some slides from Diane Mueller, JustSystems 1 Outline XBRL: adding semantics to business reports World Wide Adoption of XBRL Users and use cases for XBRL Realizing the potential Feeding the Semantic Web ◦ XBRL, XLink, RDF, Turtle, SPARQL, OWL ◦ Web APIs, Smart Searches, Web Scale Queries ◦ Findings June 2009 2 So What is XBRL? eXtensible Business Reporting Language ◦ a freely available electronic language for financial reporting. ◦ based on XML, XML Schema and XLink ◦ based on accepted financial reporting standards and practices to transport financial reports across all software, platforms and technologies Business reporting includes, but is not limited to: ◦ financial statements, ◦ financial and non-financial information ◦ general ledger transactions ◦ regulatory filings such as annual and quarterly financial statements. “XBRL allows software vendors, programmers and end users who adopt it as a specification to enhance the creation, exchange, and comparison of business reporting information” from xbrl.org June 2009 3 Not just a number XBRL binds each reported fact to a concept in a reporting taxonomy e.g. US GAAP, IFRS ◦ Each concept can be bound to a description and its definition in the accounting literature Hierarchy of Terse label, EN Currency, amount Reporting period concepts Impairment of goodwill: $M21 3 months to 2009-04-30 Description Impairment of goodwill: Loss recognized during the period that results from the write-down of goodwill after comparing the implied fair value of reporting unit goodwill with the carrying amount of that goodwill.
    [Show full text]
  • Extended Link Visualization with DHTML: the Web As an Open Hypermedia System
    Extended Link Visualization with DHTML: The Web as an Open Hypermedia System Glenn Oberholzer and Erik Wilde Computer Engineering and Networks Laboratory Swiss Federal Institute of Technology, Z¨urich TIK Report 125 January 2002 Abstract The World Wide Web is by far the most successful hypermedia system, its name often being used synonymously for the Internet. However, it is based on a rather restricted hy- permedia model with limited linking functionality. Even though underlying systems may provide a richer data model, there is still the question of how to present this informa- tion in a Web-based interface in an easily understandable way. Assuming an underlying system similar to Topic Maps, which allows storing, managing, and categorizing meta data and links, we propose a presentation of extended links. We try to provide a usable way for users to handle the additional functionality. The mechanism is based on already available technologies like DHTML. It is one facet of our approach to make the Web more interconnected and to work towards a more richly and openly linked Web. Keywords: Electronic publishing (020), Graphic design (029), Hypermedia (036), Internet (045), World Wide Web (084), XLink, Linkbases, DHTML 1 Introduction Compared to many other hypermedia systems [24,11,16], the linking capabilities of the World Wide Web are rather limited. It only makes use of a few concepts of hypermedia. In recent years, however, new recommendations issued by the W3C like XML [3], XLink [10], and XPointer [9], or ISO/IEC’s Topic Maps [19] have tried to overcome this shortcoming. Due to the popularity of the Web, efforts have to be made to integrate and improve the current system with more sophisticated hypermedia concepts.
    [Show full text]
  • Information Technology - Object Management Group XML Metadata Interchange (XMI)
    ISO/IEC 19509:2014(E) Date: April 2014 Information technology - Object Management Group XML Metadata Interchange (XMI) formal/2014-04-06 This version has been formally published by ISO as the 2014 edition standard: ISO/IEC 19509. ISO/IEC 19509:2014(E) Table of Contents 1 Scope ................................................................................................. 1 2 Conformance ...................................................................................... 1 2.1 General ....................................................................................................1 2.2 Required Compliance ...............................................................................1 2.2.1 XMI Schema Compliance ................................................................................. 1 2.2.2 XMI Document Compliance .............................................................................. 1 2.2.3 Software Compliance ....................................................................................... 2 2.3 Optional Compliance Points .....................................................................2 2.3.1 XMI Extension and Differences Compliance .................................................... 2 3 Normative References ........................................................................ 2 4 Terms and Definitions ......................................................................... 3 5 Symbols .............................................................................................. 3 6 Additional
    [Show full text]
  • ULAD Data Relationships Using Xlink and MISMO Arcroles
    Uniform Loan Application Dataset (ULAD) Data Relationships Using Xlink and MISMO Arcroles Document Document Version 1.1 March 27, 2018 This document relates to the Uniform Mortgage Data Program®, an effort undertaken jointly by Fannie Mae and Freddie Mac at the direction of the Federal Housing Finance Agency. ©2018 Fannie Mae and Freddie Mac. All Rights Reserved. MISMO® is a registered trademark of the Mortgage Industry Standards Maintenance Organization. Document Revisions DOCUMENT REVISIONS Date Change 3/27/2018 Added ASSET is associated with ROLE, LIABILITY is associated with ROLE, and EXPENSE is associated with ROLE to the ULAD Xlink ArcRole section 3/27/2018 Condensed COUNSELING_EVENT is associated with ROLE into one row 3/27/2018 Modified the xlink:label for CURRENT_INCOME_ITEM from INCOME_ITEM_n to CURRENT_INCOME_ITEM_n in the ULAD Xlink Arcroles section and Appendix A (Code Sample) 3/27/2018 Modified Asset to Associated Liabilities under ULAD Xlink Arcroles section to read Asset (Owned Property) instead of Owned Property (Asset) because the relationship is from the Asset container to the Liability container 3/27/2018 Added Document Revisions table and updated page numbers in Table of Contents Data Relationships Using Xlink and MISMO Arcroles Page 2 of 29 Version 1.1 Table of Content Table Of Contents Document Revisions ................................................................................................................. 2 Acronyms and Abbreviations.....................................................................................................
    [Show full text]
  • Semantic Sensor Observation Service
    Wright State University CORE Scholar The Ohio Center of Excellence in Knowledge- Kno.e.sis Publications Enabled Computing (Kno.e.sis) 5-2009 SemSOS: Semantic Sensor Observation Service Cory Andrew Henson Wright State University - Main Campus Josh Pschorr Wright State University - Main Campus Amit P. Sheth Wright State University - Main Campus, [email protected] Krishnaprasad Thirunarayan Wright State University - Main Campus, [email protected] Follow this and additional works at: https://corescholar.libraries.wright.edu/knoesis Part of the Bioinformatics Commons, Communication Technology and New Media Commons, Databases and Information Systems Commons, OS and Networks Commons, and the Science and Technology Studies Commons Repository Citation Henson, C. A., Pschorr, J., Sheth, A. P., & Thirunarayan, K. (2009). SemSOS: Semantic Sensor Observation Service. 2009 International Symposium on Collaborative Technologies and Systems: May 18-22, 2009, Baltimore, Maryland, USA, 44-53. https://corescholar.libraries.wright.edu/knoesis/333 This Article is brought to you for free and open access by the The Ohio Center of Excellence in Knowledge-Enabled Computing (Kno.e.sis) at CORE Scholar. It has been accepted for inclusion in Kno.e.sis Publications by an authorized administrator of CORE Scholar. For more information, please contact [email protected]. 1 SemSOS: Semantic Sensor Observation Service Cory A. Henson, Josh K. Pschorr, Amit P. Sheth, and Krishnaprasad Thirunarayan Kno.e.sis Center, Department of Computer Science and Engineering Wright State University, Dayton, OH 45435 [email protected], [email protected], [email protected], [email protected] enabled by semantic modeling and what advantages this Abstract provides to standard SOS.
    [Show full text]
  • XHTML+Rdfa 1.1 - Third Edition Table of Contents
    XHTML+RDFa 1.1 - Third Edition Table of Contents XHTML+RDFa 1.1 - Third Edition Support for RDFa via XHTML Modularization W3C Recommendation 17 March 2015 This version: http://www.w3.org/TR/2015/REC-xhtml-rdfa-20150317/ Latest published version: http://www.w3.org/TR/xhtml-rdfa/ Implementation report: http://www.w3.org/2010/02/rdfa/wiki/CR-ImplementationReport Previous version: http://www.w3.org/TR/2014/PER-xhtml-rdfa-20141216/ Previous Recommendation: http://www.w3.org/TR/2013/REC-xhtml-rdfa-20130822/ Editor: Shane McCarron, Applied Testing and Technology, Inc., [email protected] Please check the errata for any errors or issues reported since publication. This document is also available in these non-normative formats: XHTML+RDFa, Diff from Previous Recommendation, Postscript version, and PDF version The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2015 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply. Abstract RDFa Core 1.1 [RDFA-CORE [p.61] ] defines attributes and syntax for embedding semantic markup in Host Languages. This document defines one such Host Language. This language is a superset of XHTML 1.1 [XHTML11-2e [p.61] ], integrating the attributes as defined in RDFa Core 1.1. This document is intended for authors who want to create XHTML Family documents that embed rich semantic markup. - 1 - Status of This Document XHTML+RDFa 1.1 - Third Edition Status of This Document This section describes the status of this document at the time of its publication.
    [Show full text]