text:
DRIFT: Spring Dance Concert
April 8, 2016, 7:30pm — April 9, 2016, 2:30pm and 7:30pm
The Department of Theatre Arts closes the season through movement with "DRIFT: Spring Dance Concert"—taking you on a journey through time, generations, emotions and movement. The culmination and final presentation of our dance students, the concert brings theory, studio techniques, and performance skills into one setting.
POSTER: Official poster [jpg]
FOR MEDIA: Press release [pdf]
27th James A. Porter Colloquium
"Roots and Branches: Black Arts Movements into the 21st Century"
Saturday, April 9, 2016 — 9am to 10pm
The 27th Annual James A. Porter Colloquium on African-American Art will examine the influence of the Black Arts Movements of the 1960s and 1970s on the trajectory of African-American art and celebrate the influence of the Black Arts Movement on later African-American art.
Breathing Working Committee
Strategic Approach to Ending Public Violence: Police Brutality, Mass Incarceration and Black Bodies
The committee is hosting its 2nd workshop on April 8, 2016. Committed to Breathing Project is a collaborative effort between and among community leaders and Howard faculty, staff and students to design an effective intervention that can help minimize different forms of violence in society and, particularly, in black communities.
POSTER IMAGE: Ending Public Violence
Physics Colloquium: Dr. Jed Pixley
Spin Orbit Coupling in Ultra-Cold Atomic Gases of Spin-1 Bosons
EXCERPT: Inside the Mott lobes with an odd-integer filling we derive the effective low-energy magnetic Hamiltonian. Focusing on the quasi‐one-dimensional limit we solve the strongly coupled magnetic model via its classical limit and using the density matrix renormalization group.
ABSTRACT: Physics and Astronomy Colloquium [pdf]
English receives NEH grant
Funds support Seshat Digital Humanities Initiative
The Department of English has received a $100,000 HBCU Humanities Initiative grant from the National Endowment for the Humanities to support "Seshat: A Howard University Digital Humanities Initiative," a year-long project that generates new digital humanities data in African-American literary studies.
For more information: Dr. Dana A. Williams, (202) 806-6730, firstname.lastname@example.com. Workshop applications are available online.
W. Montague Cobb Research Laboratory
Home to the most varied collections of skeletal remains and other genomic materials from peoples of African descent, the W. Montague Cobb Research Laboratory is one of the most unique biological and anthropological laboratories in the nation.
COAS faculty lead expedition
Profs Vernon Morris and Everette Joseph lead AEROSE expedition
Since 2004, COAS faculty members have lead research missions on the NOAA Aerosols and Ocean Science Expeditions (AEROSE). AEROSE has supported the research and experiential training of over fifty (50) students, with the largest fraction of students and faculty coming from Howard.
This year's research campaign embarked from Las Palmas, Canary Islands, on November 16, 2015, and involved a combined mission of three teams.
WBHR-LSAMP scholar wins at 2015 ABRCMS
Honoree's passion for research gains momentum each semester
Honoreé Brewton, a senior psychology major and Washington Baltimore Hampton Roads- Louis Stokes Alliance for Minority Participation (WBHR-LSAMP) participant recently won top honors for her poster presentation at the 2015 Annual Biomedical Research Conference for Minority Students (ABRCMS).
Brandon researches 3C-SiC growth
In particular, on a 6H-SiC wafer using Chemical Vapor Deposition
Anthony Brandon's research is funded in part by the Washington Baltimore Hampton Roads Louis Stokes Alliance for Minority Participation (WBHR-LSAMP). Students involved in this program are paired with a faculty mentor, attend and present at scientific conferences and receive a stipend for their participation.
Ta-Nehisi Coates visits the Flagship
Coates and students dialog, then—a selfie
Ta-Nehisi Coates launched the tour for his critically acclaimed book, Between the World and Me, with the College of Arts and Sciences Freshman Seminar at Howard University.
Coates spent the entire day on campus engaged in dialogue with the students.


text:
Austronic can provide custom cable services to our customers of different industries.
What type of custom Cables we can make ?
1. Custom Cables for Computer
Custom cables for computer include special length computer cables and special connectors.
For example, right angle USB, DVI and VGA Connectors.
2. Custom Cables for Point of Sales
We can make various cables for POS scanners, printers, and EFTPOS machines.
3. Custom Wire Harness
We can make different types of wire harness for industry uses.
4. Custom Ribbon cables
We can offer different colour and lengths ribbon cables.
How to get a quotation for my custom make cables ?
To be able to quote and make the exact cables you need, we will need you to provide information as detailed as possible. For example, you can send us the technical drawing, samples, pictures.
Upon receiving these information, one of our sales represenative will check the possibility of making the cable. If we can make it, he will assign a product code to this custom cable and send you the quotation including price, lead time and freight charges.

subset: commoncrawl


text:
'Star Wars: Episode V - The Empire Strikes Back' (1980)
Domestic box office: $290,475,067 | Worldwide box office: $538,375,067 | "The Empire Strikes Back" is perhaps the most critically revered film in the "Star Wars" franchise, but Irvin Kershner, the movie's director, nearly didn't take the job. "I didn't want to follow a picture like 'Star Wars,' because what could I do that was different?" Kershner said. "But George said, 'I want to make a picture that is better than the first one. Because if the second one is not successful, that kills the whole series.' ... I really knocked myself out. I was able to go deeper into the characterization. I was doing the second act of a three-act play, or the second movement of a symphony. That's always the slower movement. I could not have a grand climax, I had to leave things ambiguous. My big climax came at the beginning of the film, with the battle in the snow, then I told the story of the people."


text:
Rigid Mountain Bikes Are Better To Learn On? Another MTB Myth?
I read an article last week that claimed that rigid mountain bikes are the best bikes to learn on. I couldn't disagree a more! While I agree that it is amusing to see riders who are struggling to ride sections of trail on their $10,000 carbon full suspension bikes with carbon wheel sets that cost $2,800 I don't agree that a rigid bike some how "teaches" you to be a better rider. I bought my first mtb in 1989 and it was fully rigid and I had a blast on that bike! Unfortunately, a bike can't teach you anything and just riding a bike (without the knowledge of correct skills and drills to practice those skills) tends to get you better at your instincts (which are old, hunter gather type instincts, mtbs have not been around long enough for us to be born with mtb instincts. Read more


text:
Click the button below to add the Ancient Gold Parchment Cardstock to your wish list.
8.5" x 11".
80# Cardstock.
Very nice heavy cardstock.
We promise to never spam you, and just use your email address to identify you as a valid customer.
This product hasn't received any reviews yet. Be the first to review this product!
All prices are in USD. © 2019 Creative Images | Sitemap
Powered by BigCommerce


text:
Taylor Swift Covers 'Marie Claire UK' November 2012
Taylor Swift graces the cover of British Marie Claire's November 2012 issue, on newsstands October 4.
Here is what the 22-year-old singer had to share with the mag:
On if she warns boyfriends that they might end up in song: "Ha! Well… it's not like it's in fine print, but music is absolutely everything that I am and everything that I stand for. It's not my fault if someone gets into a relationship with me and then cheats and I write a song about it."
On her high-profile relationships being a potential problem: "I agree with everything you're saying. I think I have to trust that you end up with the person you're supposed to end up with, and that everything in between is there to teach you stuff. Plus it makes for great stories when you're older."
On having kids one day: "[My] money will be really good for sending my kids to college some day – or maybe I'll have a few more kids than I thought. I want a bunch of them running around, minimum four. I want to wait a while, but… the idea of pouring everything you are into another person when you become a parent has always been amazing to me."
For more from Taylor, visit MarieClaire.co.uk and pick up the issue this Thursday for the full interview!


