Multiple URI/URL per resource (1)

Slides:



Advertisements
Similar presentations
FpML Versioning An AWG Discusion Document. Namespace URIs & Versions An XML parser locates the schema for a document based on its namespace URI To be.
Advertisements

FpML Versioning An AWG Discusion Document. Versioning in FpML To Date Based on major.minor numbering –Major increments to indicate a breaking change –Minor.
LIS650lecture 1 XHTML 1.0 strict Thomas Krichel
Naming, Addressing, & Discovery
II. Basic Web Concepts.
OpenSG Service Definition, Feb 2010 RESTful Service Discussions Shawn Hu.
XML Namespaces Kanda Runapongsa Dept. of Computer Engineering Khon Kaen University.
SOAP Quang Vinh Pham Simon De Baets Université Libre de Bruxelles1.
Internet Networking Spring 2006 Tutorial 12 Web Caching Protocols ICP, CARP.
3.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 3: Introducing Active Directory.
Introduction to XLink Transparency No. 1 XML Information Set W3C Recommendation 24 October 2001 (1stEdition) 4 February 2004 (2ndEdition) Cheng-Chia Chen.
XML Namespaces Andrey Smirnov CSCI 7818 September 21, 2000.
XML files (with LINQ). Introduction to LINQ ( Language Integrated Query ) C#’s new LINQ capabilities allow you to write query expressions that retrieve.
Working with Namespaces Combining XML Vocabularies in a Compound Document.
WORKING WITH NAMESPACES
XP New Perspectives on XML Tutorial 4 1 XML Schema Tutorial – Carey ISBN Working with Namespaces and Schemas.
WSDL and Schemas Discussion CMIS F2F January 27, 2009 Gary Gershon
XP New Perspectives on XML Tutorial 6 1 TUTORIAL 6 XSLT Tutorial – Carey ISBN
WORKING WITH XSLT AND XPATH
ODATA DELTAS Deltas provide a hypermedia-driven solution for retrieving changes to a given set of data.
XP 1 DECLARING A DTD A DTD can be used to: –Ensure all required elements are present in the document –Prevent undefined elements from being used –Enforce.
WebDAV Issues Munich IETF August 11, Property URL encoding At present, spec. allows encoding of the name of a property so it can be appended to.
Lecture 22 XML querying. 2 Example 31.5 – XQuery FLWOR Expressions ‘=’ operator is a general comparison operator. XQuery also defines value comparison.
ECA 228 Internet/Intranet Design I XSLT Example. ECA 228 Internet/Intranet Design I 2 CSS Limitations cannot modify content cannot insert additional text.
CITA 330 Section 6 XSLT. Transforming XML Documents to XHTML Documents XSLT is an XML dialect which is declared under namespace "
XSLT Kanda Runapongsa Dept. of Computer Engineering Khon Kaen University.
RDF and XML 인공지능 연구실 한기덕. 2 개요  1. Basic of RDF  2. Example of RDF  3. How XML Namespaces Work  4. The Abbreviated RDF Syntax  5. RDF Resource Collections.
XP New Perspectives on XML, 2nd Edition Tutorial 2 1 TUTORIAL 2 WORKING WITH NAMESPACES.
Chapter 27 The World Wide Web and XML. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.27-2 Topics in this Chapter The Web and the Internet.
Tutorial 13 Validating Documents with Schemas
1 Tutorial 12 Working with Namespaces Combining XML Vocabularies in a Compound Document.
What is SOAP? Luciano Piccoli. SOAP – Simple Object Access Protocol  SOAP is an XML based protocol to let software components and applications communicate.
 defined as Extensible Markup Language (XML) is a set of rules for encoding documents  Defines structure and data.
Lecture 23 XQuery 1.0 and XPath 2.0 Data Model. 2 Example 31.7 – User-Defined Function Function to return staff at a given branch. DEFINE FUNCTION staffAtBranch($bNo)
 XML derives its strength from a variety of supporting technologies.  Structure and data types: When using XML to exchange data among clients, partners,
