
	Where results make sense

Topic: PSVI

Related Topics

SSLIOP

Light rail

Convulsion

BRP

Frolic

BJJ

Integrin

6x86

Map

Yellow Pack

Caria

Yami

Lammi

Casino

CodeCon

In the News (Thu 10 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	PSVI architectural discussion from Tim Bray on 2002-06-22 (www-tag@w3.org from June 2002)
		Use of PSVI contents The XML Schema WG is currently engaged in investigating which pieces of the PSVI are of potential interest and assembling use cases.
		The PSVI contents are heterogeneous The PSVI's contents have the sole defining characteristic that they are generated as a result of schema validation.
		Coupling specs to PSVI as it exists today is architecturally unsound The PSVI is a grab-bag of stuff that's defined as being the outcome of a particular operation; any attempt to pretend that all its contents can be talked about, addressed, or used in a uniform way is just misguided.
	lists.w3.org /Archives/Public/www-tag/2002Jun/0146.html (1247 words)

	Potential new issue: PSVI considered harmful from Tim Bray on 2002-06-12 (www-tag@w3.org from June 2002)
		Potential new issue: PSVI considered harmful from Tim Bray on 2002-06-12 (www-tag@w3.org from June 2002)
		The PSVI is distinguished from the normal XML infoset as follows: - the addition of default element/attribute values provided in the schema - addition of type information declared in the schema, i.e.
		These are sufficiently problematic that the IETF is about to recommend they not be used at all, and I for one think there is a good case that they should be deprecated for architectural reasons.
	lists.w3.org /Archives/Public/www-tag/2002Jun/0085.html (811 words)

	Post Schema Validation Infoset (PSVI) API
		The API defines a way to access the XML Schema components, such as complex types, simple types, and element declarations, and interfaces to access the PSVI from a document instance when the DOM is used and in a streaming way when SAX is used.
		The main two interfaces to access the PSVI information are the ElementPSVI and AttributePSVI interfaces, which expose augmentations such as [validity], [validation attempted], [type definition], [schema default].
		To expose the PSVI via an API that provides a streaming document infoset, such as SAX or Xerces Native Interface (XNI), we defined the PSVIProvider interface to be implemented by the parser.
	www.idealliance.org /papers/dx_xml03/html/abstract/07-00-03.html (455 words)

	An API to Query XML Schema Components and the PSVI
		In addition, the PSVI will contain the property [schema normalized value], which is the normalized value of the information item (as validated); for element information items, this property will only appear if the element’s type is simple.
		The PSVI also provides information about the type definition used for validation of the element or attribute information; two alternate sets of properties may be included in the PSVI, depending on whether the schema processor is light-weight or not.
		In general, there are two types of applications working with the DOM that would want to retrieve PSVI: applications that build the DOM tree from scratch in memory and applications that parse an existing XML document and modify it in memory.
	idealliance.org /papers/dx_xmle04/papers/02-05-02/02-05-02.html (4232 words)

	Re: [xsl] With or without PSVI (Site not responding. Last check: 2007-10-14)
		My point is (a) that subtle changes in behaviour due to presence/non-presence of psvi is bad, and (b) if it was the WGs job to describe them, it would have an incentive to keep the list short (like changing the casting rule above to something sensible)...
		I also have a vague feeling that there is a quite simple (and XPath 1 like) language lurking under the surface of "type-exception-policy-flexible-XPath 2.0".
		And it seems kind of strange to spend hundreds of pages to define type safe construction/casting rules, and then follow that up with: "if the types don't match, the processor will make them match anyway, just as in the old days".
	www.xslt.com /xsl-list/2002-05/msg00796.html (625 words)

	Re: Objections to / uses of PSVI?
		I'd like to be able to have a template that matches all elements in > a certain group, for example "all block elements".
		I'd like to have access to the PSVI so that I can have access > to the contents of appinfo elements from within the stylesheet.
		I thought the PSVI was going to hold type info and validation status.
	www.xsltdebugger.com /xmldev/200205/post30980.html (390 words)

	short notes: XML schema languages, PSVI, Infoset
		Out of many candidates for XML schema language W3C XML Schema is the only one to introduce PSVI or post-schema validation infoset.
		PSVI is returned by schema processor analogous to how Infoset is returned by parsers.
		PSVI provides not only information on validation of an XML document but also type information on elements and attributes as well as their default values.
	notes.antville.org /stories/79176 (166 words)

	Dan Holmsand - With or without PSVI
		It seems to me that if you stay away from "instance of", "cast" (and perhaps a few other related functions/operators), and if your source document doesn't contain any XSD list types, you would get essentially the same output (thanks to "automatic" casts).
		You could also maybe lose some precision in numerical calculations if a PSVI is produced (since the calculations could use e.g.
		Something like "If a PSVI is provided you may also use instance of, xf:data, and count on automagic sequence construction from XML Schema list types.
	sources.redhat.com /ml/xsl-list/2002-05/msg00791.html (356 words)

	xml-dev - Objections to / uses of PSVI? (Site not responding. Last check: 2007-10-14)
		Since this already exists with DTDs, it seems any controversy here should have existed before the PSVI came to being.
		My guess is that this is where the greatest controversy / utility is. On the utility side, it means you can do type-aware programming.
		It seems that the only people who would be interested are a very small group of applications such as validators and editors who want to tell the user where their document is invalid.
	lists.xml.org /archives/xml-dev/200205/msg00910.html (279 words)

	The Cover Pages: Rick Jelliffe on NRL and DSDL (Defaults, PSVI)
		Rick Jelliffe on NRL and DSDL (Defaults, PSVI)
		Rick Jelliffe on Namespace Routing Language and DSDL (Defaults, PSVI)
		The Schematron schema would not pick up any new PSVI items.
	xml.coverpages.org /JelliffeDSDL200306.html (863 words)

	WebLogic Server 8.1 API Reference: Package weblogic.apache.xerces.xni.psvi
		Represent a PSVI item for one attribute information item.
		Represent a PSVI item for one element information item.
		Represent a PSVI item for one element or one attribute information item.
	edocs.bea.com /wls/docs81/javadocs/weblogic/apache/xerces/xni/psvi/package-summary.html (39 words)

	Re: Objections to / uses of PSVI?
		>Part of the problem may be that nobody knows what the PSVI is; there is >no specification of it anywhere except in XML Schemas part 1, where it is >hard to separate from the surrounding spec.
		Previous by thread: Re: Objections to / uses of PSVI?
		Trademarks— Stylus Studio®, a product from DataDirect Technologies, is a registered trademark of Progress Software Corporation in the U.S. and other countries.
	www.xmlstudio.com /xmldev/200205/post40950.html (351 words)

	Xerces, XInclude and PSVI
		Now, I try to put some XML file into an project file, which is an XML file with XInclude.
		Now, the problem is that I'm not able anymore to get the PSVI for XML elements.
		In other words, when the XInclude is resolved, I cannot validate the included XML files.
	forums.devshed.com /archive/t-139832 (127 words)

	Regular Fragmentations and the PSVI (Site not responding. Last check: 2007-10-14)
		Although there is an XML representation of the PSVI available from the XSV validator, this representation isn't especially workable for transmission.
		The output of regular fragmentations is always directly serializable as XML and can be used as XML by other processors with no understanding of the fragmentation processing that took place.
		W3C XML Schema processors perform several different tasks, both validating documents and painting (annotating) them with type and other information which is accessible from the PSVI.
	www.simonstl.com /articles/regfrag/recombine.html (178 words)

	Re: Adding nodes to a PSVI generated document again (Site not responding. Last check: 2007-10-14)
		Adding nodes to a PSVI generated document again Jakub Kahovec (1k)
		Re: Adding nodes to a PSVI generated document again Michael Glavassevich (2k)
		Re: Adding nodes to a PSVI generated document again Jakub Kahovec (2k)
	subscriber.diezmil.com /message/xerces-j-user@xml.apache.org/245482.html (183 words)

	PSVI and XPath 2.0 data model
		At 6:58 PM +0100 5/7/02, Michael Kay wrote: >The XPath 2.0 data model is based on the PSVI, not on the schema definition >language.
		It's explicitly an aim that you can generate the PSVI by >validation against a DTD, it should also be possible to generate it by >validation against other schema languages.
		For instance, is it acceptable for an XSLT2 processor to replace all child elements with attributes or convert rectangle elements into circle elements?
	www.stylusstudio.com /xmldev/200205/post60360.html (473 words)

	Re: RE: PSVI and XPath 2.0 data model
		Re: RE: PSVI and XPath 2.0 data model
		Previous by thread: RE: PSVI and XPath 2.0 data model
		Next by thread: RE: PSVI and XPath 2.0 data model
	edn.exln.com /xmldev/200205/post10430.html (150 words)

	Re: PSVI
		Maybe there should be another flag that says whether types matter in the document.
		If they don't, you don't need to do schema processing to get a "PSVI".
		You can create it forthwith and get on with your work.
	www.xsltstudio.com /xmldev/200103/post10080.html (274 words)

	Adding nodes to a PSVI generated document again
		Adding nodes to a PSVI generated document again
		I am trying to add new node to a PSVI generated document but the problem is that the node I am adding doesn't
		I'd tried to set the document 'psvi' and 'validate' fetures and then normalized document by calling method
	www.opensubscriber.com /message/xerces-j-user@xml.apache.org/240931.html (144 words)

	RE: how to retrieve psvi information from a parser (Site not responding. Last check: 2007-10-14)
		Re: how to retrieve psvi information from a parser Alberto Massari (2k)
		RE: how to retrieve psvi information from a parser Lin Guo (1k)
		RE: how to retrieve psvi information from a parser Alberto Massari (1k)
	subscriber.diezmil.com /message/xerces-c-dev@xml.apache.org/284986.html (137 words)

	What use is the PSVI? (Site not responding. Last check: 2007-10-14)
		Who benefits by the existence/imposition of the PSVI?
		Who is harmed by the existence/imposition of the PSVI?
		Next by thread: The Future of XML with and without PSVI
	www.stylusstudio.com /xmldev/200205/post40920.html (136 words)

	Re: PSVI using existing infoset items
		It sounds like the kid of thing you are suggesting.
		Previous by thread: Re: PSVI using existing infoset items
		Next by thread: Re: PSVI using existing infoset items
	www.xmlstudio.com /xmldev/200110/post20560.html (160 words)

	PSVI - Art History Online Reference and Guide
		PSVI - Art History Online Reference and Guide
		A schema assigns an identifiable type to each element Schema validation is produces in a Post Schema Validation Infoset, PSVI for short.
		Schema aware applications using schema parsers and APIs can make use of the types of elements.
	www.arthistoryclub.com /art_history/PSVI (95 words)

	xml-dev - Re: [xml-dev] Objections to / uses of PSVI? (Site not responding. Last check: 2007-10-14)
		One typesys to rule them, and in the darkness bind them.
		Prev by Date: Re: [xml-dev] Objections to / uses of PSVI?
		Previous by thread: Re: [xml-dev] Objections to / uses of PSVI?
	lists.xml.org /archives/xml-dev/200205/msg00921.html (144 words)

	Re: [xmi] Can XMI document conformance be based on PSVI? (Site not responding. Last check: 2007-10-14)
		Re: [xmi] Can XMI document conformance be based on PSVI?
		For example, maybe the conformance rules could be stated in terms >of XML Infoset and/or Post-Schema-Validation-Infoset (PSVI)?
		Since it makes absolutely no difference the the information where the namespace declaration is actually placed (or which prefix is used or if it is bound to an explicit prefix or declared by overriding the the default namespace) the resulting XMI document forms a valid document instance in terms of XML 2nd ed.
	www.dstc.edu.au /ListArchive/xmi/archive/2002/01/msg00000.html (197 words)

	Xerces, XInclude and PSVI
		If you have not registered, please click here.
		I developed an Java application which use Xerces to manipulate XML files.
		If there is somebody which can help me, thank you in advance.
	forums.devshed.com /t139832/s.html (167 words)

Try your search on: Qwika (all wikis)