text:
Puppy Linux Discussion Forum
Puppy HOME page :
"THE" alternative forum :
Log in to check your private messages
Log in
The time now is Fri 18 Jan 2019, 14:49
All times are UTC - 4
Forum index
Advanced Topics
Additional Software (PETs, n' stuff)
Truecrypt unable to open MRL
View previous topic
View next topic
Page 1 of 1
[6 Posts]
Joined: 25 Mar 2013
Posts: 57
Posted: Sat 08 Jun 2013, 13:16
Post subject:
Truecrypt unable to open MRL
This is a quirky problem I have had for months:
1) I have terabytes of video on hard disk, each in its own Truecrypt volume. I simply mount the volume I want to see and drag/drop the VIDEO_TS folder into VLC, and it throws this error:
VLC is unable to open the MRL: 'dvd:///mnt/dm-0/VIDEO_TS/'
...and yet it clearly finds it: it starts playing the DVD Folder one VOB at a time skipping everywhere...each VOB plays serially like its own file...as from a list...requiring constantly resetting subtitles, sound, etc., making the experience unusable). I formerly blamed VLC for playing poorly with Truecrypt but that just doesn't make sense the more I test:
2) I thought maybe I needed a swap file (which I am reluctant to employ) or increase my 4GB RAM, but if I simply take the decrypted volume and copy the exact same VIDEO_TS folder to hard disk (no longer involving Truecrpyt) then drag/drop it into VLC, it plays the whole "DVD" as it was meant to: perfectly. Of course, this makes the whole encryption thing nonsensical to begin with.
3) This is true whether I use Truecrypt 7.0a, 7.1, turn off kernel cryptographic services (in which case DM-0 doesn't appear but I drag the folder from /mnt/truecrypt1 with the similar error), or whatever version of VLC I use and whatever advanced menu option I attempt to use to open the folder. It also behaves the same way regardless of the hard disk the Truecrypt volume physically resides on: fixed, removable, etc.
This is the ONE THING I am relegated to using Windows for anymore
(and on the exact same machine, and also with VLC and Truecrypt). I am what you could otherwise describe as super-Fatdog-happy.
I am guessing I am clueless about some missing mapping library that makes a Truecrypt volume behave as if it were an honest-to-God hard drive volume...
Any advice about this would be most enlightening and appreciated.
Back to top
Joined: 12 Aug 2011
Posts: 823
Posted: Thu 27 Jun 2013, 14:34
Post subject:
Subject description: don't get your hopes up
this work-around may be worth a try ...
Back to top
Joined: 25 Mar 2013
Posts: 57
Posted: Fri 12 Jul 2013, 12:32
Post subject: Thanks
Subject description: I had given up on hearing from anyone
I had previously tried that script and couldn't
get it to execute/intefrace. It DOES seem like Truecrypt is
designed to interface with Nautilus which I thought
might be the problem with it finding paths in ROX in a flawed fashion.
Fatdog quite nicely creates an "DM-X" icon when a Truecrypt
volume is mounted so opening it as in Windows was never necessary.
But in revisiting your comments in that thread it would seem
like there might be something truncating names INSIDE my VIDEO_TS
folder. I will have to check the paths from the command line
and even try your idea of creating the same volume under
Windows and also Puppy, and alternatively open both.
Hopefully this will occur before I am to elderly to type.
Back to top
Joined: 25 Mar 2013
Posts: 57
Posted: Mon 09 Sep 2013, 22:08
Post subject: Finally did some testing
Very carefully controlled the same files on the same disk (external USB hard drive) which play great under Win7/Truecrypt/VLC, but choke under Fatdog621/Truecrypt/VLC. However, the same folders not under Truecrypt on the same drive work identically in both systems (same machine). Making the DVD folders on either platform is moot as it turns out. Invoking VLC from the command line in Fatdog gives lots of errors, the most telling of which is it can't read the initial block of the decrypted/mounted device and guesses it isn't a DVD at all (which it isn't...it is folder on a hard drive...but Win7 figures that out). The error is thrown by VLC's call using libdvdcss. I tried a series of tests using both Truecrypt and cryptsetup to open/mount the archive, unmount it manually, then try to mount it as a psuedo DVD file system, but so far libdvdcss still chokes on it. Perhaps someone with familiarity with the code can give me a workaround? For instance, it appears to be probing in /root for mapping files it says don't exist but might give it more mapping intelligence?
Back to top
Joined: 25 Mar 2013
Posts: 57
Posted: Wed 11 Sep 2013, 16:57
Post subject: Here are some lines from vlc opened on the command line:
libdvdread: Using libdvdcss version 1.2.11 for DVD access
libdvdread: Attempting to use device /dev/mapper/truecrypt1 mounted on /mnt/truecrypt1 for CSS authentication
libdvdnav: Can't read name block. Probably not a DVD-ROM device.
libdvdnav: Unable to find map file '/root/.dvdnav/.map'
libdvdnav:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdnav:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.
libdvdnav: vm: failed to read VIDEO_TS.IFO
libdvdread attempts to open the block device (at the mountpoint?) "for CSS authentication" then everything acts like the path is mythical. After that VLC finds a way to open each VOB one at a time. So it seems the path is correct.
That message is the fork compared to playing the same folder extracted/unencrypted. In other words there is no similar statement "Attempting to use device /dev/mapper/truecrypt1 mounted on /mnt/truecrypt1 for CSS authentication" when the path doesn't involve dm-mapper?
Back to top
Joined: 25 Mar 2013
Posts: 57
Posted: Mon 02 Dec 2013, 12:03
Post subject: Update
Just a word about what I have been doing to resolve this:
1) Upgraded to Fatdog 630
2) Tested this against other Linux Ubuntu distributions
3) Ran the test inside pure upgraded DM-Crypt
4) Gone to the the VLC forums and asked advice and tried
all from command line to each menu option.
Dragging a VIDEO_TS folder from an encrypted archive
into VLC loses the path in every case in every Linux distribution (tested). Still works with all files
and hardware identical (in Windows (7)).
Back to top
Display posts from previous:
All Posts
1 Day
7 Days
2 Weeks
1 Month
3 Months
6 Months
1 Year
Sort by:
Post Time
Post Subject
Page 1 of 1
[6 Posts]
View previous topic
View next topic
Forum index
Advanced Topics
Additional Software (PETs, n' stuff)
Jump to:
Select a forum
Forum index
|___ House Training
| |___ Beginners Help ( Start Here)
| |___ Users ( For the regulars )
| | |___ Usuarios de habla Hispana
| | |___ Für deutschsprachige Anhänger
| | |___ Pour les francophones
| |
| |___ HOWTO ( Solutions )
| |___ Bugs ( Submit bugs )
|___ Advanced Topics
| |___ Additional Software (PETs, n' stuff)
| | |___ Package Collections / Repositories
| | |___ Browsers and Internet
| | |___ Business
| | |___ Compiling
| | |___ Desktop
| | |___ Documents
| | |___ Drivers
| | |___ Educational
| | |___ Engineering/Science/Simulation
| | |___ Eye Candy
| | |___ Filesystem
| | |___ Games
| | |___ Graphics
| | |___ Multimedia
| | |___ Network
| | |___ Security/Privacy
| | |___ System
| | |___ Utilities
| | |___ Virtualization
| | |___ Unsorted
| |
| |___ Cutting edge
| | |___ Multi-session live-CD/DVD
| |
| |___ Hardware
| | |___ Audio
| | |___ Networking
| | | |___ Dialup
| | | |___ Ethernet
| | | |___ Wireless
| | |
| | |___ Printers
| | |___ Video
| |
| |___ Puppy Derivatives
| |___ Puppy Projects
| |___ Next Puppy Development
| | |___ 4.x
| | | |___ Bugs (4.x dev)
| | | |___ Usability Issues (4.x dev)
| | |
| | |___ 5.x
| | |___ Bugs (5.x dev)
| | |___ Usability Issues (5.x dev)
| |
| |___ Localization Project
| |___ Documentation Project
|___ Taking the Puppy out for a walk
| |___ Announcements
| |___ Puppy Power
| |___ Suggestions
| |___ Misc
|___ Off-Topic Area
|___ Programming
|___ Security
post new topics in this forum
reply to topics in this forum
edit your posts in this forum
delete your posts in this forum
vote in polls in this forum
attach files in this forum
download files in this forum
Powered by
© 2001, 2005 phpBB Group
[ Time: 0.0396s ][ Queries: 12 (0.0099s) ][ GZIP on ]


text:
Our website uses cookies. By continuing we assume your permission to deploy cookies, as detailed in our Terms & Conditions.
Our wedding hair accessories collection includes tiaras, hair combs, headpieces, headband,& side tiaras as well as hairvines,ribbon garlands and hairpins. So we have put together a little video of how best to wear them.


text:
As details of alleged cop killer Jeremy Goulet's past continue to emerge Thursday, the picture continued to grow darker.
In 2006, the former Blackhawk helicopter pilot beat charges that could have landed him in a military prison for life, with a former defense attorney saying the Army dropped two separate rape charges against Goulet in Hawaii. And Santa Cruz County officials said Thursday they were investigating a previously unknown molestation case against the 35-year-old former barista, adding to a growing list of past sex and violence charges.
"These officers possessed limited information about Goulet. They were investigating a misdemeanor case. They had no information that led them to believe that they were in danger or that Goulet, at that time, was a danger to them," Santa Cruz County Sheriff Phil Wowak said Thursday.
First reported by the Honolulu Star-Advertiser, the new revelations add to Goulet's history of peeping activity, with misdemeanor convictions in San Diego, Portland, Ore. and Berkeley.
Friday, Goulet allegedly broke into the home of a co-worker after a night of drinking an in apparent sex assault attempt, an incident that set in motion Tuesday's shooting deaths of two Santa Cruz police detectives.
That allegation — which occurred after a night of after-work drinks, sources familiar with the incident say — mirrors the facts behind a rape charge brought against Goulet while he served in the military. Army officials later agreed to drop all charges under a plea deal, and did not immediately respond to a request seeking comment.
Former Goulet defense attorney Don Wilkerson in Hawaii said the first charges stemmed from an incident just days after being stationed at Wheeler Army Airfield, Honolulu.
A group of soldiers threw a party, which was attended by a young female officer who lived off base. After going home, locking her doors and going to bed, Goulet allegedly attacked her.
"The first one happened within one week of his arrival here," Wilkerson said. "Mr. Goulet was accused of crawling in through her bathroom window and raping her."
Rather than lock up Goulet, military brass grounded him and ordered him not to leave the base. He was assigned to watch over barracks.
Several months later, a group of military personnel in one of Goulet's barracks threw a party the night before deploying to Iraq. After that party, Goulet allegedly raped a second female officer.
After the second allegation, the military locked up Goulet in Naval Brig Ford Island in the middle of Pearl Harbor, Wilkerson said. Goulet stayed there for several months.
Lack of consent was not an issue in either case, Wilkerson said. However, there were identification issues in the first and credibility issues in the second.
Wilkerson negotiated a plea deal that saw the Army drop the case in exchange for a less-than-honorable discharge.
Military records confirm Goulet was assigned to Hawaii in April 2006. He was discharged in early 2007, and immediately embarked for Portland, Ore., records show.
Later that year, Goulet was arrested over a peeping incident and subsequent brawl, during which a gun was discharged. Beaten badly by the victim's boyfriend — as well as the victim herself, who wielded a shelf — a jury acquitted Goulet of four felonies, finding him guilty of two misdemeanors.
Portland investigators found evidence that Goulet secretly taped another victim as well. He admitted on the stand to video recording women. People close to the case, who did not want to be identified, said the jury did not see what everyone else connected to the case did — that's something was wrong with Goulet.
Though given probation on the misdemeanors and not required to register as a sex offender, Judge Eric Bloch ordered Goulet to undergo treatment and submit to polygraph tests and searches of his computers and cellphones. But Goulet rejected treatment and fought with his female probation officer, even refusing to leave the premises and peering into her office windows after one meeting was cut short.
Rather than comply with the terms of probation, Goulet chose jail instead. Bloch took the highly unusual step of giving him maximum misdemeanor penalties, and strung them back-to-back.
Bloch also refused to reduce the sentence, which is standard in many Oregon cases. Goulet served two years in jail.
"I felt it was my duty to impose the maximum penalty within my power because I was very concerned that he was a risk to the community," Bloch told the Oregonian newspaper this week. "He thought his behavior was normal, and I was very clear to him that I thought his behavior was not normal and not appropriate."
Follow Sentinel reporter Jason Hoppin on Twitter at Twitter.com/scnewsdude


text:
Dina Bar-el is well known throughout the fashion world for her elegant gowns that are picture perfect for any red carpet event. But trust me, you don't have to be Beyonce Knowles, Katherine McPhee or Penelope Cruz to look like a million bucks in a Bar-El original. The three c's of a great dress – cut, color and contour – have had its standards set by the chic and ever so glamorous designer.
Since her humble beginnings in 1974 until now, the evolution of her design sense has continued to surge and spawn out creations that are sought after season after season. For her Spring 2008 collection, Bar-el didn't pull out the stops when it came to sparkle, vibrant color and flowing silks and chiffons. This collection takes us from cocktail parties to wedding parties in a matter of minutes and celebs such as Ali Landry and Adrienne Frantz were there to witness the transformation.
Elements of appeal for the collection happened to be the use of two tone colors throughout the line. Deep purples paired with pale pinks and glitzy gold's trimmed with iridescent ivory made the dresses pop off the runway. Another favorite happened to be brightly colored "lipstick" sheaths with delicate detailing and blouson style tops. With all the play in color, there was yet room for a few sophisticated looks in black and white or mixture of the two.
Another look that is sure to make headway for the spring is metallic. Bar-el stamped her imprint on short and tight metallic gold and silver mini dresses with contoured bodices. Slide into one of these dresses and you will definitely be a showstopper. But, from my perspective, the metallic minis were trumped by similar styled dress in bold print patterns. There is something about an eccentric pattern that makes my blood boil with excitement. Bar-el created an art canvas on many of her designs all with the use of color splashes or bleeds and blends of one color into the next. A little bling mixed in took the collection to the next level.
On the other side of the spectrum, if you dare not to be a showstopper in a mini dress, but rather be the belle of your own ball or shall I say wedding, then grace yourself in one of the long flowing dresses in satin and chiffon. I could picture many of the looks as the backdrop to a stellar wedding party. And speaking of weddings, Bar-el closed her show with a jewel accentuated silk wedding gown in a light silver hue. It was stunning!
My sister Gwendolyn Carlson and I had the pleasure of sitting next to Dina Bar-el's esthetician Kathleen Boniface who rushed to the show from her skin care facility, Boniface Skin Care in Beverly Hills, CA. An avid fan of Bar-El, Boniface was exhilarated by the show and designs. "Dina always knows what looks great on the female figure…her designs are so glamorous," states Boniface. And I couldn't agree with her more.
If you would like to experience what it means to wear a Dina Bar-el original, check out her website at www.dinabarel.com. Trust me, you will be glad you did!


text:
Save Editor v4.3
The Save Editor is an external software. So you can change the following settings:
Money, debt, gold coins, wheat, barley, canola, grain corn, chaff, hay, grass, potatoes stock, sugar camp, wood chips, Fields, chicken stock, sheep population, number of cows, manure Stand, dunghill, milk, eggs, silage, game speed (even beyond 120x ), tap Remove, fill up all the vehicles, clean, reset, multiplayer settings
In addition, there the Save Editor information about:
Played days, compacted bales, weather, future demands, evaluation, Hofwert and the total value (animals, vehicles, items, storage content), place in the ranking ...
Step 1: Right click on the zip file and click "Extract".
Step 2: Double-click on the exe file.
Prerequisite: The DLL file (s) and the EXE must be in the same directory, but not in a zip folder.
Frequently asked questions are answered in this video:
2015-07-24 23:22
2015-07-24 23:22
2015-07-24 23:23
greatjack (Programmierer)
DerFabsi (Bereitsteller der Fahrzeugdaten in einer Excel-Tabelle)


text:
New boutique: America's Cup Team Store
Right now, the official America's Cup souvenir shop in San Francisco stands alone in a white tent bordered by construction fences at Pier 27, on the Embarcadero at Battery Street. By next summer, however, it will be cheek-to-jowl with the America's Cup Village, now under construction, that will serve as a hub for concerts, big-screen TVs, wine bars and other public activities; a media center; a headquarters for race authorities; and a cruise terminal.
The shop opened Aug. 26 and contains a variety of clothing, gifts and accessories, most notably jackets bearing the names and sponsors of competing teams from New Zealand, Great Britain, Sweden, Korea and France, but not, unfortunately, from China, Italy (made by Prada, and the most sought-after), or Oracle Team USA (made by Puma and currently sold only on the America's Cup website.)
There are long-sleeve, casual button-down shirts from Emirates New Zealand ($54), high-performance waterproof squall jackets from France's Team Energy ($200) and Henry Lloyd parkas from Britain's Ben Ainslie team ($135), to name a few. Also offered are women's V-neck T-shirts ($30) and zip-up polyester sports jackets ($90), coffee mugs ($10), shot glasses ($8.50), umbrellas ($30), scrunched knit caps (for that Mission District hipster look, $22) and artwork. Framed prints, posters and oil paintings with the San Francisco skyline and America's Cup vessels range from $20 to $7,000.
Sailing gets a knock for being a rich man's sport, but at the America's Cup store, there's something for just about every price range. "We're trying to be as accessible as possible," said James Whitburn, licensing manager for the America's Cup Event Authority. "More inclusive than exclusive."
Pier 27, Embarcadero at Battery Street; S.F.; 10 a.m.-6 pm., Mon.-Sun. www.americascup.com.


text:
Disk Configurationsillucine Jul 17, 2011 1:56 PM
I'm building a new system and have some questions about what sort of disk configuration to put together. Probably about 90% of my source will be AVCHD (more details in my earlier post). The articles on this forum are great and have been very helpful but I'm still confused. The Generic Guideline for Disk Setup talks about distributing access across as many disks as possible but then shows all configurations with more than 4 disks as placing everything except the OS, programs, and pagefile on the same RAID. A file is distributed across multiple disks in a RAID but it's one logical drive so there must be head contention if more than one file is needed at the same time from that RAID. Wouldn't a setup like this work better?
C: [1 Drive] OS, Programs
D: [RAID 3] Media, Projects
E: [RAID 0] Pagefile, Media Cache
F: [1 Drive] Previews, Exports
Would there be any problems having multiple RAIDs? In the above example, the RAID 3 would require a hardware controller and the RAID 0 could run off the ICH10R on the motherboard. Can ICH10R support multiple RAIDS (more than one RAID 0) and can a hardware controller (say, an Areca) support more than one RAID? If so, would it be better to run both the RAID 3 and RAID 0 in this example off the Areca?
To RAID or not to RAID has been helpful but I'm still not clear on everything. What are the differences between an inexpensive controller like the Areca ARC-1210 and the more expensive models which can cost 4 times as much? Obviously the more expensive controllers have faster processors and more cache but do you get 4 times the performance? I'm sure a high-end controller would be helpful if you're editing 4K files or uncompressed HD but I suspect it's not worth the expense for a mostly-AVCHD environment.
What about using RAID 0 for source media? I understand the likelihood of problems increases with the number of disks but what does that mean in the real world? I've been using my current drives (Seagate SCSIs) for about 7 years and have never had a problem. In fact I've owned computers with hard drives since the early 80s and don't believe I've ever had a disk fail on me. Of course everything needs to be backed up but how often might I be rebuilding a RAID 0 due to disk failure? Maybe I've been very lucky or maybe "they don't build 'em like they used to".
I've been using (parallel)SCSI for over 10 years but no longer believe it's cost effective. It seems like adding more SATA drives to a RAID would be cheaper than expensive 15K RPM SAS drives. Does everyone agree with that? Also, SAS drives are only available in much smaller capacities than SATA drives.
A hardware controller is required for RAID 3 and strongly recommended for RAID 5 but do they offer an advantage for RAID 0? What about for RAID 10? One advantage would be providing extra ports since most motherboards only provide 6 SATA ports. Does one motherboard offer any better SATA and RAID performance than any other or are they all about the same in that regard?
Is there any advantage to external RAIDS other than convenience in moving data from one computer to another? It seems like a controller directly on the bus would be faster than one connected externally.
Is there any disadvantage to running SATA 3 drives on a SATA 2 controller? A possible advantage might be the larger cache that some SATA 3 drives have. Would a 64MB cache help much over a 32MB cache? I've also heard SATA 3 can increase burst speeds. If I have two SATA 3 ports, and I'm using one on an SSD for the OS, would it help to use the other port for another drive or might that take away bandwidth from the SSD?
I've run across some things (don't have links handy) that indicate there may be problems with drives larger than 2 TB. Is this just for single drives larger than 2 TB, RAIDs larger than 2 TB, or am I confused and this is not an an issue?
What about specific drives that are quiet and perform well? Quietness is important to me and I worry about building a box, with as many as 10 drives, sounding like an airport runway. I've heard the Caviar Blues are quieter than the Black but I don't think they perform as well. I've heard Samsung F3 are both quiet and fast and that's what I'm leaning towards at the moment. What's with the F4? Samsung's site says it's "Independently tested as the fastest 3.5" HDD available" yet it also refers to it as an "Eco-Green HDD", which usually means slow.
Should I use different drives in RAIDs than standalone? I've heard "enterprise" models are better for RAIDs because of differences in their firmware error recovery. These sources say "consumer" models are more likely to time-out in a RAID because they have more aggressive error recovery. Is this true and should be a concern?


text:
carlgo wrote:How many times have we heard about how Slow Joe Blow, career 2.4/game scorer just scored his 28th point? Or that nobody rotated over to guard Dead Eye Jones who makes 8 million a year for shooting 3-pointers?
Exactly. As an example, how many good games has Ronny Turiaf played in the NBA?. One. Guess which one?
carlgo wrote:Also, there is a lack of respect by the officials which comes from their own perceptions of how well the defense is playing. A team that is constantly being called for tickytack fouls is going to back off some or substitute in even worse defensive players.
That's true. The way the refs call the fouls can really hurt a defense... and they sure don't look at us kindly. I mean, look at fouls called against Detroit and against us in any given game.


text:
- Document title:
- RIF Core (Second Edition)
- Editors
- Harold Boley, National Research Council Canada
- Gary Hallmark, Oracle Corporation
- Michael Kifer, State University of New York at Stony Brook, USA
- Adrian Paschke, Free University Berlin
- Axel Polleres, DERI
- Dave Reynolds, Hewlett-Packard Laboratories, Bristol UK
- Abstract
This document, developed by the Rule Interchange Format (RIF) Working Group, specifies RIF-Core, a common subset of RIF-BLD and RIF-PRD based on RIF-DTB 1.0. The RIF-Core presentation syntax and semantics are specified as restrictions on RIF-BLD. The XML serialization syntax of RIF-Core is specified via a mapping from the presentation syntax. A normative XML schema is also provided.
- Status of this Document
- @@initial draft.
Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
- 1 Overview
- 2 RIF-Core Presentation Syntax
- 3 RIF-Core Semantics
- 4 XML Serialization Syntax for RIF-Core
- 5 Conformance and Safety
- 6 RIF-Core as a Specialization of RIF-PRD
- 7 Acknowledgements
- 8 References
- 9 Appendix: XML Schema for RIF-Core
1 Overview
This specification develops RIF-Core (the Core of the Rule Interchange Format). From a theoretical perspective, RIF-Core corresponds to the language of definite Horn rules without function symbols ('Datalog') and a standard first-order semantics. RIF-Core thus is a subset of RIF-BLD [RIF-BLD]. At the same time, RIF-Core is a language of production rules permitting only assert actions. RIF-Core thus also is a subset of RIF-PRD [RIF-PRD]. Moreover, RIF-Core is based on the built-ins of RIF-DTB 1.0 [RIF-DTB]. The common subset of RIF-BLD and RIF-PRD is specified based on RIF-DTB 1.0.
Syntactically, RIF-Core has a number of Datalog extensions to support features such as objects and frames as in F-logic [KLW95], internationalized resource identifiers (or IRIs, defined by [RFC-3987]) as identifiers for concepts, and XML Schema datatypes [XML-SCHEMA2]. In addition, RIF RDF and OWL Compatibility [RIF-RDF+OWL] defines the syntax and semantics of integrated RIF-Core/RDF and RIF-Core/OWL languages. These features make RIF-Core a Web-aware language. However, it should be kept in mind that RIF is designed to enable interoperability among rule languages in general, and its uses are not limited to the Web.
RIF-Core is defined as a specialization of RIF-BLD (hence of [RIF-FLD] which is part of the RIF extensibility framework). It is a syntactic subset of RIF-BLD, so that a well-formed RIF-Core formula (including documents and condition formula) is also a well-formed RIF-BLD formula. The semantics of RIF-Core is defined to be identical to that of RIF-BLD.
RIF-Core is also a syntactic subset of RIF-PRD. It is intended that a RIF-PRD consumer can treat a RIF-Core ruleset as if it were a RIF-PRD rule set and it would conform to the normative RIF-Core first order semantics. However, due to the presence of builtin functions and predicates there are RIF-Core rulesets which are unsafe and do not reach a stable fixed-point under RIF-PRD semantics. We define the conformance to RIF-Core so as to only require conformance over a safe subset of rules, in this way we permit RIF-PRD processors to be minimally conformant while allowing RIF-Core documents to contain unsafe rules. Producers of RIF-Core who require maximum interchange are advised to restrict themselves to safe rules. These notions of safeness and strict conformance are defined formally in section 5 Conformance and Safety.
To give a preview, here is a simple complete RIF-Core example deriving a ternary relation from its inverse.
Example 1 (An introductory RIF-Core example).
A rule can be written in English to derive the buy relationships (rather than store them) from the sell relationships that are stored as facts (e.g., as exemplified by the English statement below):
- A buyer buys an item from a seller if the seller sells the item to the buyer.
- John sells LeRif to Mary.
The fact Mary buys LeRif from John can be logically derived by a modus ponens argument. Assuming Web IRIs for the predicates buy and sell, as well as for the individuals John, Mary, and LeRif, the above English text can be represented in RIF-Core Presentation Syntax as follows.
Document( Prefix(cpt http://example.com/concepts#) Prefix(ppl http://example.com/people#) Prefix(bks http://example.com/books#) Group ( Forall ?Buyer ?Item ?Seller ( cpt:buy(?Buyer ?Item ?Seller) :- cpt:sell(?Seller ?Item ?Buyer) ) cpt:sell(ppl:John bks:LeRif ppl:Mary) ) )
For the interchange of such rule (and fact) documents, an equivalent RIF-Core XML Syntax is given in this specification. To formalize their meaning, a RIF-Core Semantics is specified.
2 RIF-Core Presentation Syntax
RIF-BLD [RIF-BLD] specifies a presentation syntax and an XML syntax. The presentation syntax is normative, but is not intended to be a concrete syntax. Since RIF is an interchange format, it uses XML as its concrete syntax.
RIF-Core is a syntactic subset of RIF-BLD and in this section we define a corresponding presentation syntax for RIF-Core, we do this as a restriction on the RIF-BLD syntax and so this specification depends upon that of RIF-BLD.
2.1 Alphabet of RIF-Core
The alphabet of the presentation language of RIF-Core is the alphabet of the RIF-BLD presentation language with the exclusion of the symbol ## and the set of symbols ArgNames.
That is it consists of:
- a countably infinite set of constant symbols Const
- a countably infinite set of variable symbols Var (disjoint from Const)
- connective symbols And, Or, and :-
- quantifiers Exists and Forall
- the symbols =, #, ->, External, Import, Prefix, and Base
- the symbols Group and Document
- the auxiliary symbols (, ), [, ], <, >, and ^^
Where the sets Const and Var are disjoint from each other and from all other symbols listed above.
2.2 Terms of RIF-Core
The Terms of RIF-Core are the terms of RIF-BLD with the exclusion of terms with named arguments and Subclass terms.
That is RIF-Core terms are one of:
- Simple terms: constants and variables.
- Positional terms: t(t1 ... tn)
- Equality terms: t = s
- Class membership terms - t#s
- Frame terms: t[p1->v1 ... pn->vn], or
- Externally defined terms: External(pt) where pt is a positional term.
Editor's Note: This presumes that the At Risk #1 feature External frames is dropped from RIF-BLD, if that is not the case the above will need updating.
A base term is a simple, positional or externally defined term, each of the t, p, v and s above are base terms.
2.3 Formulas of RIF-Core
The Formulas of the RIF-Core are the formulas of RIF-BLD with the following modifications.
- Atomic formula: any RIF-Core term, including base terms, equality terms, class membership terms and frame terms.
- Restricted atomic formula: a RIF-Core simple, positional or frame term (i.e. excluding equality, class membership and externally defined terms).
- Conditional formula: either an atomic formula, a conjunction, disjunction or existential over RIF-Core conditional formula.
- Rule implication: φ :- ψ is a formula, called rule implication, if:
- φ is an restricted atomic formula,
- ψ is a condition formula, and
- none of the atomic formulas in φ is an externally defined term (i.e., a term of the form External(...)). (Note: external terms can occur in the arguments of atomic formulas in the rule conclusion.)
- Universal rule: as RIF-BLD restricted to RIF-Core rule implications. If φ is a RIF-Core rule implication and ?V1, ..., ?Vn, n>0, are variables then Forall ?V1 ... ?Vn(φ) is a RIF-Core universal rule formula also referred to as a RIF-Core Rule. It is required that all the free variables in φ occur among the variables ?V1 ... ?Vn in the quantification part.
- Universal fact: as RIF-BLD restricted to RIF-Core restricted atomic formula. If φ is a RIF-Core atomic formula then Forall ?V1 ... ?Vn(φ) is a formula, called a universal fact, provided that all the free variables in φ occur among the variables ?V1 ... ?Vn.
- Group: If φ1, ..., φn are RIF-Core rules, universal facts, variable-free rule implications, variable-free atomic formulas, or group formulas then Group(φ1 ... φn) is a RIF-Core group formula.
- Document: An expression of the form Document(directive1 ... directiven Γ) is a RIF-Core document formula, if Γ is an optional RIF-Core group formula and directive1, ..., directiven is an optional sequence of directives as defined in RIF-BLD.
2.4 Annotations and documents
RIF-Core allows every term and formula to be optionally annotated in the same way as RIF-BLD. Every term and formula (including terms and formulas that occur inside other terms and formulas) may be optionally preceded by an annotation of the form (* id φ *), where id is a rif:iri constant and φ is a frame formula or a conjunction of frame formulas.
RIF-Core document formulas with and without annotations will be referred to as RIF-Core documents.
2.5 Well-formed formulas
Definition (Well-formed formula). A RIF-Core formula φ is well-formed iff it is a well-formed RIF-BLD formula. That is iff:
- every constant symbol (whether coming from the symbol space rif:local or not) mentioned in φ occurs in exactly one context.
- if φ is a RIF-Core document formula and Δ'1, ..., Δ'k are all of its imported RIF-Core documents, then every non-rif:local constant symbol mentioned in φ or any of the imported Δ'is must occur in exactly one context (in all of the Δ'is).
- Whenever a formula contains a term or a subformula of the form External(t), t must be an instance of the coherent set of external schemas (Section Schemas for Externally Defined Terms of [RIF-DTB]) associated with the language of RIF-Core.
- If t is an instance of the coherent set of external schemas associated with the language then t can occur only as External(t), i.e., as an external term or atomic formula.
Where the definition of context is given in [RIF-BLD].
Definition (Language of RIF-Core). The language of RIF-Core consists of the set of all well-formed RIF-Core formulas and is determined by:
- the alphabet of the language and
- a set of coherent external schemas, which determine the available built-ins and other externally defined predicates and functions.
2.6 EBNF Grammar for the Presentation Syntax of RIF-Core (Informative)
Until now, we have used mathematical English to specify the syntax of RIF-Core. Tool developers, however, may prefer EBNF notation, which provides a more succinct overview of the syntax. However, note that EBNF is unable to express all of the above well-formedness conditions, in particular the requirement that each symbol appear in only one context. For this reason this section is not Normative.
The EBNF for the RIF-BLD presentation syntax is given as follows, showing the entire (top-down) context of its three parts for rules, conditions, and annotations.
Rule Language:
Document ::= IRIMETA? 'Document' '(' Base? Prefix* Import* Group? ')' Base ::= 'Base' '(' IRI ')' Prefix ::= 'Prefix' '(' Name IRI ')' Import ::= IRIMETA? 'Import' '(' IRICONST PROFILE? ')' Group ::= IRIMETA? 'Group' '(' (RULE | Group)* ')' RULE ::= (IRIMETA? 'Forall' Var+ '(' CLAUSE ')') | CLAUSE CLAUSE ::= Implies | ATOMIC Implies ::= IRIMETA? ATOMIC ':-' FORMULA PROFILE ::= TERM
Condition Language:
FORMULA ::= IRIMETA? 'And' '(' FORMULA* ')' | IRIMETA? 'Or' '(' FORMULA* ')' | IRIMETA? 'Exists' Var+ '(' FORMULA ')' | ATOMIC | IRIMETA? Equal | IRIMETA? Member | IRIMETA? 'External' '(' Atom | Frame ')' ATOMIC ::= IRIMETA? (Atom | Frame) Atom ::= UNITERM UNITERM ::= Const '(' (TERM* ')' Equal ::= TERM '=' TERM Member ::= TERM '#' TERM Frame ::= TERM '[' (TERM '->' TERM)* ']' TERM ::= IRIMETA? (Const | Var ) Const ::= '"' UNICODESTRING '"^^' SYMSPACE | CONSTSHORT Name ::= UNICODESTRING Var ::= '?' UNICODESTRING SYMSPACE ::= ANGLEBRACKIRI | CURIE
IRIMETA ::= '(*' IRICONST? (Frame | 'And' '(' Frame* ')')? '*)'
The following subsections explain and exemplify these parts, starting with the basic language of positive conditions.
2.6.1 EBNF for the Condition Language
The Condition Language represents formulas that can be used in the premises of RIF-Core rules (also called rule bodies). The EBNF grammar for a superset of the RIF-Core condition language is as follows.
FORMULA ::= IRIMETA? 'And' '(' FORMULA* ')' | IRIMETA? 'Or' '(' FORMULA* ')' | IRIMETA? 'Exists' Var+ '(' FORMULA ')' | ATOMIC | IRIMETA? Equal | IRIMETA? Member | IRIMETA? 'External' '(' Atom | Frame ')' ATOMIC ::= IRIMETA? (Atom | Frame) Atom ::= UNITERM UNITERM ::= Const '(' (TERM* ')' Equal ::= TERM '=' TERM Member ::= TERM '#' TERM Frame ::= TERM '[' (TERM '->' TERM)* ']' TERM ::= IRIMETA? (Const | Var ) Const ::= '"' UNICODESTRING '"^^' SYMSPACE | CONSTSHORT Name ::= UNICODESTRING Var ::= '?' UNICODESTRING SYMSPACE ::= ANGLEBRACKIRI | CURIE
The production rule for the non-terminal FORMULA represents RIF condition formulas (defined earlier). The connectives And and Or define conjunctions and disjunctions of conditions, respectively. ATOMIC terms represent those terms that can be used in the conclusion part of a rule, whereas FORMULA also include Equal, Member and External terms. A TERM can be a constant or variable.
The RIF-Core presentation syntax does not commit to any particular vocabulary and permits arbitrary Unicode strings in constant symbols and variables. Constant symbols can have this form: "UNICODESTRING"^^SYMSPACE, where SYMSPACE is a ANGLEBRACKIRI or CURIE that represents the identifier of the symbol space of the constant, and UNICODESTRING is a Unicode string from the lexical space of that symbol space. ANGLEBRACKIRI and CURIE are defined in Section Shortcuts for Constants in RIF's Presentation Syntax of [RIF-DTB]. Constant symbols can also have several shortcut forms, which are represented by the non-terminal CONSTSHORT. These shortcuts are also defined in the same section of [RIF-DTB]. One of them is the CURIE shortcut, which is extensively used in the examples in this document. Names are Unicode character sequences. Variables are composed of UNICODESTRING symbols prefixed with a ?-sign.
A frame term is a term composed of an object Id and a collection of attribute-value pairs. An External(Atom) is a call to an externally defined predicate; External(Frame) is a call to an externally defined frame.
As noted in Section 2.4, RIF-Core formulas and terms can be prefixed with optional annotations, IRIMETA, for identification and metadata. IRIMETA is represented using (*...*)-brackets that contain an optional IRI constant, IRICONST, as identifier followed by an optional Frame or conjunction of Frames as metadata. An IRICONST is the special case of a Const with the symbol space rif:iri, again permitting the shortcut forms defined in [RIF-DTB]. One such specialization is '"' IRI '"^^' 'rif:iri' from the Const production, where IRI is a sequence of Unicode characters that forms an internationalized resource identifier as defined by [RFC-3987].
Example 2 (RIF-Core conditions).
This example shows conditions that are composed of atoms, expressions and frames. In frame formulas variables are shown in the positions of object Ids, object properties, and property values. For brevity, we use the CURIE shortcut notation prefix:suffix for constant symbols, which is understood as a macro that expands into an IRI obtained by concatenation of the prefix definition and suffix. Thus, if bks is a prefix that expands into http://example.com/books# then bks:LeRif is an abbreviation for "http://example.com/books#LeRif"^^rif:iri. This and other shortcuts are defined in [RIF-DTB]. Assume that the following prefix directives appear in the preamble to the document:
Prefix(bks http://example.com/books#) Prefix(auth http://example.com/authors#) Prefix(cpt http://example.com/concepts#)
Positional terms: cpt:book(auth:rifwg bks:LeRif) Exists ?X (cpt:book(?X bks:LeRif)) Frames: bks:wd1[cpt:author->auth:rifwg cpt:title->bks:LeRif] Exists ?X (bks:wd2[cpt:author->?X cpt:title->bks:LeRif]) Exists ?X (And (bks:wd2#cpt:book bks:wd2[cpt:author->?X cpt:title->bks:LeRif])) Exists ?I ?X (?I[cpt:author->?X cpt:title->bks:LeRif]) Exists ?I ?X (And (?I#cpt:book ?I[cpt:author->?X cpt:title->bks:LeRif])) Exists ?S (bks:wd2[cpt:author->auth:rifwg ?S->bks:LeRif]) Exists ?X ?S (bks:wd2[cpt:author->?X ?S->bks:LeRif]) Exists ?I ?X ?S (And (?I#cpt:book ?I[author->?X ?S->bks:LeRif]))
2.6.2 EBNF for the Rule Language
The presentation syntax for RIF-Core rules extends the syntax in Section EBNF for RIF-Core Condition Language with the following productions.
Document ::= IRIMETA? 'Document' '(' Base? Prefix* Import* Group? ')' Base ::= 'Base' '(' IRI ')' Prefix ::= 'Prefix' '(' Name IRI ')' Import ::= IRIMETA? 'Import' '(' IRICONST PROFILE? ')' Group ::= IRIMETA? 'Group' '(' (RULE | Group)* ')' RULE ::= (IRIMETA? 'Forall' Var+ '(' CLAUSE ')') | CLAUSE CLAUSE ::= Implies | ATOMIC Implies ::= IRIMETA? ATOMIC ':-' FORMULA PROFILE ::= TERM
Recall that an IRI has the form of an internationalized resource identifier as defined by [RFC-3987].
A RIF-Core Document consists of an optional Base, followed by any number of Prefixes, followed by any number of Imports, followed by an optional Group. Base and Prefix serve as shortcut mechanisms for IRIs. An Import indicates the location of a document to be imported and an optional profile. A RIF-Core Group is a collection of any number of RULE elements along with any number of nested Groups.
Rules are generated using CLAUSE elements. The RULE production has two alternatives:
- In the first, a CLAUSE is in the scope of the Forall quantifier. In that case, all variables mentioned in CLAUSE are required to also appear among the variables in the Var+ sequence.
- In the second alternative, CLAUSE appears on its own. In that case, CLAUSE cannot have variables.
Frame, Var, ATOMIC, and FORMULA were defined as part of the syntax for positive conditions in Section EBNF for RIF-Core Condition Language. In the CLAUSE production, an ATOMIC is what is usually called a fact. An Implies rule can have an ATOMIC elements as its conclusion; it has a FORMULA as its premise. Note that, by a definition in Section Formulas, formulas that query externally defined atoms (i.e., formulas of the form External(Atom(...))) are not allowed in the conclusion part of a rule (ATOMIC does not expand to External).
Example 3 (RIF-Core rules).
This example shows a business rule borrowed from the document RIF Use Cases and Requirements:
- If an item is perishable and it is delivered to John more than 10 days after the scheduled delivery date then the item will be rejected by him.
As before, for better readability we use the compact URI notation defined in [RIF-DTB], Section Constants and Symbol Spaces. Again, prefix directives are assumed in the preamble to the document. Then, two versions of the main part of the document are given.
Prefix(ppl http://example.com/people#) Prefix(cpt http://example.com/concepts#) Prefix(func http://www.w3.org/2007/rif-builtin-function#) Prefix(pred http://www.w3.org/2007/rif-builtin-predicate#) a. Universal form: Forall ?item ?deliverydate ?scheduledate ?diffduration ?diffdays ( cpt:reject(ppl:John ?item) :- And(cpt:perishable(?item) cpt:delivered(?item ?deliverydate ppl:John) cpt:scheduled(?item ?scheduledate) ?diffduration = External(func:subtract-dateTimes(?deliverydate ?scheduledate)) ?diffdays = External(func:days-from-duration(?diffduration)) External(pred:numeric-greater-than(?diffdays 10))) ) b. Universal-existential form: Forall ?item ( cpt:reject(ppl:John ?item ) :- Exists ?deliverydate ?scheduledate ?diffduration ?diffdays ( And(cpt:perishable(?item) cpt:delivered(?item ?deliverydate ppl:John) cpt:scheduled(?item ?scheduledate) ?diffduration = External(func:subtract-dateTimes(?deliverydate ?scheduledate)) ?diffdays = External(func:days-from-duration(?diffduration)) External(pred:numeric-greater-than(?diffdays 10))) ) )
Example 4 (A RIF-Core document containing an annotated group).
This example shows a complete document containing a group formula that consists of two RIF-Core rules. The first of these rules is copied from Example 3a. The group is annotated with an IRI identifier and frame-represented Dublin Core metadata.
Document( Prefix(ppl http://example.com/people#) Prefix(cpt http://example.com/concepts#) Prefix(dc http://purl.org/dc/terms/) Prefix(func http://www.w3.org/2007/rif-builtin-function#) Prefix(pred http://www.w3.org/2007/rif-builtin-predicate#) Prefix(xs http://www.w3.org/2001/XMLSchema#) (* "http://sample.org"^^rif:iri pd[dc:publisher -> http://www.w3.org/ dc:date -> "2008-04-04"^^xs:date] *) Group ( Forall ?item ?deliverydate ?scheduledate ?diffduration ?diffdays ( cpt:reject(ppl:John ?item) :- And(cpt:perishable(?item) cpt:delivered(?item ?deliverydate ppl:John) cpt:scheduled(?item ?scheduledate) ?diffduration = External(func:subtract-dateTimes(?deliverydate ?scheduledate)) ?diffdays = External(func:days-from-duration(?diffduration)) External(pred:numeric-greater-than(?diffdays 10))) ) Forall ?item ( cpt:reject(ppl:Fred ?item) :- cpt:unsolicited(?item) ) ) )
3 RIF-Core Semantics
RIF-Core is a syntactic subset of RIF-BLD and the semantics of RIF-Core is identical that of RIF-BLD.
We use the same semantic structures I as defined in RIF-BLD [RIF-BLD] section 3.2 and the same truth value mapping TValI as defined in [RIF-BLD] section 3.4 to give the interpretation of RIF-Core non-Document formulas.
Then we define the interpretation of RIF-Core Documents analogously to RIF-BLD documents:
Let Δ be a RIF-Core document formula and let Δ1, ..., Δk be all the RIF-Core document formulas that are imported (directly or indirectly, according to Definition Imported document in [RIF-BLD] section 2.5) into Δ. Let Γ, Γ1, ..., Γk denote the respective RIF-Core group formulas associated with these documents. Let I = {IΔ, IΔ1, ..., IΔk, ...} be a semantic multi-structure that contains semantic structures adorned with at least the documents Δ, Δ1, ..., Δk. Then we define:
- TValI(Δ) = t if and only if TValIΔ(Γ) = TValIΔ1(Γ1) = ... = TValIΔk(Γk) = t. ☐
We then define the same notion of logical entailment for RIF-Core as for RIF-BLD:
Definition (Models). A multi-structure I is a model of a formula, φ, written as I |= φ, iff TValI(φ) = t. Here φ can be a RIF-Core document or a non-document formula. ☐
Definition (Logical entailment). Let φ and ψ be RIF-Core (document or non-document) formulas. We say that φ entails ψ, written as φ |= ψ, if and only if for every multi-structure, I, for which both TValI(φ) and TValI(ψ) are defined, I |= φ implies I |= ψ. ☐
4 XML Serialization Syntax for RIF-Core
The RIF-Core XML serialization defines
- a normative mapping from the RIF-Core presentation syntax to XML (Section Mapping from the Presentation Syntax to the XML Syntax), and
- a normative XML Schema for the XML syntax (Appendix XML Schema for Core).
Recall that the syntax of RIF-Core is not context-free and thus cannot be fully captured by EBNF or XML Schema. Still, validity with respect to XML Schema can be a useful test. To reflect this state of affairs, we define two notions of syntactic correctness. The weaker notion checks correctness only with respect to XML Schema, while the stricter notion represents "true" syntactic correctness.
Definition (Valid Core document in XML syntax). A valid Core document in the XML syntax is an XML document that is valid with respect to the XML schema in Appendix XML Schema for Core. ☐
Definition (Conformant Core document in XML syntax). A conformant Core document in the XML syntax is a valid Core document in the XML syntax that is the image of a well-formed RIF-Core document in the presentation syntax (see Definition Well-formed formula in Section Formulas) under the presentation-to-XML syntax mapping χcore defined in Section Mapping from the Presentation Syntax to the XML Syntax. ☐
The XML serialization for RIF-Core is alternating or fully striped [ANF01]. A fully striped serialization views XML documents as objects and divides all XML tags into class descriptors, called type tags, and property descriptors, called role tags [TRT03]. We follow the tradition of using capitalized names for type tags and lowercase names for role tags.
The all-uppercase classes in the presentation syntax, such as FORMULA, become XML Schema groups in Appendix XML Schema for Core. They act like macros and are not visible in instance markup. The other classes as well as non-terminals and symbols (such as Exists or =) become XML elements with optional attributes, as shown below.
RIF-Core uses [XML1.0] for its XML syntax.
4.1 XML for the Condition Language
XML serialization of RIF-Core in Section EBNF for RIF-Core Condition Language uses the following elements.
- And (conjunction) - Or (disjunction) - Exists (quantified formula for 'Exists', containing declare and formula roles) - declare (declare role, containing a Var) - formula (formula role, containing a FORMULA) - Atom (atom formula, positional or with named arguments) - External (external call, containing a content role) - content (content role, containing an Atom) - Member (member formula) - Frame (Frame formula) - object (Member/Frame role, containing a TERM or an object description) - op (Atom role for predicates/functions as operations) - args (Atom positional arguments role, with fixed 'ordered' attribute, containing n TERMs) - instance (Member instance role) - class (Member class role) - sub (Subclass sub-class role) - slot (Atom or Frame slot role, with fixed 'ordered' attribute, containing a Name or TERM followed by a TERM) - Const (individual, function, or predicate symbol, with optional 'type' attribute) - Var (logic variable) - id (identifier role, containing IRICONST) - meta (meta role, containing metadata as a Frame or Frame conjunction)
The id and meta elements, which are expansions of the IRIMETA element, can occur optionally as the initial children of any Class element.
For the XML Schema definition of the RIF-Core condition language see Appendix XML Schema for Core.
The XML syntax for symbol spaces uses the type attribute associated with the XML element Const. For instance, a literal in the xs:dateTime datatype is represented as <Const type="&xs;dateTime">2007-11-23T03:55:44-02:30</Const>. RIF-Core also uses the ordered attribute to indicate that the children of args and slot elements are ordered.
Example 5 (A RIF condition and its XML serialization).
This example illustrates XML serialization for RIF conditions. As before, the compact URI notation is used for better readability. Assume that the following prefix directives are found in the preamble to the document:
Prefix(bks http://example.com/books#) Prefix(cpt http://example.com/concepts#) Prefix(rif http://www.w3.org/2007/rif#) Prefix(xs http://www.w3.org/2001/XMLSchema#)
RIF condition And (Exists ?Buyer cpt:purchaseBook(?Buyer, ?Seller, bks:LeRif, ?Author) ?Seller = ?Author <And> <formula> <Exists> <declare><Var>Buyer</Var></declare> <formula> <Atom> <op><Const type="&rif;iri">&cpt;purchaseBook</Const></op> <args ordered="yes"> <Var>Buyer</Var> <Var>Seller</Var> <Const type="&rif;iri">&bks;LeRif</Const> <Var>Author</Var> </args> </Atom> </formula> </Exists> </formula> <formula> <Equal> <left><Var>Seller</Var></left> <right><Var>Author</Var></right> </Equal> </formula> </And>
4.2 XML for the Rule Language
We now extend the set of RIF-Core serialization elements from Section XML for RIF-Core Condition Language by including rules, along with their enclosing groups and documents, as described in Section EBNF for RIF-Core Rule Language. The extended set includes the tags listed below. While there is a RIF-Core element tag for the Import directive, there are none for the Prefix and Base directives: they are handled as discussed in Section Mapping of the RIF-Core Rule Language.
- Document (document, containing optional directive and payload roles) - directive (directive role, containing Import) - payload (payload role, containing Group) - Import (importation, containing location and optional profile) - location (location role, containing IRICONST) - profile (profile role, containing PROFILE) - Group (nested collection of sentences) - sentence (sentence role, containing RULE or Group) - Forall (quantified formula for 'Forall', containing declare and formula roles) - Implies (implication, containing if and then roles) - if (antecedent role, containing FORMULA) - then (consequent role, containing ATOMIC or conjunction of ATOMICs)
The XML Schema Definition of RIF-Core is given in Appendix XML Schema for Core.
Example 7 (Serializing a RIF-Core document containing an annotated group).
This example shows a serialization for the document from Example 4. For convenience, the document is reproduced at the top and then is followed by its serialization.
Presentation syntax: Document( Prefix(ppl http://example.com/people#) Prefix(cpt http://example.com/concepts#) Prefix(dc http://purl.org/dc/terms/) Prefix(func http://www.w3.org/2007/rif-builtin-function#) Prefix(pred http://www.w3.org/2007/rif-builtin-predicate#) Prefix(xs http://www.w3.org/2001/XMLSchema#) (* "http://sample.org"^^rif:iri pd[dc:publisher -> http://www.w3.org/ dc:date -> "2008-04-04"^^xs:date] *) Group ( Forall ?item ?deliverydate ?scheduledate ?diffduration ?diffdays ( cpt:reject(ppl:John ?item) :- And(cpt:perishable(?item) cpt:delivered(?item ?deliverydate ppl:John) cpt:scheduled(?item ?scheduledate) ?diffduration = External(func:subtract-dateTimes(?deliverydate ?scheduledate)) ?diffdays = External(func:days-from-duration(?diffduration)) External(pred:numeric-greater-than(?diffdays 10))) ) Forall ?item ( cpt:reject(ppl:Fred ?item) :- cpt:unsolicited(?item) ) ) ) XML syntax: <!DOCTYPE Document [ <!ENTITY ppl "http://example.com/people#"> <!ENTITY cpt "http://example.com/concepts#"> <!ENTITY dc "http://purl.org/dc/terms/"> <!ENTITY rif "http://www.w3.org/2007/rif#"> <!ENTITY func "http://www.w3.org/2007/rif-builtin-function#"> <!ENTITY pred "http://www.w3.org/2007/rif-builtin-predicate#"> <!ENTITY xs "http://www.w3.org/2001/XMLSchema#"> ]> <Document xmlns="http://www.w3.org/2007/rif#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema#"> <payload> <Group> <id> <Const type="&rif;iri">http://sample.org</Const> </id> <meta> <Frame> <object> <Const type="&rif;local">pd</Const> </object> <slot ordered="yes"> <Const type="&rif;iri">&dc;publisher</Const> <Const type="&rif;iri">http://www.w3.org/</Const> </slot> <slot ordered="yes"> <Const type="&rif;iri">&dc;date</Const> <Const type="&xs;date">2008-04-04</Const> </slot> </Frame> </meta> <sentence> <Forall> <declare><Var>item</Var></declare> <declare><Var>deliverydate</Var></declare> <declare><Var>scheduledate</Var></declare> <declare><Var>diffduration</Var></declare> <declare><Var>diffdays</Var></declare> <formula> <Implies> <if> <And> <formula> <Atom> <op><Const type="&rif;iri">&cpt;perishable</Const></op> <args ordered="yes"><Var>item</Var></args> </Atom> </formula> <formula> <Atom> <op><Const type="&rif;iri">&cpt;delivered</Const></op> <args ordered="yes"> <Var>item</Var> <Var>deliverydate</Var> <Const type="&rif;iri">&ppl;John</Const> </args> </Atom> </formula> <formula> <Atom> <op><Const type="&rif;iri">&cpt;scheduled</Const></op> <args ordered="yes"> <Var>item</Var> <Var>scheduledate</Var> </args> </Atom> </formula> <formula> <Equal> <left><Var>diffduration</Var></left> <right> <External> <content> <Expr> <op><Const type="&rif;iri">&func;subtract-dateTimes</Const></op> <args ordered="yes"> <Var>deliverydate</Var> <Var>scheduledate</Var> </args> </Expr> </content> </External> </right> </Equal> </formula> <formula> <Equal> <left><Var>diffdays</Var></left> <right> <External> <content> <Expr> <op><Const type="&rif;iri">&func;days-from-duration</Const></op> <args ordered="yes"> <Var>diffduration</Var> </args> </Expr> </content> </External> </right> </Equal> </formula> <formula> <External> <content> <Atom> <op><Const type="&rif;iri">&pred;numeric-greater-than</Const></op> <args ordered="yes"> <Var>diffdays</Var> <Const type="&xs;integer">10</Const> </args> </Atom> </content> </External> </formula> </And> </if> <then> <Atom> <op><Const type="&rif;iri">&cpt;reject</Const></op> <args ordered="yes"> <Const type="&rif;iri">&ppl;John</Const> <Var>item</Var> </args> </Atom> </then> </Implies> </formula> </Forall> </sentence> <sentence> <Forall> <declare><Var>item</Var></declare> <formula> <Implies> <if> <Atom> <op><Const type="&rif;iri">&cpt;unsolicited</Const></op> <args ordered="yes"><Var>item</Var></args> </Atom> </if> <then> <Atom> <op><Const type="&rif;iri">&cpt;reject</Const></op> <args ordered="yes"> <Const type="&rif;iri">&ppl;Fred</Const> <Var>item</Var> </args> </Atom> </then> </Implies> </formula> </Forall> </sentence> </Group> </payload> </Document>
4.3 Mapping from the Presentation Syntax to the XML Syntax
This section defines a normative mapping, χcore, from the presentation syntax to the XML syntax of RIF-Core. The mapping is given via tables where each row specifies the mapping of a particular syntactic pattern in the presentation syntax. These patterns appear in the first column of the tables and the bold-italic symbols represent metavariables. The second column represents the corresponding XML patterns, which may contain applications of the mapping χcore to these metavariables. When an expression χcore(metavar) occurs in an XML pattern in the right column of a translation table, it should be understood as a recursive application of χcore to the presentation syntax represented by the metavariable. The XML syntax result of such an application is substituted for the expression χcore(metavar). A sequence of terms containing metavariables with subscripts is indicated by an ellipsis. A metavariable or a well-formed XML subelement is marked as optional by appending a bold-italic question mark, ?, on its right.
4.3.1 Mapping of the Condition Language
The χcore mapping from the presentation syntax to the XML syntax of the RIF-Core Condition Language is specified by the table below. Each row indicates a translation χcore(Presentation) = XML. Since the presentation syntax of RIF-Core is context sensitive, the mapping must differentiate between the terms that occur in the position of the individuals and the terms that occur as atomic formulas. To this end, in the translation table, the positional and named argument terms that occur in the context of atomic formulas are denoted by the expressions of the form pred(...) and the terms that occur as individuals are denoted by expressions of the form func(...). In the table, each metavariable for an (unnamed) positional argumenti is assumed to be instantiated to values unequal to the instantiations of named arguments unicodestringj -> fillerj. Regarding the last but first row, we assume that shortcuts for constants [RIF-DTB] have already been expanded to their full form ("..."^^symspace).
|Presentation Syntax
|XML Syntax
And ( conjunct1 . . . conjunctn )
<And> <formula>χcore(conjunct1)</formula> . . . <formula>χcore(conjunctn)</formula> </And>
Or ( disjunct1 . . . disjunctn )
<Or> <formula>χcore(disjunct1)</formula> . . . <formula>χcore(disjunctn)</formula> </Or>
Exists variable1 . . . variablen ( body )
<Exists> <declare>χcore(variable1)</declare> . . . <declare>χcore(variablen)</declare> <formula>χcore(body)</formula> </Exists>
External ( atomframexpr )
<External> <content>χcore(atomframexpr)</content> </External>
pred ( argument1 . . . argumentn )
<Atom> <op>χcore(pred)</op> <args ordered="yes"> χcore(argument1) . . . χcore(argumentn) </args> </Atom>
inst [ key1 -> filler1 . . . keyn -> fillern ]
<Frame> <object>χcore(inst)</object> <slot ordered="yes"> χcore(key1) χcore(filler1) </slot> . . . <slot ordered="yes"> χcore(keyn) χcore(fillern) </slot> </Frame>
inst # class
<Member> <instance>χcore(inst)</instance> <class>χcore(class)</class> </Member>
<Const type="symspace">unicodestring</Const>
4.3.2 Mapping of the Rule Language
The χcore mapping from the presentation syntax to the XML syntax of the RIF-Core Rule Language is specified by the table below. It extends the translation table of Section Translation of RIF-Core Condition Language. While the Import directive is handled by the presentation-to-XML syntax mapping, the Prefix and Base directives are not. Instead, these directives should be handled by macro-expanding the associated shortcuts (compact URIs). Namely, a prefix name declared in a Prefix directive is expanded into the associated IRI, while relative IRIs are completed using the IRI declared in the Base directive. The mapping χcore applies only to such macro-expanded documents. RIF-Core also allows other treatments of Prefix and Base provided that they produce equivalent XML documents. One such treatment is employed in the examples in this document, especially Example 7. It replaces prefix names with definitions of XML entities as follows. Each Prefix declaration becomes an ENTITY declaration [XML1.0] within a DOCTYPE DTD attached to the RIF-Core Document. The Base directive is mapped to the xml:base attribute [XML-Base] in the XML Document tag. Compact URIs of the form prefix:suffix are then mapped to &prefix;suffix.
|Presentation Syntax
|XML Syntax
Document( Import(loc1 prfl1?) . . . Import(locn prfln?) group )
<Document> <directive> <Import> <location>χcore(loc1)</location> <profile>χcore(prfl1)</profile>? </Import> </directive> . . . <directive> <Import> <location>χcore(locn)</location> <profile>χcore(prfln)</profile>? </Import> </directive> <payload>χcore(group)</payload> </Document>
Group( clause1 . . . clausen )
<Group> <sentence>χcore(clause1)</sentence> . . . <sentence>χcore(clausen)</sentence> </Group>
Forall variable1 . . . variablen ( rule )
<Forall> <declare>χcore(variable1)</declare> . . . <declare>χcore(variablen)</declare> <formula>χcore(rule)</formula> </Forall>
conclusion :- condition
<Implies> <if>χcore(condition)</if> <then>χcore(conclusion)</then> </Implies>
4.3.3 Mapping of Annotations
The χcore mapping from RIF-Core annotations in the presentation syntax to the XML syntax is specified by the table below. It extends the translation tables of Sections Translation of RIF-Core Condition Language and Translation of RIF-Core Rule Language. The metavariable Typetag in the presentation and XML syntaxes stands for any of the class names And, Or, External, Document, or Group, and Quantifier for Exists or Forall. The dollar sign, $, stands for any of the binary infix operator names #, ##, =, or :-, while Binop stands for their respective class names Member, Subclass, Equal, or Implies. Again, each metavariable for an (unnamed) positional argumenti is assumed to be instantiated to values unequal to the instantiations of named arguments unicodestringj -> fillerj.
|Presentation Syntax
|XML Syntax
(* iriconst? frameconj? *) Typetag ( e1 . . . en )
<Typetag> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? e1' . . . en' </Typetag> where e1', . . ., en' are defined by the equation χcore(Typetag(e1 . . . en)) = <Typetag>e1' . . . en'</Typetag>
(* iriconst? frameconj? *) Quantifier variable1 . . . variablen ( body )
<Quantifier> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? <declare>χcore(variable1)</declare> . . . <declare>χcore(variablen)</declare> <formula>χcore(body)</formula> </Quantifier>
(* iriconst? frameconj? *) pred ( argument1 . . . argumentn )
<Atom> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? <op>χcore(pred)</op> <args ordered="yes"> χcore(argument1) . . . χcore(argumentn) </args> </Atom>
(* iriconst? frameconj? *) pred ( unicodestring1 -> filler1 . . . unicodestringn -> fillern )
<Atom> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? <op>χcore(pred)</op> <slot ordered="yes"> <Name>unicodestring1</Name> χcore(filler1) </slot> . . . <slot ordered="yes"> <Name>unicodestringn</Name> χcore(fillern) </slot> </Atom>
(* iriconst? frameconj? *) inst [ key1 -> filler1 . . . keyn -> fillern ]
<Frame> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? <object>χcore(inst)</object> <slot ordered="yes"> χcore(key1) χcore(filler1) </slot> . . . <slot ordered="yes"> χcore(keyn) χcore(fillern) </slot> </Frame>
(* iriconst? frameconj? *) e1 $ e2
<Binop> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? e1' e2' </Binop> where Binop, e1', e2' are defined by the equation χcore(e1 $ e2) = <Binop>e1' e2'</Binop>
(* iriconst? frameconj? *) unicodestring^^symspace
<Const type="symspace"> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? unicodestring </Const>
(* iriconst? frameconj? *) ?unicodestring
<Var> <id>χcore(iriconst)</id>? <meta>χcore(frameconj)</meta>? unicodestring </Var>
5 Conformance and Safety
RIF-Core is a syntactic subset of both RIF-BLD and RIF-PRD. The semantics of any RIF-Core formula is well defined via the semantic structures, truth valuation function and definition of logical entailment given in section 3.
All RIF-Core documents are syntactically also RIF-PRD documents. However, some formula are unsafe and do not lead to a stable fixed-point if executed under the RIF-PRD operational semantics. Without datatypes and builtins then RIF-Core would correspond to pure Datalog for which the logical semantics and operational fixed-point semantics do coincide [Vianu97].
In order to allow production rule systems and logic programming systems to interchange rulesets via RIF-Core we define a safe subset of RIF-Core and only require minimally conformant RIF-Core consumers to correctly translate this safe subset. A minimally conformant RIF-Core consumer when presented with a well-formed but not safe RIF-Core document is free to reject that document or translate it (with or without a warning) with the risk that the translated ruleset when executed may not terminate. We allow any well-formed RIF-Core document to be regarded as a Conformant RIF-Core document even if not safe, thus allowing RIF-Core producers and consumers to produce and consume unsafe rulesets when appropriate.
5.1 Safeness
A subformula of a RIF-Core condition formula is called an external subformula if it appears within an Externally defined term. A subformula of a condition formula is called disjunctive subformula if it appears within a Disjunction.
Definition (Safeness).
- A variable ?v is called safe with respect to a RIF formula φ if it appears in at least one non-external, non-disjunctive atomic subformula of φ such that ?v is not in the scope of an existential quantifier within ψ.
- A RIF condition formula φ is called safe if all its variables are safe with respect to φ and for all its existential subformulas Exists ?V1 ... ?Vn ( ψ ) each ?V1 ... ?Vn is safe with respect to ψ
- A RIF rule φ :- ψ is called safe if all its variables are safe with respect to ψ.
- A RIF rule implication φ :- ψ is called safe if all its variables are safe with respect to ψ.
- A RIF Universal rule implication Forall ?V1 ... ?Vn (&phi) is called safe if φ is safe.
- A RIF Universal fact Forall ?V1 ... ?Vn (φ) is called safe if φ is ground.
5.2 Conformance Clauses
RIF-Core does not require or expect conformant systems to implement the RIF-Core presentation syntax. Instead, conformance is described in terms of semantics-preserving transformations.
Let Τ be a set of datatypes that includes the datatypes specified in [RIF-DTB], and suppose Ε is a set of external predicates and functions that includes the built-ins listed in [RIF-DTB]. We say that a formula φ is a CoreΤ,Ε formula iff
- it is a well-formed Core formula,
- all the datatypes used in φ are in Τ, and
- all the externally defined functions and predicates used in φ are in Ε.
A RIF processor is a conformant CoreΤ,Ε consumer iff it implements a semantics-preserving mapping, μ, from the set of all CoreΤ,Ε formulas to the language L of the processor.
Formally, this means that for any pair φ, ψ of CoreΤ,Ε formulas for which φ |=Core ψ is defined, φ |=Core ψ iff μ(φ) |=L μ(ψ). Here |=Core denotes the logical entailment in RIF-Core and |=L is the logical entailment in the language L of the RIF processor.
A RIF processor is a conformant CoreΤ,Ε producer iff it implements a semantics-preserving mapping, ν, from a subset of the language L of the processor to a set of CoreΤ,Ε formulas.
Formally, this means that for any pair φ, ψ of formulas in the aforesaid subset of L for which φ |=L ψ is defined, φ |=L ψ iff ν(φ) |=Core ν(ψ).
A conformant document is one which conforms to all the syntactic constraints of RIF-Core, including ones that cannot be checked by an XML Schema validator (cf. Definition Conformant Core document in XML syntax).
A round-tripping of a conformant Core document is its semantics-preserving mapping to a document in any language L followed by a semantics-preserving mapping from the L document back to a conformant Coredocument. While semantically equivalent, the original and the round-tripped Core documents need not be identical. Metadata should survive Core round-tripping.
The above definitions are specializations to Core of the general conformance clauses defined in the RIF framework for logic dialects [RIF-FLD]. The following clauses are further restrictions that are specific to RIF-Core.
RIF-Core specific clauses
- Conformant Core producers and consumers are required to support only the entailments of the form φ |=Core ψ, where ψ is a closed RIF condition formula, i.e., an existentially quantified RIF condition in which every variable, ?V, is in the scope of a quantifier of the form Exists ?V.
- Safely conformant Core producers and consumers are required to support only entailments of the form φ |=Core ψ, where ψ is a closed RIF condition formula and φ is a safe formula.
- A conformant RIF-Core consumer is a conformant CoreΤ,Ε consumer in which Τ consists only of the datatypes and Ε consists only of the externally defined functions and predicates that are required by RIF-Core. These datatypes and externally defined terms (called built-ins) are specified in [RIF-DTB]. A conformant RIF-Core consumer must reject all inputs that do not match the syntax of Core. If it implements extensions, it may do so under user control -- having a "strict Core" mode and a "run-with-extensions" mode.
- A conformant Core producer is a conformant CoreΤ,Ε producer, which produces documents that include only the datatypes and externals that are required by Core.
Feature At Risk #3: Strictness Requirement
Note: This feature is "at risk" and may be altered or removed from this specification based on feedback. If you have concerns about this or information which may be useful in our eventual decision, please tell us at email@example.com. See the full list of features "at risk" in RIF.
The two preceding clauses are features AT RISK. In particular, the "strictness" requirement is under discussion.
6 RIF-Core as a Specialization of RIF-PRD
This normative section describes RIF-Core by specializing RIF-PRD . The reader is assumed to be familiar with RIF-PRD as described in [RIF-PRD]. The reader who is not interested in how RIF-Core is derived from PRD can skip this section.
6.1 Intersection of RIF-PRD and RIF-BLD
RIF-PRD and RIF-BLD share essentially the same presentation syntax and XML syntax.
The differences between the two dialects are summarized below:
- RIF-BLD allows logic and externally specified, fixed-interpretation functions as TERM, whereas RIF-PRD accepts only externally specified functions;
- RIF-BLD allows ATOMIC or And(ATOMIC*) in rule conclusions, whereas RIF-PRD allows ACTION or Do(ACTION*). In RIF-PRD it is not possible to conclude equality or class membership.
- RIF-PRD allows Not(FORMULA), which RIF-BLD does not accept;
- RIF-PRD defines ASSERT and Retract actions that are not allowed in RIF-BLD.
- RIF-PRD introduces a pattern matching constraint in Forall
For context, the table below lists the constructs which are in the maximal common subset (intersection) of BLD and PRD, marks certain rows as not being in Core, or annotates them w.r.t. restrictions making them part of Core.
|Presentation syntax
|XML syntax
[Const | Var | External]
|Const ::=
<Const type=xsd:anyURI [xml:lang=xsd:language]? > Any Unicode string </Const>
|Var ::=
'?' Any Unicode string
<Var> Any Unicode string </Var>
|External (as TERM) ::=
|Remark: only used for external built-in calls; no logical functions
'External' '(' Expr ')'
<External> <content> Expr </content> </External>
[Atom | Frame]
|Atom ::=
Const '(' (TERM* ')'
<Atom> <op> Const </op> <args rif:ordered="yes"> TERM* </args>? </Atom>
|Equal ::=
<Equal> <left> TERM </left> <right> TERM </right> </Equal>
|Member ::=
|Remark: under discussion; might be not part of Core
<Member> <instance> TERM </instance> <class> TERM </class> </Member>
|Frame ::=
<Frame> <object> TERM </object> <slot rif:ordered="yes"> TERM TERM </slot>* </Frame>
[ATOMIC | External | And | Or | Exists]
|External (as FORMULA) ::=
'External '(' [Atom | Frame] ')'
<External> <content> [ Atom | Frame ] </content> </External>
|And ::=
'And' '(' FORMULA* ')'
<And> <formula> FORMULA </formula>* </And>
|Or ::=
'Or' '(' FORMULA* ')'
<Or> <formula> FORMULA </formula>* </Or>
|Exists ::=
'Exists' Var+ '(' FORMULA ')'
<Exists> <declare> Var </declare>+ <formula> FORMULA </formula> </Exists>
|Remark: There is an implicit assert assumption for production rules
[ Forall | Implies | ATOMIC ]
|Forall ::=
|Remark: There is an implicit assert assumption for production rules
' Forall ' Var+ ' ( ' [Implies | ATOMIC] ' ) '
<Forall> <declare> Var </declare>+ <formula> [Implies | ATOMIC ] </formula> </Forall>
|Implies ::=
|Remark: There is an implicit assert assumption for production rules;
<Implies> <if> FORMULA </if> <then> ATOMIC </then> </Implies>
|Group ::=
METADATA? 'Group' '(' ([RULE | Group])* ')'
<Group> <sentence> [ RULE | Group ] </sentence>* </Group>
METADATA? 'Document' '(' Group? ')'
<Document> <payload> Group </payload>? </Document>
'(*' Const? (Frame | 'And' '(' Frame* ')')? '*)'
<AnyClassTag> <id> Const </declare>? <meta> [ Frame | <And> <formula> Frame </formula> </And> ] </meta>? other content of AnyClassTag </AnyClassTag>
7 Acknowledgements
This document is the product of the Rules Interchange Format (RIF) Working Group (see below) whose members deserve recognition for their time and commitment. The editors extend special thanks to: ***, for their thorough reviews and insightful discussions; the working group chairs, Chris Welty and Christian de Sainte-Marie, for their invaluable technical help and inspirational leadership; and W3C staff contact Sandro Hawke, a constant source of ideas, help, and feedback.
The regular attendees at meetings of the Rule Interchange Format (RIF) Working Group at the time of the publication were: Adrian Paschke (Freie Universitaet Berlin), Axel Polleres (DERI), Chris Welty (IBM), Christian de Sainte Marie (IBM), Dave Reynolds (HP), Gary Hallmark (ORACLE), Harold Boley (NRC), Jos de Bruijn (FUB), Leora Morgenstern (IBM), Michael Kifer (Stony Brook), Mike Dean (BBN), Sandro Hawke (W3C/MIT), and Stella Mitchell (IBM). We would also like to thank *** past members of the working group, ***.
8 References
8.1 Normative References
- Resource Description Framework (RDF): Concepts and Abstract Syntax, Klyne G., Carroll J. (Editors), W3C Recommendation, 10 February 2004, http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/. Latest version available at http://www.w3.org/TR/rdf-concepts/.
- RFC 3066 - Tags for the Identification of Languages, H. Alvestrand, IETF, January 2001. This document is http://www.isi.edu/in-notes/rfc3066.txt.
- RFC 3987 - Internationalized Resource Identifiers (IRIs), M. Duerst and M. Suignard, IETF, January 2005. This document is http://www.ietf.org/rfc/rfc3987.txt.
- RIF Basic Logic Dialect, Boley H. and Kifer M. (Editors), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/BLD.
- RIF Datatypes and Built-Ins 1.0, Polleres A., Boley H. and Kifer M. (Editors), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/DTB.
- RIF Framework for Logic Dialects, Boley H. and Kifer M. (Editors), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/FLD.
- RIF RDF and OWL Compatibility, de Bruijn, J. (Editor), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/SWC.
- RIF Production Rule Dialect, de Sainte Marie C., Paschke A., Hallmark G. (Editors), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/PRD.
- Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation, World Wide Web Consortium, 16 August 2006, edited in place 29 September 2006. This version is http://www.w3.org/TR/2006/REC-xml-20060816/.
- [XML-Base]
- XML Base, W3C Recommendation, World Wide Web Consortium, 27 June 2001. This version is http://www.w3.org/TR/2001/REC-xmlbase-20010627/. The latest version is available at http://www.w3.org/TR/xmlbase/.
- XML Schema Part 2: Datatypes, W3C Recommendation, World Wide Web Consortium, 2 May 2001. This version is http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/. The latest version is available at http://www.w3.org/TR/xmlschema-2/.
8.2 Informational References
- Normal Form Conventions for XML Representations of Structured Data, Henry S. Thompson. October 2001. Available at http://www.ltg.ed.ac.uk/~ht/normalForms.html.
- Symbolic Logic and Mechanical Theorem Proving, C.L. Chang and R.C.T. Lee. Academic Press, 1973.
- CURIE Syntax 1.0: A syntax for expressing Compact URIs, Mark Birbeck, Shane McCarron. W3C Working Draft 2 April 2008. Available at http://www.w3.org/TR/curie/.
- [Enderton01]
- A Mathematical Introduction to Logic, Second Edition, H. B. Enderton. Academic Press, 2001.
- Logical foundations of object-oriented and frame-based languages, M. Kifer, G. Lausen, J. Wu. Journal of ACM, July 1995, pp. 741--843.
- [Mendelson97]
- Introduction to Mathematical Logic, Fourth Edition, E. Mendelson. Chapman & Hall, 1997.
- [OWL-Reference]
- OWL Web Ontology Language Reference, M. Dean, G. Schreiber, Editors, W3C Recommendation, 10 February 2004. Latest version available at http://www.w3.org/TR/owl-ref/.
- RDF/XML Syntax Specification (Revised), Dave Beckett, Editor, W3C Recommendation, 10 February 2004, http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/. Latest version available at http://www.w3.org/TR/rdf-syntax-grammar/.
- RIF Use Cases and Requirements, Paschke A., Hirtle D., Ginsberg A., Patranjan P-L., McCabe F. (Editors), W3C Rule Interchange Format Working Group Draft. Latest Version available at http://www.w3.org/2005/rules/wiki/UCR.
- Object-Oriented RuleML: User-Level Roles, URI-Grounded Clauses, and Order-Sorted Terms, H. Boley. Springer LNCS 2876, Oct. 2003, pp. 1-16. Preprint at http://iit-iti.nrc-cnrc.gc.ca/publications/nrc-46502_e.html.
- [vEK76]
- The semantics of predicate logic as a programming language, M. van Emden and R. Kowalski. Journal of the ACM 23 (1976), pp. 733-742.
- [Vianu97]
- Rule-Based Languages, Vianu V.. Annals of Mathematics and Artificial Intelligence 19 (1997), pp. 215-259.
9 Appendix: XML Schema for RIF-Core
The namespace of RIF is http://www.w3.org/2007/rif#.
XML schemas for the RIF-Core sublanguages are defined below and are also available here with additional examples.
9.1 Condition Language
<?xml version="1.0" encoding="UTF-8"?>
9.2 Rule Language
<?xml version="1.0" encoding="UTF-8"?>


text:
NETS: Heat improve to 4-0 at home
MIAMI -- In 25 seasons of Miami Heat basketball, the club had never won its first four home games of any season.
That is, until now.
And the Heat are making it look easy.
Dwyane Wade scored 22 points on 10 for 14 shooting, LeBron James finished two assists shy of a triple-double and the Heat clamped down defensively again to beat the Brooklyn Nets 103-73 on Wednesday night.
Miami scored 31 points off Brooklyn turnovers, and starting with the final minute of the first half, the Heat outscored the Nets 57-32.
"When we get stops, we're going to break open a lot of games because we can score," James said. "So that's the No. 1 key."
James had 20 points and 12 rebounds in only 30 minutes, and Rashard Lewis came off the bench to score 13 points on 6 for 9 shooting for the Heat (4-1). Miami -- which plays its next six games on the road -- has won its four home games by an average of 17.8 points.
Kris Humphries had a double-double by halftime, then was silent in the second half and finished with 11 points and 11 rebounds for the Nets (1-2). Deron Williams scored 14 for Brooklyn, which got 12 off the bench from MarShon Brooks.
"It was just an off-night because we had a lot of open looks," said Nets guard Joe Johnson, who finished 4 for 14 with nine points. "I know I did and I missed a few myself. Other than that it was just shots that we normally make that we didn't make tonight. Against a good team like Miami, you have to make them pay."
Miami started 3-0 at home in four other seasons, always falling in the fourth game. Not this time. The Nets held the lead four times in the opening quarter, but all by one point and lasting a total of 2:33.
Other than that, all Miami. The Heat started 3 for 12 from 3-point range, then made seven of their last 12, giving them 40 makes from beyond the arc in their last three games.
"They're tough when you're turning the ball over," Nets coach Avery Johnson said. "I thought there were times when we got our half-court defense set that we were decent. We got the ball out of LeBron's hands some, out of Wade's hands some, but then we didn't recognize their shooters and their shooters made shots tonight."
The Heat shot 52 percent, holding New Jersey to 38 percent. Miami finished with 25 assists and 12 turnovers; New Jersey finished with 12 assists and 19 turnovers.
"It was good to see another game, sub-40 percent," Heat coach Erik Spoelstra said. "Our guys were, for the most part, committed to try to make an impact on that side of the floor."
Brooklyn didn't lose sight of Miami in the first half, still being within five with less than a minute remaining until the break, before the Heat got late scores from Wade and James to take a 50-41 edge into the locker room.
And as was the case against Phoenix (with a 23-6 run) on Monday, the Heat used the third quarter as the springboard.
It was a 54-46 game after Keith Bogans made a 3-pointer for Brooklyn early in the third, but after that, all Heat. Miami needed just 91 seconds to put together a 10-0 run -- two baskets by Wade started it, and 3-pointers from Shane Battier and Mario Chalmers finished it, putting the Heat up 64-46.
"We know there's going to be moments when you're not going to be able to shoot the ball as well as you want to," Wade said. "It averages out for this team. ... That's why you have to be a good defensive team to be successful in this league."
The outcome was never again in doubt. Chalmers extended the lead to 20 when he sliced down the lane for a nifty layup with 3:45 left in the third, and James made a stepback 3-pointer as time was running out in the period for what was then Miami's largest lead, 79-56.
By then, the only drama was whether James would get his 33rd regular-season triple-double, which would have been his first since March 29, 2011.
Instead, he remained on the bench in the fourth, the Heat comfortably ahead the whole way.
"One, I didn't know," Spoelstra said. "Two, that's not the time to put him back in. We're thinking big picture."
NOTES: Wade sent his mother, Jolinda, flowers during a second-quarter timeout as a video message played on the overhead scoreboards. ... The Nets were without Gerald Wallace, who missed his second straight game with a sprained left ankle. Brooklyn is hoping he may be able to do more before its game Friday at Orlando. ... Heat F Udonis Haslem was poked in the left eye in the first half, dropping to his knees in pain when he got hit but staying in the game. ... Wade drew laughter after the morning shootaround, pretending he was miffed about Nets part-owner Jay-Z not attending the meeting when the team tried wooing him as a free agent in 2010 -- but that the rapper appeared in person for James' sit-down that summer with the team. "True," James said.


text:
Feb. 3, 2007
CAMBRIDGE, Mass. - Despite being held to a career-low four points, sophomore standout Jimmy Bartolotta found other ways to lead the MIT men's basketball team to victory against NEWMAC-rival Coast Guard, Saturday afternoon, in Rockwell Cage. Bartolotta hauled in a career-high 15 rebounds and dished out a game-best eight assists, while Alex Krull sparked the scoring contingent with a game-high 20 points as the Engineers rallied late against the Bears, 51-47.
Coast Guard (11-10, 2-7 NEWMAC) was determined not to let the league's second leading scorer win the game for MIT (11-10, 4-5) with a big offensive performance, holding Bartolotta without a field goal attempt in the second half and only five for the entire game. The special attention enabled MIT's other players to secure good looks from the floor as the Engineers finished the game shooting 51.3% from the field.
The Bears endured a tough afternoon on the offensive end, shooting just 30.9% (17-of-55) for the game, including 5-of-22 from outside. Coast Guard stayed in contention and actually was in position to secure the road win mostly thanks to a monster advantage on the boards. The Bears hauled down 16 offensive rebounds, and outscored MIT in second-chance points, 17-0.
However, MIT stayed incredibly patient in its offensive end, often working the shot clock inside five seconds. Krull enjoyed the hot hand, especially early, and finished with 20 points on 8-of-11 shooting. Rookie Erich Bracht was also 8-of-11 from the field, adding 19 points and six rebounds to MIT's totals.
"I thought we adjusted well to their defensive scheme," noted assistant coach Oliver Eslinger. "It was a really gutsy win for our guys."
Jeff Prebeck continued his outstanding junior campaign, leading the Bears with 17 points and 13 rebounds. Al Sowers also reached double figures for Coast Guard by adding 11, while Ryan Burgess helped solidify CGA's big rebounding edge with nine points and 10 boards.
MIT led the entire way in the first half. Leading by as many as 10, the Engineers had a 26-21 lead at halftime. Coast Guard quickly cut into the advantage in the second half and took its first lead of the day at 30-28 following a lay-up by Prebeck with 15:55 to go. Krull answered immediately for MIT, setting the stage for eight lead changes and three ties in the final 15 minutes.
With every possession becoming increasingly important as the game rolled on, the Bears looked to deliver a decisive blow after Sowers drained a three to give Coast Guard a 47-43 lead with less than four minutes left in regulation. On the ensuing possession, Bracht took advantage of a wide-open three from the top of the key and sliced the deficit to one.
In the final minute of the game, Bartolotta showcased his leadership despite the limited offensive numbers. Driving hard to the hoop, he delivered a great pass to Bracht, who finished on a lay-up, while drawing a whistle. After completing the three-point play, MIT led 49-47 with 50 seconds remaining in the game. With less than 10 seconds to go, a potential game-tying field goal was neutralized after Bartolotta drew a charge. He knocked down two free throws between timeouts at the following end to seal the win.


text:
This promotion is for Rewards members only. To take advantage of exclusive offers like these, join Office Depot® OfficeMax® Rewards now!
States Store Locations
Alabama (AL)
Arkansas (AR)
Arizona (AZ)
California (CA)
Colorado (CO)
Connecticut (CT)
District of Columbia (DC)
Delaware (DE)
Florida (FL)
Georgia (GA)
Hawaii (HI)
Iowa (IA)
Illinois (IL)
Indiana (IN)
Kansas (KS)
Kentucky (KY)
Louisiana (LA)
Massachusetts (MA)
Maryland (MD)
Maine (ME)
Michigan (MI)
Minnesota (MN)
Missouri (MO)
Mississippi (MS)
North Carolina (NC)
North Dakota (ND)
Nebraska (NE)
New Hampshire (NH)
New Jersey (NJ)
New Mexico (NM)
Nevada (NV)
New York (NY)
Ohio (OH)
Oklahoma (OK)
Oregon (OR)
Pennsylvania (PA)