Jackson, Web Technologies: A Computer Science Perspective, © 2007 Prentice-Hall, Inc. All rights reserved Chapter 7 Representing Web Data:
BOF-1147, JavaTM Technology and WebDAV: Standardizing Content Management Java and WebDAV Juergen Pill Team Leader Software AG Remy Maucherat Software Engineer.
Jan Pettersen Nytun, UIA, page 1 Knowledge Representation Part IV The Semantics Web Starting with XML Jan Pettersen Nytun, UiA.
Building a Data Warehouse
Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.
This template provides guidance for the execution of task, Analyze Capabilities (EA.040). It is in a presentation format that may be used to present.
Unit 4 Representing Web Data: XML
Data Structures and Design in Java © Rick Mercer
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
WORKING WITH NAMESPACES
Chapter 20 Lists, Stacks, Queues, and Priority Queues
Data Virtualization Tutorial: JSON_TABLE Queries
2016 and Beyond: Advanced tips for Developers and users David J. Just
Internet Networking recitation #12
Chapter 7 Representing Web Data: XML
IETF WebDAV Working Group
Hash Tables and Associative Containers
March 17, 1999 Judy Slein WebDAV Collections March 17, 1999 Judy Slein
New Perspectives on XML
Collaborative Authoring Support for the Next Generation
Jonathan Rosenberg dynamicsoft
Property Registry Rationale
Section 10.1 Groups.
WebDAV Collections Breakout Session
WebDAV Design Overview
Part 1. Preparing for the exercises
WEB SERVICES From Chapter 19, Distributed Systems
Introduction to Active Directory Directory Services
Quiz Points 1 Rules Raise your hand if you know the question
WebDAV Advanced Collection Requirements
Result: Yes - ; No - ; Abstain - .
WebDAV Collections Protocol
Focusing Your CSS Selectors
Section 9.1 Groups.
New Perspectives on XML
Presentation transcript:

Multiple URI/URL per resource (1) Long discussion on list, key issues were: Can a WebDAV resource have more than one URI? Can a WebDAV collection resource have more than one URI? Resolution: yes, any WebDAV resource can have more than one URI. Are terms URI/URL used consistently? Resolution: some inconsistent use was fixed in -10, some may linger. Needs review.

Multiple URI/URL per resource (2) Does the draft distinguish between URI/URL and resource correctly? Resolution: The draft was changed so that URI/URL and resource are properly distinguished so its clear when requirements affect URI/URL, and when they affect resources. Open issues: Discussion of collections can use some work to make intent more clear. Others?

Namespace Consistency (1) There was significant discussion/confusion on the list about WebDAV requirements for namespace consistency. “An HTTP URL namespace is said to be consistent if it meets the following conditions: for every URL in the HTTP hierarchy there exists a collection that contains that URL as an internal member. The root, or top-level collection of the namespace under consideration is exempt from the previous rule.”

Namespace Consistency (2) “Neither HTTP/1.1 nor WebDAV require that the entire HTTP URL namespace be consistent. However, certain WebDAV methods are prohibited from producing results that cause namespace inconsistencies.” For example, COPY and MOVE have require the destination namespace to be consistent.

Namespace Consistency (3) “For all WebDAV compliant resources A and B, identified by URIs U and V, for which U is immediately relative to V, B MUST be a collection that has U as an internal member URI.” So, if the resource with URL http://foo.com/bar/blah is WebDAV compliant and if the resource with URL http://foo.com/bar/ is WebDAV compliant then the resource with URL http://foo.com/bar/ must be a collection and must contain URL http://foo.com/bar/blah as an internal member.

Namespace Consistency (4) “Collection resources MAY list the URLs of non-WebDAV compliant children in the HTTP URL namespace hierarchy as internal members but are not required to do so.” For example, if the resource with URL http://foo.com/bar/blah is not WebDAV compliant and the URL http://foo.com/bar/ identifies a collection then URL http://foo.com/bar/blah may or may not be an internal member of the collection with URL http://foo.com/bar/.

Namespace Consistency (5) “If a WebDAV compliant resource has no WebDAV compliant children in the HTTP URL namespace hierarchy then the WebDAV compliant resource is not required to be a collection.”

XML attributes in property values If a property value contained in a PROPPATCH “set” instruction contains XML attributes associated with the XML elements of the property, what should the server do with them? 1. Store them, and return them on later retrievals 2. Throw them away Spec. is currently silent on this issue.